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.

Historical bounded qualification, 3 October 2026: independent source and retained installed stage evidence passed, as did the 7/7 native concert. This supersedes earlier source/package-pending statements below for that bounded profile. Historical 7cf combined full checks and independent evidence acceptance passed for the bounded local profile; complete stress/adoption matrices, exact-final-head CI and live commissioning remain separate. Reviewed scope.

See the input → responsibility → output diagram.

What it does for you: Each registered project can keep up to eight core values. Each value is a few words plus the rule it applies when choosing between development options, each part up to 280 characters. You add and edit them on the project's Core values page in the Dashboard. Every accepted save becomes a new revision, up to 500 per project, and earlier revisions stay exactly as they were. Anything that later cites a revision by number and digest gets back exactly that revision, whatever was edited since: it holds plumb however later edits swing. If a save is not confirmed, the page keeps your draft and offers to retry the same operation, so nothing is recorded twice; if someone else saved first, your draft is kept and, once the current values can be read, both are shown.

A slender violet bob with a map and compass.

Meet the navigator. Keep the agreed direction in view. Keeps versioned project values so guidance can be named precisely. Meet the whole Plumb family.

How it links: Records every revision in the Command journal. An independent caller can supply its own registered project identities without creating a Git checkout; Factory keeps using Portfolio through the compatible adapter · Gives current values, history and exact revisions to the Dashboard. Nothing else reads them yet.

Honest limits:

  • Optional Knowledge planning advice reads an exact current Guidance revision and retains its original pin. Values grant no permission to deliver and change no acceptance, budget or safety rule. An empty list blocks nothing.
  • A revision records where the words came from (typed directly, or summarised from a document), not who wrote them. Damaged records are refused rather than shown, but someone with write access to the journal file could rewrite them consistently.
  • An unsaved draft lives only on the open page: reloading or leaving loses it. The page shows the newest ten revisions; older ones are kept but not shown.
  • Reading recorded values checks the history through the revision captured when the read began. If another editor commits during that read, it can return the captured revision. Later events without a valid aggregate that accounts for them are refused; the reader never repairs records. Nothing is measured for speed, and there is no way past the 500-revision limit yet.

New saves use version 2. Older revisions, their digests and every pin keep their original meaning. Once a project has a version-2 save, it needs the upgraded reader; an older reader refuses its saved history and edits. No live Factory guidance has been migrated.

Status: The existing local domain and browser interface were accepted with Required actions and blockers. The caller-owned identity package has a local external-consumer proof. It and the eight-value change passed independent Astra review and were merged on 1 October 2026 after an Opus 5.5 review and accepted locally the same day by the owner-designated acceptance reviewer after a Fable 5.1 review; the complete adoption gate remains open. Acceptance and evidence.

Contract and limits

New save commands use a guidance- identity; the dashboard already supplies it. Recorded older commands retain exact replay. See the command contract.

The narrow surplus-history correction, including the 500-revision check, is merged. Its additive record records independent qualification and preserves earlier acceptance separately; required merged-main verification remains open.

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

A separately authored v3 candidate records complete owner rationale together with values in one revision. It requires an exact, current owner decision and a qualified caller fence. Existing values, pins and recorded saves stay unchanged; the existing Dashboard editor becomes read-only after explicit migration. Independent source and earlier installed adapters/UI evidence retain their original pins. 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. No live Product is migrated. Atomic contract and adapter inventory.

A dated recollection supplement can retain a later owner explanation without inventing what was recorded originally. The separate candidate requires an exact owner decision and current READ, keeps its own bounded append-only history, and leaves the original values, rationale and pins unchanged. Supplement contract.

Source: docs/guide/project-guidance.md