Skip to content

v0.2.3

Choose a tag to compare

@github-actions github-actions released this 27 Oct 21:51
· 38 commits to main since this release
v0.2.3
0a93e24

Release v0.2.3

Durable-record/v1 gains continuation streams and restriction review.

This release adds a journal representation for reviewing restrictions on a
stream that re-records another stream's content, so that pending review
travels with the journal instead of living in implementation state. It also
clarifies four checks in the draft repository-classes standard. The change to
durable-record/v1 adds fields and an entry type; existing v1 records, digests
and pins are unchanged. The v0 family and every other contract family are
unchanged.

Highlights

Durable-record/v1 continuation streams and restriction review

  • Continuation. A v1 stream that re-records content from another stream
    declares continues on stream_opened: the source journal's capability
    (contract: durable-record/v0 or contract: durable-record/v1), its stream
    and a source cut. Each re-recorded appended or revised entry carries
    imported_from, the exact source pin it re-records.
  • Cut digest. A source cut is named by cut_seq, which ends a complete
    group, and cut_digest, the SHA-256 of the RFC 8785 JCS bytes of the source
    entries through that cut as one array. It binds history; it does not by
    itself prove the cut is current.
  • restrictions_reviewed. A new journal entry type, its own atomic group,
    covering the destination cut immediately before it. It binds the reviewed
    source cut, a digest of the effective source restriction manifest
    (qualified holds, retirements and inherited reviews), a digest of the
    destination's applied manifest, an authorization reference and provenance.
    A review's source cut may advance beyond the opening cut, provided the
    opening prefix is unchanged.
  • Serving fails closed. Serve, export and reuse of a continuation are
    refused as restrictions_pending until a current review exists. A later
    import, a destination tombstoned, untombstoned or retired entry, or a
    change in the effective restrictions of the source or any ancestor makes
    review pending again; ordinary destination content writes do not. The
    manifests describe effective state, not event history.
  • Observed sources are validated. Every observed source and ancestor
    journal is checked under its own family before its restriction state is
    used. An invalid or malformed source is refused as continuation.

New refusals are restrictions_pending and continuation. The v1 logical
controls grow from 92 vectors, 21 schema rejects and 34 mutation witnesses to
124, 25 and 53. Guards that have a vector but no single-guard mutation witness
are named in the checker.

These are logical fixture controls. They qualify no store. Mapping source
restrictions to re-recorded destination pins, authorization, authoritative
observation of the source, and serializing the currency check with release
remain adopter duties.

Repository classes clarifications (draft 0.1.1)

  • C5: a version subcommand with --extended is required; a
    --version flag alone does not satisfy C5. Each reporting verb is checked
    with --format json, or without the flag when JSON is its only output. A
    verb whose stdout is the transformed artifact is exempt if the CLI has a
    JSON reporting verb.
  • C3: test-only and harness variables count.
  • C4: a repo whose release ceremony needs host tools SHOULD also provide
    make doctor; it is not in the minimum target set.
  • P1: the @3leaps/ npm scope is the reservation. For PyPI, the README
    names the intended distribution.

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/v1 implementers: a store that re-records content from
    another stream declares continues, marks imports with imported_from and
    appends restrictions_reviewed before serving that stream. A store with no
    continuation streams needs no change. Existing v1 journals remain valid.
  • For classed repositories: a CLI needs a version subcommand to meet C5.
  • durable-record v0 and every other contract family are unchanged.

References