Decisions still requiring explicit ratification
Decisions still requiring explicit ratification
Section titled “Decisions still requiring explicit ratification”These items require explicit owner-level confirmation.
The decisions
Section titled “The decisions”| Decision | Why it matters |
|---|---|
| Final validation strictness for the authoring pack | This determines how much safe freedom juniors actually have |
| Definition-store ownership and API boundary | This determines where versioning, rollback, and visibility checks live |
| First concrete artifact families | This determines what Composer and runtime emission shapes target first |
| Pinax first capability set | This determines the practical first product slices that can be built |
| Artifact panel contract scope | This determines whether AG-UI panel payloads are Composer-only or shared more broadly |
| Runtime rollout order | This determines how aggressively old workflow paths are retired |
| Old-draft retirement wording | This determines how clearly the org stops treating older draft platform docs as current architecture |
The principle behind all of them
Section titled “The principle behind all of them”Each decision affects the documented Nexus model in which most engineers author product files inside governed runtime boundaries.