docs: surface SP9-SP13 in README + endpoint reference #1
Reference in New Issue
Block a user
Delete Branch "docs/sp9-13-readme-sync"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Bring the README back in line with the codebase. The root README only documented up to SP8 even though SP9-SP13 (multi-payer + multi-NPI + SFTP stub, 277CA + Payer-Rejected lane, tamper-evident audit log, optional SQLCipher encryption, paramiko SFTP wire-up) are all merged into main.
Changes
Inbox
New top-level sections
providers/payers/payer_configs/clearhousetables,config/payers.yamlloader, the config + clearhouse endpoint table.POST /api/parse-277ca,GET /api/277ca-acks[/...], monotonic payer-rejection stamp contract.audit_log,GET /api/admin/audit-log/verifychain walker.docs/reference/co-medicaid.md.Persistence
Roadmap
parse-ta1+ta1-acks.Project layout
api_helpers,db,db_migrate,db_crypto,audit_log,inbox_lanes,inbox_state,inbox_state_277ca,providers,payers,secrets,reconcile.config/payers.yaml,docs/reviews/, and the newdocs/superpowers/specs/tree.backend/README.md
parse-999,parse-ta1,parse-277ca,eligibility/request,eligibility/parse-271,clearhouse,clearhouse/submit,admin/reload-config,admin/audit-log,admin/audit-log/verify. Point at the root README for the full route list.Verification
pytest --collect-onlyinbackend/collects 733 tests (the suite has grown past the 574 reported in the 2026-06-20 review).git diff --checkclean.##top-level sections added; existing sections preserved.Out of scope
There is a separate, unrelated refactor in the working tree (the
api.py→api_helpers.pysplit) that I deliberately did NOT include in this PR. That belongs in its own PR.Pull request closed