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.

Status: In progress. Shared implementation is internal; standalone adoption is not established.

Use the existing internal shared libraries when adding Factory code. Public consumers continue to use their Module's declared package entry; private source paths remain private.

  1. Validate and copy caller data at the owning boundary before freezing. Select the existing freezing profile by its handling of hidden keys, pre-frozen parents and cycles.
  2. For Milestone dates, pass the owning Module's field reader, instant reader and refusal policy to readMilestoneDate. Keep current-authority, provenance and generation policy in the owner.
  3. Compute Milestone identity through milestoneValueDigest using the owner's canonical hash. Preserve protocol strings and all pinned preimage fields.
  4. For native Promise data, reuse a reviewed observation profile with its original per-call budget, synchronous fault policy and native-property policy. Do not equate observation with validation or permission, reset an allowance during settlement, or substitute different accounting without boundary evidence.
  5. Verify the Module's source and installed consumer, exact import closure and historical replay/drift refusal. Add fresh evidence; never rewrite an old receipt or silently re-pin stored state.

The audit distinguishes equivalent code from behaviour that must remain separate. node --test test/shared-values.test.ts test/promise-observation.test.ts test/module-graph.test.ts checks the shared contracts; the final full check includes affected integrations and package consumers.

Source: docs/how-to/reuse-shared-values.md