rejected-packlisted

# Rejected Pack Build Standard **Spec:** AIP-BS-REJECTED-PACK · **Version:** 2026-09-15 · **Canonical:** https://aipathway.com.au/explore-ai/rejected-pack-build-standard Open specification: how to stop a licence, insurance or compliance pack failing after the work is done. The parent standard for Invoice Check, the Compliance Calendar and QA Proofcheck. One graph, eight checks in a fixed order, four queues, a named human gate, and the binding layer that is the hard step. Free to implement, with a twelve-point conformance checklist. ## Read the standard first The full specification is in `reference/rejected-pack.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/rejected-pack-build-standard.md. This copy is 2026-09-15. 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/rejected-pack-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 rejected-pack-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 yo