Factory docs, home
Page navigation

Pre-release documentation. Proposed designs are labelled in the page; acceptance evidence is maintained in the build review. Local paths appear as placeholders. Current state: Build review.

Save the values that should guide decisions for one registered Product. Open its project page in the local dashboard, then open the values editor. Add or edit a statement and its application rule, review the order, and save.

Confirm that the page shows your saved values and a new revision. Each Product supports up to eight values. If another editor saved first, compare both versions and explicitly choose which draft to keep. An uncertain save retains its operation ID for a safe retry.

Before the first guidance save made with the current code on a journal that older servers or worktrees also read, rehearse it on a copy. Every new save writes the new revision format, even one of six or fewer values, and older servers cannot read it.

Saved values do not yet feed an automatic planner. For the exact storage and pinning contract, use the Project guidance reference.

Storage

See the storage contract.

Provenance

See the provenance contract.

API

See the api contract.

Commands

See the commands contract.

Integrity

See the integrity contract.

For future briefs

See the for future briefs contract.

Tests

See the tests contract.

API callers: the command contract covers new save identities and retries of older commands.

New saves use the versioned eight-value format. Previous revisions and pins stay unchanged. The eight-value implementation was accepted locally; the narrow surplus-history correction passed independent review and focused checks including the later-version bound; integration and required CI remain pending. No live Factory values were migrated.

Source: docs/project-guidance.md