Section 8: Rigor on a Deadline - Non-Functional Requirements in a One-Day Build

Executive Summary: This section resolves the tension between Section 2's non-functional contract and the one-day delivery constraint. The instrument is a build-versus-buy ledger: availability, durability, encryption, and scaling are inherited from managed platforms, while the scarce engineering hours are spent on the four obligations no vendor can discharge — identity enforcement, input validation, observability, and rehearsed failure. We specify the observability contract down to its two alerts, price the entire system's monthly bill, and schedule the day itself hour by honest hour.

The interviewer glances at the clock — theatrically. "Remember: this ships tomorrow. Walk me through how you hit your own NFRs in a day." The question is a pincer, and both jaws are sharp. One candidate uses the deadline as an amnesty — "we'll add monitoring later" — not realizing that later is where internal tools go to become unexplainable. The other candidate ignores the deadline and recites the full enterprise hardening liturgy: compliance frameworks, chaos suites, an eight-week rollout plan for a service that must exist in twenty-four hours. Both fail the same underlying test: rigor and speed are reconciled by right-sizing depth, never by dropping categories.

Critical Insight: The deepest lesson of the one-day constraint is that in the managed-cloud era, most non-functional excellence is procured, not programmed. The Staff skill is knowing the residue — the obligations that remain yours because they encode your system's meaning, which no vendor can know.

The Ledger: What You Inherit Versus What You Owe

Read the inherited column against Section 2's contract and notice how much is already discharged. Durability — the never-lose-a-save covenant — is the managed table replicating across availability zones before acknowledging, an engineering effort that took those platform teams years and takes us a console click (NFR Connection: this is why Section 5's verdict table weighted durability so heavily). Availability at 99.5% sits comfortably beneath the published SLAs of the platforms we stand on. Scaling from midnight-zero to the morning spike is the serverless contract from Section 6. Transport security is a gateway checkbox.