Approvals & deliverables

The deliverable ladder runs: NDA → technical proposal → commercial proposal → techno-commercial → contract.

Each rung unlocks when its inputs exist and its named approvals are recorded. Two properties matter:

• Gates are server-enforced. A locked rung isn’t a greyed button — the server refuses to produce the artifact (with the missing approval names) until the ladder says otherwise. The priced client submission cannot exist without its technical and commercial approvals on record.
• The review draft is deliberately ungated. It’s the document a human reads in order to approve — approval gates what leaves the building, not what you review internally.

Every approval records who, what and when, in a trail the application role cannot delete from.