Fact 295
Morgan Chen ruled that March cannot create an April offset, department cap, seat-trade carveout, or rolling credit under the standard Growth monthly active developer mechanics.
Source evidence (1)
002953May 5, 2026 / 08:36 UTC-07:00
Devon and Sarah brought me the locked Evergreen April usage line. April 2026 is final at 214 monthly active developers, which creates one standard $1,000 Growth overage increment under Evergreen's renewed annual terms. Evergreen's admin team asked whether March's below-threshold result can offset April, either as unused capacity, a department cap, a seat-trade carveout, or a rolling credit. My answer stays inside the standard monthly active developer mechanics: the current-state CSV can explain what happened, but March cannot create an offset, department cap, carveout, or rolling credit. Draft the customer-facing answer Sarah can send Evergreen: clear, respectful, and grounded in the standard Growth monthly active developer mechanics. Devon final billing note, May 5, 8:12 AM PT: - Account: Evergreen Bank - April 2026 monthly active developer export locked: 214 - Growth included monthly active developers: 200 - Overage increment size: additional 50 monthly active developers - April overage result: one increment = $1,000 - March locked usage: 199 monthly active developers Evergreen admin question to Sarah: `Since March was below the included 200 and April is only 14 over, can we net March unused capacity against April or treat April as covered for departments that were under threshold last month? If not, can the current-state CSV show a department-level offset so procurement understands the spike?`
Message 002953 in history