multi-site-conformancelisted

# Multi Site Conformance Build Standard **Spec:** AIP-BS-MULTI-SITE-CONFORMANCE · **Version:** 2026-09-17 · **Canonical:** https://aipathway.com.au/explore-ai/multi-site-conformance-build-standard Open specification: how to run one operating standard across many branches, franchises or entities. A versioned key contract, four kinds of drift, one score computed once, and why training material is not a control. Free to implement, with a conformance checklist. ## Read the standard first The full specification is in `reference/multi-site-conformance.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/multi-site-conformance-build-standard.md. This copy is 2026-09-17. 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/multi-site-conformance-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 multi-site-conformance-build-standard` prints them and comes with a stub and a runner, so a build can be driven through those ports and asserted without a live phone number. Verdicts are not pass/fail: a check needing a live number returns `with_us` rather than failing you, and one asking what you measured befo