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.

The 3 October refactor replaces sixteen local freezing implementations, three Milestone date readers, two copies of the Milestone identity formula and sixteen Promise walkers with explicit caller profiles with shared libraries. Existing exported Module contracts, stored JSON, command identities, error policy and authority boundaries remain intact. The reference owns helper semantics and build review owns current verification; the prior receipt remains historical evidence. The refinement snapshot preserves the full-run failure and separate corrective proof; PR #99 records the final merge gate.

Why these responsibilities belong together

Freezing is a value operation, rather than a Portfolio, Service or Planning decision. Canonical JSON already belongs to every affected dependency closure, so common freezing adds no transitive source file to pinned collector resources. Its source bytes still change the collector resource digest; old recipes must refuse current dispatch on drift.

Milestones, Research handoffs and work briefs read the same date values and immutable Milestone identities. A shared reader keeps grammar consistent while caller adapters retain errors and bounds. Review, current authority, provenance, predecessor checks and Research's generation-one policy remain in their owning Modules. External consumer fixtures retain independent identity calculations so incompatible changes can still fail.

Promise observers need common implementations for equivalent profiles. Their budgets are part of behaviour. The refactor retains both visit accounting and the Dashboard's caught-fault observation, alongside the existing object/key helper. Fulfilment and rejection share the original allowance. The remaining eight profiles now share a configurable observer after independent old/new differential, multi-root and boundary-order proof. Delivery also observes nested rejection reasons; Subscriptions gains a finite work allowance. Historical receipts retain the previous snapshot.

Deliberate boundaries

Similar codeReason it stays separate
strict-input and Repository Assurance freezingIndependently reviewed delivery boundaries keep their exact importer/export grammar; sharing them requires new boundary evidence.
Producer descriptor freezingIt skips accessors and traverses all own data keys; enumerable/own-key readers have different semantics.
Lifecycle child-first freezingIts pre-frozen-parent shortcut differs from the validated JSON-tree profile.
Dashboard date presentationIt accepts a wider civil date/zone grammar than the Milestone domain reader.
Observer profilesOne shared implementation preserves differing accounting, reset points, descriptor faults and native-property rules. Reflection key-list allocation and owning validators remain separate boundaries.
Module JSON/hash/error wrappersLabels, byte limits, negative-zero rules, failure codes and recorded protocols are owned by each boundary.
Notification envelopeOwnership and delivery already reuse provider-event-body; there is no second encoder to extract.

Remaining technical debt

This is a bounded source refactor, not a debt-free claim. The existing owning issues retain their unresolved work; planned customer capabilities and live adoption gates are separate from code debt.

OwnerVerified gap or next bounded action
Promise observation #58Closed after #102: common finite observer, installed/full checks and exact-main CI passed; historical verification remains immutable.
Neutral packaging #59All four additive neutral profiles are implemented and source-reviewed; installed/browser/full/CI acceptance is underway. Legacy records and authority remain unchanged.
Readability #60Closed after #102: formatting/equivalence, documentation, installed/full checks and exact-main CI passed.
Transient contention #48Reconcile current positive-contention detection and remaining acceptance rather than treating every storage error as retryable.

No live data was changed, no receipt or pin was rewritten, and no external provider or public-site operation was commissioned. Build review owns acceptance; current work is recorded in the private canonical Status.

Source: docs/explanation/shared-values.md