Skip to content

v0.2.6

Choose a tag to compare

@github-actions github-actions released this 30 Oct 19:56
· 25 commits to main since this release
v0.2.6
4676660

Release v0.2.6

Durable-record bounds protocol integers at 2^53 - 1 and batches schema validation; role catalog adds draft devsecops, mediaeng and creative prompts and refines secops.

This release tightens contract-defined integer positions across durable-record
v0 and v1 to the I-JSON safe-integer ceiling 9007199254740991
($2^{53} - 1$), formalizes raw-token numeric-domain preflight ahead of binary64
conversion, and batches durable-record schema validation through
goneat validate suite --format json. It also expands the agentic role catalog
with three supplemental draft role prompts (devsecops, mediaeng and
creative) and updates secops (1.1.0) to clarify security-tooling and
continuous-observation boundaries.

Highlights

Durable-record safe-integer wire domain and batched schema controls

  • Protocol safe-integer ceiling. All 53 contract-defined integer schema
    nodes across the 13 durable-record/v0 (record, journal-entry,
    write-receipt, stratum-profile) and durable-record/v1 (record,
    journal-entry, write-receipt, stratum-profile, protection-request,
    protection-receipt, export-request, export-result, body-state-request)
    JSON Schemas declare maximum: 9007199254740991 ($2^{53} - 1$, RFC 7493
    Section 2.2 / RFC 8785 Appendix B) as an explicit protocol interoperability
    restriction. Arbitrary record.payload numbers and the shared general-purpose
    RFC 8785 canonicalizer (scripts/rfc8785-canonicalize.py) are unchanged.
  • Four-stage wire evaluation order. Wire validation runs in ordered stages:
    ingest (RFC 7493 / RFC 8785 syntax, duplicate object-member refusal and
    finite IEEE 754 binary64 parseability), numeric_domain (exact safe-integer
    inspection on raw numeric tokens at protocol integer schema paths before
    floating-point rounding, accepting mathematically integral spellings including
    decimal fractions and canceled exponents within [0, 9007199254740991]
    without expanding huge exponents, while leaving safe negative integers and
    non-numeric JSON types to shape), shape (JSON Schema Draft 2020-12
    validation), and logical semantics.
  • Typed boundaries and counter exhaustion. Implementations MAY use wider
    internal integer types (int64, uint64) and MUST enforce the wire domain
    [minimum, 9007199254740991] at typed APIs, imports and journal boundaries.
    Counter increments (revision, seq, incarnation, and
    seq + group_size - 1) refuse exhaustion at 9007199254740991 without
    wraparound.
  • Batched schema suite validation. scripts/validate-durable-record-fixtures.py
    batches schema checks through goneat validate suite --format json with
    strict 1-to-1 (file, schema) membership and raises RuntimeError on parser,
    numeric-range, schema-load or runner failures so tool errors never satisfy
    negative schema assertions.
  • Control corpus. v0 adds 4 ceiling baseline/reject schema pairs, 1
    canceled-exponent baseline journal and 12 raw NDJSON numeric_domain /
    ingest reject fixtures; v1 grows from 172 vectors, 36 schema rejects and
    75 mutation witnesses to 200 vectors, 45 schema rejects and 76 mutation
    witnesses (including window-above-safe-max, canceled-exponent spellings and
    negative suite-error controls).

Supplemental role prompts (devsecops, mediaeng, creative) and secops 1.1.0

  • devsecops (1.0.0, status: draft, category automation).
    Repository-side security tooling, CI security gates, signing and verification
    automation, credential-lifecycle tooling and supply-chain pinning without live
    secret values, custodianship grants or signing authority.
  • secops (1.1.0). Distinguishes secops from devsecops and
    watcher, routes security-tooling remediation to devsecops while keeping
    general repository software remediation with devlead, and assigns continuous
    observation to watcher or detection tooling rather than a standing-privilege
    secops seat.
  • mediaeng (1.0.0, status: draft, category agentic). Deterministic
    audio, video, graphics, vector, DSP, codec and rendering pipelines with
    explicit signal, timing and color-space invariants, bounded stream/memory
    execution and shell-free external-encoder invocation.
  • creative (1.0.0, status: draft, category agentic). Structured
    musical arrangement, video editing, vector illustration and procedural media
    craft under human artistic direction, explicit asset/provenance hygiene and
    clean boundaries with mediaeng, uxdev, infoarch and secrev.

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-record/v0 and durable-record/v1 implementers: protocol
    integer fields (revision, length, seq, group/group_size,
    incarnation, window, counters, cuts and source pins) are bounded at
    9007199254740991. Journal readers and wire validators must inspect raw
    numeric tokens at protocol integer paths before floating-point conversion and
    map integral or safe-magnitude violations to numeric_domain; stores using
    int64 or uint64 internals must enforce [minimum, 9007199254740991] at
    API, import and journal boundaries and refuse counter exhaustion without
    wraparound. Existing journals and records whose protocol integers lie within
    [0, 9007199254740991] remain valid with unchanged digests.
  • For repositories vendoring durable-record controls:
    scripts/validate-durable-record-fixtures.py imports
    scripts/rfc3339-instant.py and runs batched schema checks via
    goneat validate suite --format json (goneat v0.6.5+).
  • For repositories vendoring role prompts: new supplemental draft prompts
    config/agentic/roles/devsecops.yaml (1.0.0),
    config/agentic/roles/mediaeng.yaml (1.0.0) and
    config/agentic/roles/creative.yaml (1.0.0), plus updated
    config/agentic/roles/secops.yaml (1.1.0), are available under
    config/agentic/roles/. schemas/agentic/v0/role-prompt.schema.json and the
    remaining canonical role prompts are unchanged.

References