Written for: maintainers of an AgentSpaces implementation, and anyone who adds a new one.
Each implementation keeps a vendored copy of golden.json at a fixed path, so every
repository builds and runs its conformance gate standalone and offline:
| Implementation | Vendored copy | Suite |
|---|---|---|
agentspaces/ (Java, the reference) |
tools/golden/golden.json |
GoldenVectorsConformanceTest, GoldenVectorsV0110ConformanceTest, AdversarialVectorsTest, SignedAgentVectorsClusterTest, VoteVectorsConformanceTest, IdsTest, run with -Dgolden.required=true |
agentspaces-python/ |
tests/golden.json |
tests/test_golden.py, tests/test_adversarial.py |
agentspaces-typescript/ |
test/golden.json |
test/golden.test.ts |
agentspaces-rb/ |
gems/agentspaces/test/golden.json |
rake golden:check and the wire-encoding tests |
the AgentSpaces Rust team's agentspaces-rust/ |
crates/agentspaces-wire/tests/golden.json |
ads_golden and the wire tests; the Rust team re-copies golden.json by hand |
golden-examples.json has one copy, in the test resources of the console that generates it,
where the console's GoldenExamplesTest builds each entry, compares the bytes, and decodes it through the
core's strict reader. sync-golden.sh refreshes that copy too, and verify-all.sh refuses when it differs.
This repository's golden.json is the source; the copies are derived. sync-golden.sh refreshes the four owned
copies, and verify-all.sh at the workspace root refuses when any of the four owned copies differs. Nobody edits a
vector by hand: the generator (agentspaces/tools/golden/GoldenVectors.java, which needs the Java
classes and so lives with them) reloads the fixed key material from the existing file, adds or
changes only the vectors whose inputs changed, and writes here; see
agentspaces/docs/BUILD-ENVIRONMENTS.md for the incantation.
A new implementation copies golden.json the same way, reproduces every entry the vectors lists under
"Reproduce exactly", and refuses every adv_* entry. TECH-SPEC.md §10 is its checklist.