03.2 / Yukh system / Projects
Declared state. Deterministic reconciliation.
Yukh Projects makes portfolio and delivery state durable, reviewable and independent from any single agent, session or consumer.
Status: published and synthetically qualified. Yukh Projects v1.7.0 includes a controlled-apply profile, but no live qualification or apply has occurred.
The problem
When planning state lives inside chats, local notes or tool-specific automation, parallel participants cannot reliably discover ownership, priority, dependencies or the accepted outcome.
Responsibility
Reconcile declared project configuration with GitHub Projects through deterministic plans, bounded mutations and verifiable postconditions.
Authority boundary
Projects owns declared portfolio and delivery state. It does not coordinate live participants, grant execution authority or treat a message as an accepted project mutation.
Public contracts
- Desired state: consumer-neutral declarations of project structure and policy.
- Plan: the deterministic difference between declared and observed state.
- Apply result: bounded mutations with stable identifiers and diagnostics.
- Postconditions: evidence that observed state now satisfies the declaration.
How it interacts
Coordination announces who is acting on a plan and carries review signals. MCP can expose reconciliation as a governed capability. Projects remains the durable source of delivery truth.
Next direction
Perform a separately authorized live qualification, then require a fresh exact approval for any live apply. Publication and synthetic convergence evidence do not authorize consumer migration or mutation.