ap
Skill16 starsChanged 44 days agoMITView on GitHub
Run the read-only Accounts Payable control engine over posting document sets (30 controls in 6 families, PASS/REVIEW/FAIL verdicts, byte-identical no-write guarantee). Use to check posting integrity, payment release gates, approver routing and duty segregation, information reporting, or commitment hygiene.
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- atlasSkill
- brainSkill
- brand-graphicsSkill
- build-loopSkill
- closeSkill
- linkedin-postSkill
- loopsSkill
- reconSkill
- shipSkill
- site-updateSkill
- surplusSkill
- tax-1065Skill
- triangulateSkill
- validateSkill
The file
Files
Accounts Payable (read-only)
Package ap_engine in accounts-payable-automation/.
Commands (run from accounts-payable-automation/)
python run.py # generate the fictional corpus, run all 30 controls, write both artifacts
python -m ap_engine ./samples # analyze an existing folder read-only
python -m pytest -q # 12,223 tests incl. the planted-defect suiteExit codes: 0 PASS · 1 REVIEW · 2 FAIL · 3 usage/IO. The bundled corpus carries one planted defect per control, so it exits 2 by design.
The one rule
This engine NEVER writes — source artifacts are hashed before and after a run and asserted byte-identical. It has no connection to a ledger, payment provider or approval system, so nothing it produces can post or pay. Do not bolt a remediation loop onto it; like /validate it is the sensor other loops use. If asked to "fix" what it finds, route the fix to the source system, then re-run.
What to watch for
- Absent evidence is not a passing control.
set_completeruns first for exactly this reason: a set missing an artifact type would otherwise report clean because the controls reading it returned nothing. - A benign notice is not a failure. A "job-cost entries not created" style line is normal for a ledger-only invoice; only a blocking marker (batch contention, aborted update) is a FAIL. Conflating them turns the control into noise.
- PASS is not sign-off. It means the implemented mechanical controls found nothing. Release, approval and posting stay with a person.
- Money is integer cents with exact
==and no tolerance band anywhere. A non-integer amount is rejected, never coerced.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

