sha256:2fbdf2a15df31817b5e737ad6147b32c418ea3886cee9b44a3262930ff7eae83
Does every accrual you are about to close trace back to a coding entry you declared? You supply the two lists (each entry as a lineage key, a GL account, an amount, optionally a source document digest, and for accruals a traces_to list of coding keys); the node returns the accruals that resolve, the accruals with no reference at all, every reference naming a key nothing declares, the coding entries nothing traces to, the coding entries with no source digest, repeated lineage keys, and an overall CLOSE_READY, GAPS_FOUND or INDETERMINATE determination. Four stages in one deterministic pass: intake with fail-closed shape validation, key uniqueness, per accrual linkage classification, coding side observations and the verdict. It pairs with the interest accrual recompute (art-661) and the GL tieout recompute (art-665), which verify the numbers this node's declared entries are about.
compute_proof_ready: deferred. No formal correctness proof has been produced for this kernel; the result above is a deterministic recompute, verified by a property-test floor and pinned to the build spec's worked example, not a proven one.Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.
Run the AINumbers MCP tool `verify_close_posting_lineage`. Task: Month-end close lineage verdict over declared entries: which accruals resolve to a declared GL coding entry, which references dangle, which coding entries nothing traces to, which lack a source digest, repeated lineage keys, overall CLOSE_READY, GAPS_FOUND or INDETERMINATE, per CLOSE-COMMAND-CENTER-BUILD-SPEC-2026-09-23.md
Call it with arguments: {"policy_parameters":{"as_of":"2026-09-30","coding_entries":[{"key":"COD-1","gl_account":"6100-office","amount":1200,"source_document_digest":"doc-digest-1"}],"accrual_entries":[{"key":"ACC-1","gl_account":"2100-accrued-expense","amount":1200,"traces_to":["COD-1"]},{"key":"ACC-2","gl_account":"2200-accrued-interest","amount":300,"traces_to":[]}]}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-692-close-posting-lineage.html#p=v1.H4sIAAAAAAAA_wFHAbj-eyJhc19vZiI6IjIwMjYtMDktMzAiLCJjb2RpbmdfZW50cmllcyI6W3sia2V5IjoiQ09ELTEiLCJnbF9hY2NvdW50IjoiNjEwMC1vZmZpY2UiLCJhbW91bnQiOjEyMDAsInNvdXJjZV9kb2N1bWVudF9kaWdlc3QiOiJkb2MtZGlnZXN0LTEifV0sImFjY3J1YWxfZW50cmllcyI6W3sia2V5IjoiQUNDLTEiLCJnbF9hY2NvdW50IjoiMjEwMC1hY2NydWVkLWV4cGVuc2UiLCJhbW91bnQiOjEyMDAsInRyYWNlc190byI6WyJDT0QtMSJdfSx7ImtleSI6IkFDQy0yIiwiZ2xfYWNjb3VudCI6IjIyMDAtYWNjcnVlZC1pbnRlcmVzdCIsImFtb3VudCI6MzAwLCJ0cmFjZXNfdG8iOltdfV193z8rjUcBAAA