Status: T36.1 accepted locally on 1 October 2026; reviews and checks: integration evidence · component evidence · acceptance receipt · build review. The accepted contract covers only pure dates/dependency evaluation; full design retains separate capacity and material timing scope, plus future durable proposal and delivery scope.
Open gates: E36 remains open (durable proposals and reliable delivery); CI on these bytes and publication are not established; a resolution policy or durable lifecycle needs another reviewed version.
Factory consumers: none. No Factory module, command or Dashboard route calls it; only its tests and the installed-package consumer do.
Intelligence: none — Dates and constraints are a deterministic evaluation of caller-owned evidence, precision and policy; no model can establish an occurrence or grant authority.
Source: contract, evaluator. Tests: semantics/refusals/history, external consumer, package helper, graph. Adoption: complete installed API/guide.
The entry is software-factory/temporal-planning. Inputs/policy/asOf are caller-owned values; the evaluator has no collaborators to contact or storage to own. Public parsers validate strict protocol versions and bounded JSON, preserve exact error class identity and return deeply frozen copies. parseTemporalPlan reproduces fixed-v1 semantics with the stored time/policy, without current zone lookup or clock access; bad digests or recomputed-but-altered assessments refuse as CORRUPT.
Invariants: scopes and source pins match exactly; unknown is not zero; source alternatives remain attributed and unranked; civil precision is never a UTC appointment; observed future/straddling instants and all civil observations are unusable in v1; every subject dependency edge participates in the DAG; withdrawals/expiry remain visible. No result grants authority, promises delivery, mutates a Commitment or starts an effect.
The pure compiler closure is temporal-planning/contract, calendar, canonical-json, strict-input and errors, plus node:buffer/crypto. Reporting vocabulary is type-only. There is no Journal, Portfolio, Git, filesystem, process, provider, scheduler or model dependency. Keep legacy calendar/reporting behaviour and all old artefacts/receipts unchanged. Adding a resolution policy or durable lifecycle requires another reviewed packet/version, not a silent v1 change.
Shared value implementation: common contracts. Owning errors, limits, stored identities and authority remain as specified above.
