Registered as issue #82; independently reviewed design, implementation remains open. Filing this issue creates no level, grant, runtime policy or schedule. Recovered design owns the complete contract; provenance preserves the original failed review and source hashes. Current E39–E41 remain unchanged.
The owner asked on 2 October 2026 for one Product dial controlling research, inbound work, implementation and marketing. Proposed positions: none, maintenance, low, exploring (the additional pre-fit position), storming, engaged, scaling and sunsetting. A 24-kind matrix supplies mode, cadence, tier ceiling, admitted classes/evidence, purposes, ordinary budget and owner queue rank. Engaged equals storming except the owner row. A level narrows existing authority; it grants nothing.
Owner requests are recorded sources of work. They waive specified score/customer-voice/Factory-novelty evidence only, keeping class or marketing-purpose scope, typed sources, measurement, Supported Assessment where required, grants and limits. Patch/minor dependency updates remain dependency work; routine majors requiring implementation use tech-debt/improvement; typed security remediations use the security floor. No owner request bypasses the class restriction.
Estimate: 7–10 reviewed increments, new Module, low confidence. Registration gives 42 epics, 15 adoption epics and 57–89 increments; E39–E41 are unchanged. All stay open; no delivery date is established. Prerequisite E28; related E14, E21–E27, E29, E32–E33, E36–E38 and E39–E41. E39's architecture delivery mode is a separate owner choice, never inferred from this investment dial.
Acceptance
- [ ] Define a standalone neutral Activity level contract with caller-owned Product identity, clock and storage; immutable owner-attributed revisions; fixed recorded zone; validated digest-pinned policy; pure decisions with complete per-class evidence, class/purpose owner-request answers, ordinary budget and separate effective hard owner cap with absence/provenance. Validate complete week history through the trusted current head, implied unset before a first mid-week set, future-snapshot refusal and unknown ceilings. Sample effective time inside the journal transaction after lock acquisition; refuse clock rollback and preserve replay instants.
- [ ] Wire independently owned consumers through narrow decision ports and current-revision fences, retaining grants, qualifications, source pins and original history. Discovery must use versioned exact Source selection with commissioned bounds, explicit first-party full-rhythm handling, claim/result/replay binding and Capture-novelty deduplication; no private-channel authority follows from class. Gates consume resolved evidence without policy imports; Marketing uses supported purposes/pins; no consumer branches on level names.
- [ ] Independently prove that weekly ordinary budgets and hard caps never enlarge mid-week, all relevant ordinary/reserve usage counts towards hard caps, and floor obligations have a bounded event-driven path. One authoritative shared ledger must serialise reserve/ordinary reservations across Products, link receipts to exact gate admissions, keep unknowns charged and reconcile crashes without redispatch or timed reclaim. Test concurrent Product gates, cap raises/clears, reservation/gate/effect/settlement crashes, two distinct same-month obligations and urgent single-owner-item updates. A one-time cap exception needs a new explicitly scoped owner-signed Budget; silence never grants it.
- [ ] Adopt the Module from a packed external host using documented contracts and substituted collaborators, preserving replay/corruption refusal/Product isolation. Keep proposals bounded, quiet counts unknown without coverage, and sunset notices/actions independently granted under a pinned notice/data plan. Report owner minutes/asks against the Factory bet baseline; local evidence establishes no customer value.
Proof: versioned contracts and register; static policy/subclass fixtures; independent current-byte review; actual packed consumer; complete budget/time/fence/shared-ledger fault matrix; consumer integration evidence; per-level attributed owner counts. The inert prototype proves static table rules only.
Proposed sequence
- AL1a pure contract/policy/resolver and file-driven matrix/resolve; AL1b journal register and saved-request set/show. No consumer or live journal.
- AL5 bounded digest and read-only dashboard; AL4 schedule commission/state revision and collection selection, coordinated with their owning lanes.
- AL7 gate revision shared with R15/E40, authoritative ledger and opportunity/work-item admission; AL2a first proposals and AL3 external adoption.
- AL6 owner queue; AL8 branch health, renewal sources, delivery forecast and Marketing purpose admission; AL2b sunset/remaining proposals when needed. AL9 guarded dashboard writes are optional and outside the estimate.
Owner decisions before any live commission: level vocabulary, floors at none, refreshed Product defaults and share/reserve sizes. Suggested defaults are historical proposals only, based on 29 September evidence. Signature enlargement semantics belongs in S1; actual sunset notice terms wait for that Product's plan.
Coordinator next action: implement the first bounded packet after the required owner choices and independent proof plan. Implementation, current operating-policy changes and live activation are separately scoped work. Historical receipts remain unchanged.
