two-recordslisted

# Two Records Build Standard **Spec:** AIP-BS-TWO-RECORDS · **Version:** 2026-09-26 · **Canonical:** https://aipathway.com.au/explore-ai/two-records-build-standard Open specification: making two systems of record agree without a machine deciding which is right. A declared pair contract naming both sources, the shared key and the master per field; joins on ids never labels; a matched pair silent and a mismatch a Difference object with both values; nothing corrected without a named person's acceptance; orphans and tolerances as declared objects; a run that publishes on schedule including the all-clear; history kept on every fix. Free to implement, with a conformance checklist. ## Read the standard first The full specification is in `reference/two-records.md` in this skill. Read it before writing code. It is about 3,000 words and it is the whole job: the checks in order, the objects with their fields, what must never be automated, and a pass test. For the current version, fetch https://aipathway.com.au/explore-ai/two-records-build-standard.md. This copy is 2026-09-26. The checks are also structured data, so you do not have to infer a test plan from the prose: https://aipathway.com.au/explore-ai/two-records-build-standard/checks.json gives each check a stable id, the ports it observes, what to inject and what to assert. `npx @aipathway/conformance show two-records-build-standard` prints them and comes with a stub and a runner, so a build can be driven through those ports an