SPEC-01 Canonical Envelope
SPEC-01 defines the UAIX canonical publication envelope. It is a portable, evidence-bearing record shape for standards text, handoff payloads, review receipts, public-safe audits, and redaction policies.
Required publication-envelope fields
| Field | Purpose | Current UAI-1 mapping |
|---|---|---|
uaixVersion |
UAIX standards record version. | uai_version |
spec |
Named standard or profile. | profile plus registry entry. |
envelopeId |
Stable record identifier. | message_id |
createdUtc |
UTC creation time. | provenance.issued_at |
issuer, issuerDisplayName, issuerPublicUrl |
Public issuer identity. | source and provenance |
issuerCapabilityLevel |
L0-L6 capability context. | Capability profile body or extension. |
audience |
Intended reader or receiver. | target |
lifecycleState |
Draft, review, accepted, archived, rejected, or superseded state. | delivery.lifecycle or body state. |
trustPosture |
Review-only, unsigned, signed-reference, verified, revoked, disabled, unknown, or local-policy-rejected posture. | trust plus validator/verifier evidence. |
payloadType, payloadSchema, payload |
Typed body content. | body plus registry/schema route. |
evidence, redactions |
Supporting facts and removed sensitive data. | provenance, integrity, body evidence, and extensions. |
signature, signatureStatus, verification |
Signature metadata and verifier result. | trust plus an explicit verifier record; no implied trust. |
exceptions, warnings |
Review notes and non-blocking issues. | Validator issues, conformance result body, or extension records. |
Core rules
- The envelope is portable and evidence-bearing. It is not an execution permit.
- Receivers must validate shape, inspect evidence, apply local policy, and reject missing authority before acting.
- Unsigned records can be useful for review, migration, and public examples. They cannot establish trusted identity.
- Signed records still need verifier output and local trust decisions.