mosaicstack/stack
1
0
Fork 0
Code Issues 47 Pull Requests 1 Actions Packages Projects Releases 15 Wiki Activity

Native Kanban/SOT canonical contract and P0-P3 delivery plan #751

New Issue
Closed
opened 2026-07-14 15:59:37 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-07-14 15:59:37 +00:00
Owner
Copy Link

Objective

Publish the owner-ratified Native Kanban/SOT requirements, mission manifest, dependency-ordered task decomposition, and frozen shared contracts before implementation begins.

Fixed invariants

  • PostgreSQL is the sole writable SOT.
  • Mutations fail closed when write health is unproven.
  • Generated exports are non-authoritative and never import sources.
  • Outage notes return only as attributable post-recovery proposals.
  • Coordinator is mechanical/non-LLM and cannot invent scope, waive gates, certify, or merge.
  • Certifier is the final independent gate and has no merge authority.

Acceptance criteria

  • Requirements and all seven owner decisions are canonical on main.
  • Mission roles, gates, and authority boundaries are explicit.
  • P0-P3 slices have non-overlapping file ownership and dependencies.
  • Drizzle schema, Coordinator interface, health/error model, recovery profiles, and N-1 migration map are frozen and type-checked.
  • Independent author-not-reviewer review clears KCR-001 through KCR-016.
  • PR is squash-merged to main with terminal-green Mosaic CI.

Implementation remains held until this canonical publication is merged.

## Objective Publish the owner-ratified Native Kanban/SOT requirements, mission manifest, dependency-ordered task decomposition, and frozen shared contracts before implementation begins. ## Fixed invariants - PostgreSQL is the sole writable SOT. - Mutations fail closed when write health is unproven. - Generated exports are non-authoritative and never import sources. - Outage notes return only as attributable post-recovery proposals. - Coordinator is mechanical/non-LLM and cannot invent scope, waive gates, certify, or merge. - Certifier is the final independent gate and has no merge authority. ## Acceptance criteria - [ ] Requirements and all seven owner decisions are canonical on main. - [ ] Mission roles, gates, and authority boundaries are explicit. - [ ] P0-P3 slices have non-overlapping file ownership and dependencies. - [ ] Drizzle schema, Coordinator interface, health/error model, recovery profiles, and N-1 migration map are frozen and type-checked. - [ ] Independent author-not-reviewer review clears KCR-001 through KCR-016. - [ ] PR is squash-merged to main with terminal-green Mosaic CI. Implementation remains held until this canonical publication is merged.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#751
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?