Skip to content

Releases: SliceOps/spec

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

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.

SliceOps v1.0.0 — the framework spec

Choose a tag to compare

@anrasi anrasi released this 22 Jun 18:20
446d9b6

SliceOps™ v1.0.0 — the open framework and audit plane for AI-first software engineering. Multi-agent teams ship auditable software, not vibe code.

This release publishes the canonical spec (spec/v1.0.0/):

  • 12 canonical principles (Layer A) in Why→How→What order — spec/v1.0.0/principles.md
  • glossary, topics, and the three-layer IP boundary
  • Layer B reference: entity catalog (13), R-rules, frontmatter schemas, templates, sessions, sizing, model-triage, context-router, development-model, patterns, project-structure
  • governance: roadmap, RFC process, IPR policy, code of conduct, DCO, + sanitized public DecisionRecords

Decision-first and platform-agnostic — runs on any text-based AI agent + git, no specific runtime required (P11). Docs CC BY 4.0, code MIT (DR-2026-06-15).

Dogfooded: the repo runs the consistency validators it publishes on every PR, on a protected main. SliceOps™ trademark pending (EUIPO #019381071) — see TRADEMARK.md.