SealLink Conformance Requirements
- Version:
1.0.0-draft.2 - Status:
draft - Normative Language: [RFC2119], [RFC8174]
1. Conformance Roles
An implementation claiming conformance to SealLink v1.0 MUST declare which of the following roles it implements and MUST pass every required specification section, registry invariant, JSON Schema, and conformance vector listed for that role.
| Conformance Role | Required Specifications | Required Registries & Schemas | Required Vector Suites |
|---|---|---|---|
| Core Wire Library | SPEC-00, SPEC-01 | object-types.json, refusal-codes.json, constraints.json, all schemas/*.schema.json | vectors/wire-jcs-and-hashes.json, vectors/constraints-and-schemas.json |
| Tier 1 Verifier | Core Wire + SPEC-02, SPEC-03 (§1–4), SPEC-04, SPEC-05, SPEC-06 (§1–4, §6) | All registry/*.json and schemas/*.schema.json | All vectors/*.json (including trace-01 through trace-04 and refusal-coverage-matrix.json) |
| Effect Executor / Provider | Tier 1 Verifier + SPEC-06 (§5 if bearer sessions enabled), SPEC-07, plus each supported PROFILE-*.md | All registry/*.json, schemas/*.schema.json, and owning profile-*.schema.json | All vectors/*.json plus profile-specific traces (trace-01, trace-03, trace-04) |
| Issuer / Signer | Core Wire + SPEC-02 (§3, §5), SPEC-03 (§1–3, §6), SPEC-05, SPEC-06 (§1, §3) | object-types.json, key-roles.json, opreturn-actions.json, constraints.json | wire-jcs-and-hashes.json, ledger-scripts-and-opreturn.json, constraints-and-schemas.json |
| Institutional / Guardian Authority | Tier 1 Verifier + Issuer + SPEC-04 (full), SPEC-05 (§4–5) | All registry/*.json, origin.schema.json, guardian.schema.json, credential.schema.json | vectors/trace-02-guardian-succession-assent.json, vectors/trace-04-agent-guardian-intake.json |
2. Mandatory Behavioral Requirements
- Deterministic Refusal Ordering: A conforming verifier MUST emit the exact first refusal code prescribed by
SPEC-01 §7,SPEC-05 §4.2, andSPEC-06 §4for every test vector invectors/. - Fail-Closed Unknown Handling: A conforming implementation MUST refuse unregistered
typestrings (WIRE_TYPE), unknown JSON members (WIRE_MEMBER), reserved action byte0x06(CHAIN_FRAME_INVALID), populatedextensions(WIRE_CONSTRAINT), unsupportedScriptPolicytemplates (CHAIN_SCRIPT_UNSUPPORTED), and anyopenconstruct lacking a locally enabled profile. - Zero Silent Repair: A conforming parser MUST reject non-canonical JSON (
WIRE_NOT_CANONICAL) and MUST NOT normalize strings, reorder keys before hashing, coerce integer encodings, or strip unknown members. - No Floating-Point Arithmetic: Conforming implementations MUST NOT route any
uint53,uint64_str, quota debit, rational quorum, or R8.5 aggregate budget sum through IEEE 754 floating-point arithmetic. - Independent Chain Observation: A conforming Tier 1 Verifier MUST NOT accept ledger state, block heights, or UTXO spend status from the presenter or issuer; it MUST query its own read-only tx-indexed node cross-checked against at least one independent comparison node (
SPEC-02 §4).
3. Interoperability Bar for Advancing Specification Maturity
Per SPEC-00 §5.1:
- **
prose->vectors:** Everydecidedrule and every registered refusal code (84/84) is exercised by executable positive, negative, and stateful trace fixtures invectors/, verified automatically by CI via Draft 2020-12 metaschemas and the reference Tier 1 verifier (tools/seallink_verifier.py). - **
vectors->dual-impl:** At least two independent implementations with disjoint cryptographic and JSON stacks pass 100% ofvectors/byte-for-byte (identical object IDs, digests, content addresses, refusal codes, and journal commitments). - **
dual-impl->chain-tested:** All four end-to-end traces (trace-01mail offline + revoke,trace-02initial & successor guardian activation + ward assent,trace-03parent pool + single-use + crash-uncertain + replay + revoke,trace-04ward agent guardian intake) plus TRUC v3 /P2ACPFP package relay (conformance/p2a-regtest/) are executed and recorded against a live Namecoin Corenc28.0regtest (and/or mainnet) network.