bd54502a5e
All checks were successful
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 8s
WAI breaking changes and the conformance runner / WAI breaking · does this change touch WAI (pull_request) Successful in 8s
WAI conformance / does this change touch it (pull_request) Successful in 8s
WAI energy receipts / does this change touch it (pull_request) Successful in 7s
WAI conformance / fast integer kernels, every x86_64 kernel set (AVX-512 silicon) (pull_request) Successful in 3m18s
WAI breaking changes and the conformance runner / WAI breaking · wire, record and API against main · linux (pull_request) Successful in 34s
WAI conformance / faces from keypoints under wasm32-wasip2 (wasmtime) (pull_request) Successful in 1m34s
WAI conformance / cross-arch byte-equality · linux (pull_request) Successful in 1m16s
WAI breaking changes and the conformance runner / WAI breaking and conform · their tests, and the independent verifiers through wai conform · linux (pull_request) Successful in 3m3s
WAI conformance / quantum core and corpus under wasm32-wasip2 (wasmtime) (pull_request) Successful in 3m44s
WAI conformance / cargo-class corpora · linux (pull_request) Successful in 17m18s
WAI energy receipts / energy receipts · linux (pull_request) Successful in 18m25s
WAI conformance / cross-arch byte-equality · macos (pull_request) Successful in 1m12s
WAI conformance / codec wrappers · fuzz smoke, text decode limits, C entry points, provenance, the semantic path (pull_request) Successful in 1m45s
standards workspaces build + test / macOS energy backends (pull_request) Successful in 11m49s
WAI conformance / cargo-class corpora · macos (pull_request) Successful in 15m6s
WAI energy receipts / energy receipts · macos (pull_request) Successful in 23m59s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 2m45s
WAI conformance / v2 vocabulary · manifests validate as stated (pull_request) Successful in 23s
standards workspaces build + test / joule-code-rs (joule-code/joule-code-rs, joule-code-rs, linux-arm64, true) (pull_request) Successful in 6m38s
WAI conformance / delivery telemetry · CMCD and CMSD against an independent library (pull_request) Successful in 18s
WAI conformance / cross-arch byte-equality · linux-arm64 (pull_request) Successful in 37s
WAI conformance / C2PA manifest emission · signed, read back, validated (pull_request) Successful in 1m56s
WAI conformance / each feature of the independent verifiers' steps compiles alone (pull_request) Successful in 14m56s
WAI energy receipts / energy receipts · linux-arm64 (pull_request) Successful in 14m8s
WAI conformance / cargo-class corpora · linux-arm64 (pull_request) Successful in 25m1s
WAI conformance / independent verifiers · claims, JWP, key discovery and integer payloads (Python) (pull_request) Successful in 1h24m50s
The README's and the specification's titles carry .WAI™. Bare WAI and every identifier stay as they are. CHARTER.md now says what Appendix C and wai/LICENSE already say about WAI's specification text. Co-Authored-By: Claude Opus 5.5 <[email protected]>
43 lines
3.5 KiB
Markdown
43 lines
3.5 KiB
Markdown
# Charter — Transaction Science Open Standards
|
|
|
|
This charter describes the stewardship pattern that applies to every standard published in this repository. It is short on purpose. The protocols themselves carry the substance; this document captures the operating principles around them.
|
|
|
|
## The pattern
|
|
|
|
Each standard in this repository is published under an open licence — Apache-2.0 for code, CC-BY-4.0 for specification text, except WAI, whose specification text is Apache-2.0 too — and is owned by no one. Transaction Science writes the reference implementation, runs the optional hosted services, and stewards the conformance vectors. The wire format and the right to fork are public.
|
|
|
|
This is the difference between **the protocol** and **the offer**:
|
|
|
|
- **The protocol** is what anyone can implement. It is free, in both senses of the word.
|
|
- **The offer** is what Transaction Science sells: managed deployments of the reference implementation, driver development against the public traits, persistence backends, custody integrations, certification engagement, and the operational scaffolding around real-world deployments.
|
|
|
|
The protocol does not tax money movement, message movement, or compute movement. The optional services are the revenue.
|
|
|
|
## Versioning
|
|
|
|
Each standard versions independently. Tags follow `openpay-v0.1.0`, `smart-byte-v1.0.0-draft.1`, `eoc-v0.2.0`, etc. — the prefix is the subdirectory name. A change in one standard does not bump the others.
|
|
|
|
## Conformance
|
|
|
|
A standard is conformant if it round-trips the published wire vectors. The vectors live under each subdirectory and are signed at release time. Reference implementations are conformant by construction; third-party implementations certify themselves by running the public test suites.
|
|
|
|
## What this charter does not say
|
|
|
|
- It does not assign exclusive authority. Anyone may fork, and a fork is no less legitimate for being a fork.
|
|
- It does not promise a release cadence. Standards advance when the work is done.
|
|
- It does not bind future standards to current ones. A standard added later is bound only by its own conformance vectors and the open-licence requirement.
|
|
|
|
## Adding a standard
|
|
|
|
A new standard joins this repository by:
|
|
|
|
1. Landing in a new top-level subdirectory.
|
|
2. Carrying its own README, LICENSE, and (where applicable) CONTRIBUTING.md.
|
|
3. Being added to the table in the root [`README.md`](README.md).
|
|
4. Inheriting the operating principles in this charter.
|
|
|
|
## Messaging — no vanity metrics
|
|
|
|
Codebase-state numbers (`N crates`, `N tests passing`, `N LOC`, `N+ adapters`) drift on every code change and create permanent sync debt between the website, the GitHub READMEs, and any downstream messaging. Marketing surfaces in this repository describe the **shape** of what's there, not the **size**. Spec versions, algorithm names, RFC numbers, license labels, and other identity-class facts are preserved — they are part of the contract.
|
|
|
|
A scanner enforces this: [`scripts/check-no-vanity-metrics.sh`](scripts/check-no-vanity-metrics.sh), run on every PR and `main` push by the [`repository checks`](.github/workflows/repo-checks.yml) CI workflow. Contributors can wire it into a local pre-commit hook via [`scripts/install-hooks.sh`](scripts/install-hooks.sh). The scanner targets marketing / spec / governance Markdown; historical progress notes, changelogs, and external corpora are exempt by design. Lines that legitimately need a number (a reference to an external spec, codec, or RFC) opt out with `<!-- allow-vanity: <reason> -->` at end of line.
|