Repository navigation
v0.2.8
Release v0.2.8
Defines durable-record (v0 and v1) RFC 3339 instant validation profiles and finite JSON Schema subset admission, deprecates durable-record/v0 for new producers, specifies the durable-record/v1 writer-owned incomplete-append abort boundary and runtime.incarnation_allocation, adds the draft opslead role, and adds workflow supply-chain, key-expiry, and local-path hygiene gates.
This release tightens durable-record (v0 and v1) timestamp validation and
schema-dialect admission, deprecates durable-record/v0 for new stream
production while preserving historical v0 verification, and codifies the
durable-record/v1 writer-owned incomplete-append abort boundary and
incarnation allocation modes (runtime.incarnation_allocation). It also adds
the supplemental draft opslead role prompt and introduces repository gates
for GitHub Actions SHA/digest pinning, release signing-key expiration horizons,
and local-path content hygiene.
Highlights
durable-record (v0 and v1) timestamp profiles, v0 deprecation, and finite JSON Schema subset
- RFC 3339 instant validation profiles. Updates
docs/standards/durable-record-contract.md,
docs/standards/durable-record-v1-contract.md,
scripts/rfc3339-instant.py,scripts/validate-durable-record-fixtures.py,
andscripts/test-durable-record-v1-controls.pyto enforce ASCII-only
([0-9]) RFC 3339 instant validation across everyv0andv1timestamp
position: year bounds0001–9999inclusive (0000and UTC year
underflow/overflow refused), proleptic Gregorian calendar validation,
unconditional:60leap-second refusal, and microsecond fractional precision
(v1requires 6 fractional digits withZ;v0acceptsZor bounded
±HH:MMoffsets< 24:00and no nonzero digit beyond the sixth fractional
place). - Per-position stage evaluation and
v0source/ancestor checks. Documents
the per-position Stage 3 (shape) vs. Stage 4 (instant_spelling/
semantic) evaluation trace, validatesv0journalattimestamps on every
entry of observedv0continuation source and ancestor streams (including
entries beyondcut_seq), validates receivedv1reconciliation
attempted_at,window_covers_from, andwindow_covers_untilpositions, and
adds AST position-deletion mutation witnesses for every timestamp check. - Finite JSON Schema Draft 2020-12 subset admission. Enforces a closed
finite allowlist of JSON Schema Draft 2020-12 keywords across allv0and
v1schemas and rejects sibling assertion keywords alongside$ref. - Deprecation of
durable-record/v0for new producers. Marks
schemas/durable-record/v0/contract.json
as"status": "deprecated"with"superseded_by": "contract: durable-record/v1".
Existingv0schemas, fixtures, and validator controls remain supported for
verifying historicalv0streams andv1continuations.
durable-record/v1 writer-owned incomplete-append abort boundary and runtime.incarnation_allocation
- NDJSON framing and writer-owned incomplete-append abort gate. Clarifies in
docs/standards/durable-record-v1-contract.md
that every committed NDJSON journal entry lineLends with a single LF
(0x0A) without CR (0x0D) and that an unterminated final line (including
k = L - 1missing only the trailing LF) refuses at Stage 1 asingest.
Codifies the completion gate for rolling back a provably incomplete write
(0 <= k < L) in-process under continuous reader and writer exclusion:
verifyingSameFiledescriptor identity on the truncate handle before
truncating, truncating back to the recorded prior-cut byte offset, syncing
the journal file and parent directory, verifying post-truncate byte length via
fstat, and re-validating the prior complete cut (1..cut_seq). - Fail-closed handle poisoning and restart semantics. Requires any
indeterminate commit (k == Lfollowed by a failedfsync,EIO, uncertain
write count, or lost exclusion) or any failure during the abort completion
gate to poison the journal handle in-process against further appends or
dependent body operations until reopen, and defines the disjunctive reopen
oracle across crash points aroundtruncateandfsync. - Incarnation allocation modes (
runtime.incarnation_allocation). Adds
optionalruntime.incarnation_allocation("effect_dependent"|
"prewrite_durable_ledger", permitted only when
deletion.external_bodies == "supported") to
schemas/durable-record/v1/stratum-profile.schema.json,
paired with schema reject fixtures and faultpoint controls in
scripts/test-durable-record-v1-controls.py.
Operations Lead opslead role (1.0.0, draft)
- Adds supplemental
config/agentic/roles/opslead.yaml
(1.0.0,status: draft, categorygovernance, domainsgovernance,
coordination, andautomation) and
docs/catalog/roles/opslead.mdfor accountable
stewardship of estate operating procedures, seat and identity lifecycle
records, and operating-convention baselines, acting through explicit grants
for any privileged step while handing coordination-tool operation to
dispatchand credential, asset, and security-hardening operations to
secopsor a human custodian.
Workflow supply-chain pinning, signing-key expiration horizon, and local-path hygiene
- Workflow supply-chain and permission gate (
scripts/test-workflow-pins.sh).
Verifies that everyuses:reference in.github/workflows/*.ymlis pinned
to a 40-hex commit SHA with a# v...version comment, everycontainer
image carries an immutable@sha256:digest, and top-level and job-level
permissionsblocks stay within read-only defaults except for the release tag
attestation job. - Release signing-key expiration horizon (
check_release_key_expiry).
Extendsscripts/release-env.sh(wired into
scripts/release-derive-anchors.shandscripts/release-verify-anchors.sh
and tested inscripts/test-release-identity.sh) to inspect
docs/security/release-signing-keys.ascandconfig/release/pgp-key-id.txt,
failing closed when the primary key or pinned signing subkey is expired,
revoked, invalid, missing an expiration timestamp on derive, or carrying
ambiguous binding signatures, and emitting a warning on stderr when
expiration is within 30 days. - Local-path content hygiene (
scripts/content-check.py). Scans git-tracked
files for accidental local home paths, macOS/Windows/Linux temporary paths,
andfile://URLs targeting local user directories, wired intomake check.
What a release carries
A crucible release is a GPG-signed annotated Git tag. It publishes no assets,
so there are no SHA256SUMS or SHA512SUMS files to verify. See
docs/security/README.md.
Upgrade notes
- For
durable-recordadopters:durable-record/v0is now marked
"status": "deprecated"("superseded_by": "contract: durable-record/v1")
for new stream production; new streams should targetdurable-record/v1while
retainingv0readers/validators for historical streams and continuation
sources. Verify that implementation timestamp parsers enforce ASCII-only digits
([0-9]), reject year0000(including after UTC offset conversion), and
reject:60leap seconds across bothv0andv1. - For
durable-record/v1external-body stores: Profiles with
deletion.external_bodies: "supported"may now declare
runtime.incarnation_allocation("effect_dependent"or
"prewrite_durable_ledger"; defaults to"effect_dependent"when omitted).