Skip to content

SliceOps Spec v1.1.0 — author ≠ approver ratified, evidence.v1 canonical

Latest

Choose a tag to compare

@anrasi anrasi released this 02 Jul 02:39
d49311e

The first minor version of the SliceOps framework specification, cut per the spec's own versioning policy: spec/v1.1.0/ is the current spec; spec/v1.0.0/ is retained, byte-untouched, for audit.

P3 — author ≠ approver, now normative

P3 (Human-in-the-Loop Authority) gains a ratified implication: the DEC schema records the ratifying human in approver; in projects with more than one maintainer, approver MUST differ from owner; single-maintainer projects MUST record self-ratification explicitly (approver == owner) — a disclosed limitation, not a silent one. Ratified 2026-07-02 via DR-2026-07-02-author-approver-separation (see its Ratification note for the field-level wording adjustment approved at ratification).

evidence.v1 — canonical

The canonical evidence record format (reference/evidence/) upstreamed as Layer B.1, now with its glossary entry: JSON Schema draft 2020-12 served at its $id (https://sliceops.org/schemas/evidence/evidence.v1.schema.json), P6/P7 category mapping machine-enforced on slice-merge records, vendor extensions namespaced (Layer C), golden examples, and an honest signing story (no embedded signature in v1; detached attestation over the artifact bundle). Validated by toolkit v0.2.0 check #10.

Full details in the CHANGELOG.