| Filename | Latest commit message | Latest commit date |
|---|---|---|
4f91795f10
The JcpGate landed as code; this makes it part of the
standard.
SPEC §5.1 (OPTIONAL) — the JCP binding, normatively:
tier as action a stage is consulted only if the
chain's leaf grant names its verb;
no l4 in the chain → no remote
frontier agent, structurally
energy as budget each consultation debits the tier's
§1.1 class marker (µJ: 1 / 10 / 10³ /
10⁶ / 10⁷, honest Estimator) from
EVERY link of the chain
denial as fallthrough
every consultation seals as a chained JCR-1 receipt with
machine-readable deny reasons
Readiness: Solid — the jcp runtime and chained receipts
exist today; the binding is composition.
CONFORMANCE C5 — gated_cascade_vectors.json (6 vectors)
Unlike C1–C4's wire round-trips, C5 runs the REAL jcp
runtime end to end: fixed fixture identities (issuer
[1;32], agent [2;32], steward [7;32]) + fixed per-tier
costs make every vector deterministic. Each vector
pins closing tiers per run, total µJ debit, and the
sealed verdict sequence:
ungranted l4 denied even when it would close
granted l4 closes and debits its class (10_000_010)
exhausted budget stops the escape hatch on run 2
(deny sealed with reason budget-exceeded)
earlier close → later tiers never consulted
denied probe still reaches a granted deeper tier
(l2 deny + l3 allow in one walk)
repeated cheap closes accumulate exact debits (3×10)
verify_gated_cascade extracts every sealed receipt and
compares verdicts AND deny-reason strings — a denial is
evidence, not a silent skip, and the suite proves it.
Pack: 24 passed, 0 failed. Workspace: 33 green.
Co-Authored-By: Claude Fable 5 <[email protected]>
|
||
| .. | ||
| cascade_vectors.json | ||
| coding_op_vectors.json | ||
| gated_cascade_vectors.json | ||
| README.md | ||
| receipt_vectors.json | ||
| regeneration.md | ||
| signature_vectors.json | ||
Joule Code v1 Conformance Vectors
The v0.1 conformance suite (../../SPEC.md §8). Four suites:
| File | Suite | Checks |
|---|---|---|
coding_op_vectors.json |
C1 — content addressing | reproduce op_id from the canonical CBOR of each CodingOp |
signature_vectors.json |
C2 — signing | verify/reproduce each Ed25519 signature; reject every negative |
receipt_vectors.json |
C3 — receipt | reproduce/verify each receipt signature; honor the provenance↔measured coupling |
cascade_vectors.json |
C4 — cascade | given scripted stage outcomes, select the same closing tier (stop-at-first-close) |
Run against the reference library:
cargo run -p joule-code-conformance -- verify .
All derived fields are real, cryptographically computed values — the content addresses (op_id) are BLAKE3 over canonical CBOR, and every signature is a genuine Ed25519 signature, regenerated against joule-code-rs (see regeneration.md). The signature_vectors.json known-answer cases use RFC 8032 keys. The harness passes this pack with no skipped vectors.