Factory docs, home
Page navigation

Historical local qualification: Source 7cf4b26e focused Core 22/22 and Dashboard 26/26 checks passed. The historical bounded local record keeps their exact scope. Historical source 7cf4b26e passed the 3,286/3,286 full checks and all 36 installed families. Independent bounded local evidence acceptance passed; exact-final-head CI is recorded separately from this frozen local proof. Module-specific and broader limits remain below.

See the input → responsibility → output diagram.

Status: In progress. The structural-bound correction keeps its focused source checks and independent review. Historical source 7cf4b26e passed the 3,286/3,286 full checks and all 36 installed families. Independent bounded local evidence acceptance passed; exact-final-head CI is recorded separately from this frozen local proof.

A plan already contains titles, intended outcomes, achievement criteria and dependencies. A caller can copy one selected implementation generation into a readable work brief without asking the owner to enter those details again. Optional reviewed additions can explain an affected capability, possible disproof or non-goals.

The brief keeps the exact captured dates and capacity counts alongside their sources, unknowns and conflicts. It does not turn a count into a delivery date or promise that a dependency is satisfied. Each page retains its own observation time; several pages are not one atomic trajectory snapshot.

A brief remains unadmitted. Actual implementation tickets need a separately qualified work owner, current permission and original effect identity. Creating or rereading a brief starts no Research, implementation, verification, release or model task. Maintenance, security, incident recovery and improvement keep their existing independent policy.

Honest limits:

  • A copied snapshot and its digest do not authenticate plan membership, approval or current authority. The caller obtains data through the existing qualified milestone reader.
  • Historical, cancelled or stale data stays labelled as captured. Global primary eligibility can describe a different milestone and never means this generation is ready.
  • Work admission, dispatch, dependency satisfaction and an aggregate resource ETA remain unavailable. Source preparation is not package, UI, live or release acceptance.

See the adoption guide for the small input and the module reference for exact bounds.

Shared value implementation: common contracts. Owning errors, limits, stored identities and authority remain as specified above.

Source: docs/guide/milestone-work-brief.md