a437feb8ab
openpay/
compliance/ PCI-DSS readiness package (scope-map,
pci-zero-architecture, hsm-kms-guidance,
qsa-checklist), citing PCI-DSS v4.0.1
requirements. (#1)
examples/pci-zero/ Runnable example demonstrating a deployment
where merchant code never touches a PAN. (#1)
crates/op-core/ Tokenized<Card> typestate + NetworkToken
+ CardNetwork + Cryptogram. (#2)
crates/op-rails-card/network_token/
NetworkTokenProvider trait + VTS adapter
+ MDES adapter, with deterministic stubs
behind a 'live' feature flag. (#2)
crates/op-driver-sdk/conformance/network_token.rs
Conformance harness for third-party
NetworkTokenProvider implementations. (#2)
crates/op-cli/src/ledger/ 'openpay ledger as-of' subcommand for
bi-temporal queries. (#3)
crates/op-orchestrator/src/telemetry.rs
OpenTelemetry span emission per
Payment<S> transition with semantic-
conventions tags. (#3)
docs/observability/ Grafana dashboard JSON + wiring guide
for the bi-temporal ledger lens. (#3)
smart-byte/
smart-byte-rs/ Rust reference implementation: envelope
encode/decode (canonical CBOR + BLAKE3
content addressing), Ed25519 sign +
verify, lockstep BFT commit MVP, Iroh
transport scaffold, CLI. (#4)
spec/identity_and_key_rotation.md
Adopts KERI SAIDs + key-event log
format; explicitly does not adopt ACDC
chaining wholesale. (#5)
conformance/v1/ 21 test vectors covering canonicalisation,
SAID computation, signature verification,
lockstep commit, gossip propagation.
CI gate enforces spec/vector coupling. (#6)
eoc/
eoc-rs/ Rust + WASM reference implementation:
4-stage cascade (cache -> kv -> graph ->
neural), joule counters via RAPL / NVML /
powermetrics, CLI, wasm-bindgen surface.
18 tests pass. (#7)
eoc-bench/ Benchmark harness, MT-Bench and Router
case sets, 'joules per MT-Bench point'
metric, 'eoc-bench run | compare' CLI. (#8)
standards/sci-for-ai-submission.md
Submission proposal mapping EOC's
receipt schema to GSF SCI-for-AI. (#9)
cookbook/ HuggingFace-style cookbook (markdown +
runnable Python) demonstrating EOC's
cascade with HF AI Energy Score. (#9)
docs/bench-v0.md Reproducibility doc for eoc-bench.
Workspace state:
- openpay clippy -- -D warnings: clean across all touched crates
- smart-byte-rs cargo test --workspace + clippy: clean
- eoc-rs cargo test --workspace + clippy: clean (18 tests)
- eoc-bench cargo check --workspace + clippy + 15 tests: clean
Rust 1.95.0 edition 2024 pinned at the open-standards root via
rust-toolchain.toml; every workspace inherits.
Closes #1 #2 #3 #4 #5 #6 #7 #8 #9.
48 lines
2.4 KiB
Markdown
48 lines
2.4 KiB
Markdown
# Smart Byte Conformance Vector Pack — Version Matrix
|
|
|
|
This document tracks the correspondence between vector-pack versions and
|
|
Smart Byte spec versions.
|
|
|
|
## Matrix
|
|
|
|
| Vector pack | Spec version | Spec source | Status | Notes |
|
|
| ----------- | ------------ | ------------------------------------------------------------- | -------- | --------------------------------------------------------------------- |
|
|
| `v1/` | v1.0-draft | `../spec/treatise_v1_parts_I_II_III_combined.md` (Parts I-III) | DRAFT | Reference vectors; expected to be regenerated when `smart-byte-rs` lands. |
|
|
|
|
Future entries are appended below this table when a new spec version is
|
|
introduced. Older entries are never removed; an implementation that pins to
|
|
a historical spec version must be able to look up that version's vector pack
|
|
indefinitely.
|
|
|
|
## Version compatibility rules
|
|
|
|
1. **Per-spec-version vector packs.** Each major spec version has exactly one
|
|
vector pack directory (`v1/`, `v2/`, ...). The pack is the canonical
|
|
conformance suite for that spec version.
|
|
|
|
2. **No backporting of incompatible vectors.** A vector that depends on
|
|
wire-format behaviour introduced in spec v2 is never added to `v1/`.
|
|
|
|
3. **Append-only inside a frozen version.** Once a spec version is frozen,
|
|
its vector pack is append-only: new vectors may be added that exercise
|
|
*additional* corners of the *same* canonical wire format, but no
|
|
existing vector's `expected_*` outputs may be changed.
|
|
|
|
4. **Bug fixes via supersession.** A vector with an `expected_*` field that
|
|
disagrees with the spec is fixed by adding a new vector (with a
|
|
distinguishing `name` suffix) and adding a `"superseded_by": "<new-name>"`
|
|
field to the original. Implementations pin to vector names, not array
|
|
positions, so supersession is non-breaking.
|
|
|
|
5. **Spec-version detection at the wire.** The wire format itself carries
|
|
version information (see spec §8.3, §8.4 — the one-byte algorithm
|
|
identifier is the substrate's wire-version-equivalent for the
|
|
cryptographic primitives). Implementations select the conformance pack
|
|
that matches the wire version they are emitting.
|
|
|
|
## Cross-references
|
|
|
|
- Spec text: `../spec/`
|
|
- Pack contents: `./v1/`
|
|
- Regeneration procedure: `./v1/regeneration.md`
|
|
- CI gate: `../../.github/workflows/conformance.yml`
|