| 1 | Corpus bytes come from stellar-core or the network. Each entry is a LedgerCloseMeta (or a smaller XDR value) emitted by stellar-core 30.0.0 on a local standalone node, imported from stellar-core’s own --check-lcm goldens, or copied unmodified from the public SEP-54 data lake. Bytes built by hand are marked synthetic: true with the reason | A failure is a failure on bytes your reader can receive. The corpus is not a fuzzer |
| 2 | Expected values never come from a reader under test. They come from the bytes (rs-stellar-xdr 30.0.0, the oracle), from hand-written pinpoints, and from a reference extractor that reads LedgerEntryChanges and consensus events, never the envelope | Your SDK or indexer cannot pass by agreeing with itself or with another SDK. A driver or adapter never sees the expected values |
| 3 | Your indexer runs unmodified, through an input it already reads. The harness serves ledgers as a SEP-54 (Galexie) data lake on disk or behind an S3-compatible store, or as a mock stellar-rpc getLedgers | No test hook in your code. The same ledgers reach your indexer the way production ledgers do |
| 4 | Verdicts are computed from what your indexer stored. An adapter reads your database rows or exported files back and reports them as neutral observations. The harness decodes stored addresses itself and compares exact values. Log text is never parsed | A wrong row is caught even when your indexer logs nothing. A crash, a halt and a silent drop are told apart |
| 5 | Known defects are declared data. An entry names the target, the version range and the expected outcome of each known divergence. Inside the range the outcome must be observed; outside it the entry must pass | Your CI fails on a new divergence, and also when a declared defect stops reproducing. A fix is confirmed, not assumed |
| 6 | Everything is pinned, and every check runs offline after one fetch. pins.toml names every version and image digest; make fetch downloads them once; OFFLINE=1 runs a check in a network namespace with only loopback | A run is reproducible. A check that needs the network fails instead of fetching silently |
| 7 | One make target per check, and the same target in CI. | You can run locally exactly what CI runs, and read its report |
| 8 | Unknown input fails closed. The oracle refuses a ledger above protocol 30 or a LedgerCloseMeta arm above v2; drivers report an unknown arm as union_arm_undeclared | A protocol upgrade shows up as a named failure, never as a silently skipped entry |