debtor-chasinglisted

# Debtor Chasing Build Standard **Spec:** AIP-BS-DEBTOR-CHASING · **Version:** 2026-09-11 · **Canonical:** https://aipathway.com.au/explore-ai/debtor-chasing-build-standard Build standard: the method for chasing your own debtor book. Four buckets, why ranking by age sends you to the wrong end of the ledger, the opener that returns a date, promise-to-pay as an object, and the compliance gate that is the one step not to hand-roll. ## Read the standard first The full specification is in `reference/debtor-chasing.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/debtor-chasing-build-standard.md. This copy is 2026-09-11. 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/debtor-chasing-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 debtor-chasing-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 before building returns `evidence_required`, which no amount of w