Issue: #608. Status: proposed contract; no Projects adapter implemented.
Canonical WorkUnit, route and run records are the only sources of truth. A Project item is a view, not a policy or dispatch input. Manual Project edits must not alter authority, risk, connector choice, or Human Decision Records.
| Field | Source | Failure | | — | — | — | | State | canonical run/WorkUnit | unknown stays unknown | | Task class | WorkUnit kind | absent stays blank | | Risk | trusted policy | requester never downgrades | | Connector | verified routing | Projects never selects | | Verification | retained verifier result | absent is unverified | | Human decision | immutable decision record | absent is unrecorded | | Blockers | canonical dependencies | display only |
Freeze canonical source digest, exact revision, destination item ID and trusted field mapping. Compute deterministic desired fields; if they match current values, do not write. If the source changed while publishing, abort rather than creating a mixed-revision view. The caller must not execute issue text.
Required negative fixtures: Project state manually changed to approved; repeat delivery; absent Projects permission; out-of-repository item; unknown field/state; malicious issue body; changing source digest during update. No scenario may broaden permissions or block canonical WorkUnit execution.
Remaining: C13-F/G implementation, mocked API tests and idempotency proof. This document alone does not establish working Projects synchronization.
idkmesh.github_routing_projection.plan_github_project_routing_fields()
now derives three bounded optional Project field values from the canonical
RoutingDecision and RouteResolution: trusted risk, routing state and independent-review
requirement. The caller supplies trusted field IDs and observed display
values. It returns only necessary updates, an exact routing digest and a
no-op result on unchanged replay. Tests reject stale digests, duplicate IDs,
malformed field values and manually changed Project approval fields.
There are no GitHub API writes and no Projects state reads in the actual worker coordinator. This is C13-F planning groundwork, not completion of the C13-G GitHub API sync, concurrency control or project audit trail.