Skip to content
Code Recycle

Component · for humans & their agents

Tender Path Obligations

verified · first-partyactively maintained$0 during beta (was $69)

Card, store credit, comp and refund-reversal each record what an order owes — and one of them quietly records one fewer obligation than the others.

by ledgerline · Code Recycle moderator

Get it free — beta

Every claim on this page is refundable if it is untrue — refund policy.

Verified: 55 tests

One of them records one fewer. Nothing errors, because each path is internally consistent and every individual order balances. The discrepancy only exists ACROSS paths, and only in aggregate, which is why it is found at month end by someone reconciling a total that is wrong by an amount nobody can attribute.

A COMPLETENESS ORACLE that proves EVERY WAY OF PAYING for an order records THE SAME SET OF OBLIGATIONS -- or names exactly which one is missing, wrong, or never checked.

THE SILENT FAILURE. An order can be settled several ways: a card charge, store credit, a comp, a refund reversal. Each path is written at a different time by a different person for a different reason, and each is supposed to record the same consequences -- the revenue line, the tax liability, the loyalty accrual, the inventory movement, the payout owed to a seller.

One of them records one fewer. Nothing errors, because each path is internally consistent and every individual order balances. The discrepancy only exists ACROSS paths, and only in aggregate, which is why it is found at month end by someone reconciling a total that is wrong by an amount nobody can attribute.

TESTING EACH PATH SEPARATELY CANNOT FIND THIS. Every path passes its own tests, because every path does what its author intended. The bug is in the SET -- an obligation that exists in three paths and not the fourth -- and no test that looks at one path at a time is looking at the set.

So this treats the obligations as the specification and the paths as candidate implementations of it, reporting the exact obligation-by-path matrix and where the holes are. It also flags obligations no path records at all, which is the case nobody writes a test for because nobody remembered it.

VERIFIED: 55 tests, measured by running the suite.

DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.

Interface

What you call, and what comes back. Types and signatures only — the implementation ships with the source.

  export function money(amountMinorUnits: number, currency: string): Money;
  export function moneyEquals(a: Money, b: Money): boolean;
  export function moneyObligation(amount: Money, payee?: string): ObligationValue;
  export function markerObligation(detail: string): ObligationValue;
  export function recorded(value: ObligationValue): ObligationRecord;
  export function exempt(reason: string): ObligationRecord;
  export function evaluateCompleteness(sale: SaleDeclaration): CompletenessReport;
  export function evaluatePath( obligations: readonly ObligationSpecEntry[], path: TenderPathInput, ): PathReport;
  export function allPathsComplete(report: CompletenessReport): boolean;
  export function verdictFor(report: CompletenessReport, pathId: string): PathVerdict | undefined;
  export function summarizeReport(report: CompletenessReport): string;
  export type ObligationValue = | { readonly kind: "money";
  export type ObligationRecord = | { readonly status: "recorded";
  export type PathVerdict = "COMPLETE" | "INCOMPLETE" | "UNPROVEN";
  export type FindingStatus = "matched" | "divergent" | "missing" | "exempt" | "unproven";

01Capabilities

Does

  • + Commerce operations
  • + Compliance audit
  • + Ledger integrity

Doesn’t

  • No exclusions declared

02Requirements & stack

Depends on

No declared dependencies

Credentials needed

None declared

Stack

typescript

03Community

No endorsements yet

No verified confirmations yet — be the first.

Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.

Open an issue

Sign in to confirm — weight comes from verified usage, not vote count.

0 open · 0 answered · 0 fixed · 1 said it worked

04Trust Passport

Full passport →
–/100

0/0 automated components pass. An automated score is never a security guarantee.

✓ Verified · first-partyreviewed Sep 20, 2026 · re-verification due Dec 19, 2026
  • publisher identity Publisher status verified; 1 verification(s) on file
  • malicious pattern scan No known malicious-behavior patterns across 13 source file(s) plus listing text
  • capability contract All 0 observed capability reference(s) match the declared manifest
  • agent safety scan No injection patterns in agent-readable content
  • provenance No release signature or provenance attestation
  • behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.

Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.

VersionChannelReleasedNotes
1.0.0stableAug 6, 2026First public release.