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.
In progress: M01 source candidate. Original source review remains separately pinned; historical 7cf actual installed/package integration and independent local evidence acceptance passed. A commissioned owner UI remains separate. This private entry records intent; it does not run Research, create tickets, schedule work or publish a release.
Supply the original host
import { createMilestones } from 'software-factory/milestone-objectives';
// All three values belong to one explicitly commissioned caller host.
export function milestones({ journal, commission, fence }) {
return createMilestones({ journal, commission, fence });
}
The caller supplies the actual CommandJournal and a persisted original commission: protocol sf-milestone-commission/1, profile m01/1, commission ID, Product/namespace/store scope, host binding ID and original allowance reference. Construction is passive. Missing or replaced storage, a changed commission or an unqualified host must refuse; opening a fresh namespace is not recovery or a renewed allowance.
Use the original unoverridden Journal class methods. The facade checks their descriptors before and after caller work. The fence's binding holds that exact Journal handle and commission; its synchronous run(request, invocation, decide) owns a real, non-expiring local lock through current authority lookup, history inspection and Journal commit. It supplies those exact binding/request/invocation references in the frame. The caller must independently qualify the physical store incarnation and lock owner, and make every authority, values, operating-policy and milestone writer participate. JSON assertions alone do not establish this. A constructor that receives arbitrary collaborators cannot authenticate a hostile host.
Two disposable qualification arrangements are exercised: a SQLite authority/commission registry and a private JSON registry, each guarded by a native SQLite immediate transaction. These are examples, not an included default store or a claim about a distributed transaction.
Retain the original envelope
execute({actorId}, request) receives trusted authenticated context separately from untrusted request data. A request has protocol sf-milestone-command/1, a bounded original request ID, expected aggregate version and one action: submit, revise, select-primary, admit-plan, cancel or record-completion.
Submit needs title, objective, optional guidance represented as null, zero to eight criteria, desired-target declaration and caller-resolved original provenance/values/policy/allowance pins. Zero criteria is useful draft intent: completion remains unknown and plan admission refuses. Owner UI should not expose storage, fence or allowance mechanics. Product values and operating policy remain separate from achievement guidance.
The caller must retain the complete expanded request and original actor context before invoking. After lost acknowledgement, restart or current-pin drift, repeat those same bytes and ID; do not reconstruct them from current facts. Scope plus request ID derives sfmilestone: followed by 64 lowercase hex characters. A changed payload conflicts; original replay under current READ authority consumes no allowance and must retrieve the actual Journal receipt. Historical authorised evidence survives outer acknowledgement faults, while success remains refused. A possible new commit returns UNKNOWN_COMMIT; it never permits an automatic fresh-ID retry.
READ permission gates all disclosure. A new change needs current mutation authority. Changed current values/policy blocks selection and plan admission; a deliberate revision adopts current pins while retaining all old revisions. Clearing/cancelling remains possible under current permission. Revision and cancellation never erase history or reset allowances. A primary selection is explicit and nullable; it does not expire or suppress upkeep lanes. The frame reports the caller's current maintenance/security/recovery/improvement policy without inventing allocation percentages.
Read plans and dates honestly
list returns a compact catalogue; plans lists immutable reviewed plan summaries; inspect selects an exact historical revision/plan or the latest for that revision. Page cursors bind the aggregate version and original identities. Pages contain whole items; stale cursors refuse. Reads do not create an aggregate, receipt, completion observation or work item.
Plan generations have exact content pins, original revision, criteria, dependencies, prior generation and source references. The current qualified review must name the exact proposal digest. Admission is a reviewed plan only: Research and implementation are unavailable; work coverage is not bound. Existing jobs, budgets and ownership ledgers are unchanged.
A completion records qualified facts for one original criteria/values/policy revision. Historical completion is separate from current satisfaction, which can become unknown after drift or unavailable current evidence. App Store submission, approval and live availability would be different observed facts, never inferred stages.
Planning inputs are exact native Temporal/Capacity values, parsed and re-evaluated at the locked observation time. Product/namespace, freshness, conflicts, constraints and source references remain native. Native expected-date disagreements stay conflicts; unknown projections retain the supplied/evaluated plan and claim references. A usable date is only an attributed source claim with an exclusive validity cutoff, never a commitment or aggregated resource ETA.
Opaque shared-scenario/account/window/exposure/reserve/profile pins are retained declarations: they do not authenticate or comparatively bind the native Capacity account/profile content. The original native forecast digest and count remain unchanged while valid; native re-evaluation checks freshness without refreshing the original forecast lifetime. After expiry the count is unknown and the original digest remains; reasons include opaque-resource-binding-unqualified. Combined resource assessment is not derived. No summing cycle durations, parallel DAG schedule, capacity reservation or third-party review-time promise is provided.
Bounds and refusal
Limits intersect and refuse before writing, never truncate: eight milestones, 16 revisions total/eight per milestone, 16 plans, 32 stable subobjective IDs/128 generations/four per ID, eight criteria/dependencies, depth16 and 32 plan sources. Canonical JSON byte limits include escapes: title160, objective2000, guidance4000, criterion/cancellation512, generation2048, completion8192 and forecast4096. Request/frame/command/event/result are64KiB; state1MiB; JSON depth32.
Growth stops at96 commands or768KiB state. Closure reserves32 slots/256KiB for at most16 first completions, eight cancellations and one final primary clear (25 obligations). No reset or eviction replenishes these limits. Every transition has one event; replay has none. Reads replay at most eight pages of16 events plus a one-row overflow sentinel. A page returns at most eight complete rows within its64KiB success envelope.
Fixed refusal codes are INVALID, LIMIT, CONFLICT, STALE, FORBIDDEN, UNAVAILABLE, CORRUPT and UNKNOWN_COMMIT. Native Promise data, including fulfilled nested/symbol values, is observed within bounded descriptor traversal but never awaited as authority or accepted as synchronous data. Accessors and generic thenables are never invoked. Raw collaborator errors are not returned.
See Journal adoption, Temporal planning and Capacity planning. No default store, Workflow/model/network port, live release or external service qualification is included.
