Accord

    Eziah Accord

    Eziah Accord is the specification system published through Eziah.dev. This page defines its publication model and states no requirements.

    Document model

    Structure
    1. 01

      Specification identity

      A specification has one permanent address. It names the work, carries its release history, and holds no normative text itself.

    2. 02

      Release

      A release is a reviewed package fixed at a point in time. It carries the artifacts actually published with that release, and nothing is assumed on its behalf.

    3. 03

      Evidence

      Evidence is recorded against one exact release and is never aggregated across releases. Each record names the conditions it was produced under.

    4. 04

      Reproduction

      Every release publishes the procedure needed to reproduce its results, with commands and requirements taken verbatim from the package.

    5. 05

      Limits

      Stated limitations and unresolved assumptions are published alongside claims, so a claim is never read as broader than its support.

    Identifier scheme

    Addresses

    A specification identifier addresses the work; a release identifier addresses one reviewed package of it. The two never share an address, so a citation always makes clear whether it refers to the specification or to an exact release.

    Specification
    /specifications/eza-001
    Release
    /releases/eza-001/r001
    Release surfaces
    /releases/eza-001/r001/{specification | evidence | reproduce | limits}

    What publication asserts

    Boundary

    Publication means a package was reviewed and fixed, and that its artifacts are available for inspection and reproduction. It is not a conformance certification, a security guarantee, or a statement of production readiness. Anything a release has not established is recorded on Limits.