AI Governance & Assurance · live demo

The covenant certificate that will not sign through a breach.

Covenant compliance against a bespoke credit agreement usually lives in one analyst's spreadsheet, and the EBITDA bridge drifts from the negotiated definition one "interpretation" at a time until an auditor recomputes it. This demo draws the trust boundary the way I believe every treasury agent should: the model extracted each defined term once from a real credit agreement, quoting the clause verbatim and abstaining where the document defines nothing, a named treasurer confirmed and froze the definitions, and from then on deterministic code recomputes every ratio from every monthly trial balance and drafts the certificate from computed values only. Flip the disputed add-back below and watch the answer, and the Sign button, change. Real clauses: SEC EDGAR · synthetic trial balances

The add-backs · drag each one on or off

the leverage ratio, trajectory and certificate recompute instantly
·
total leverage · covenant <3.50 (§6.08)
·
headroom to the covenant
·
to projected breach
·
24 TBs × 8 combinations, recomputed

Headroom now, and where it is heading

Consolidated Total Leverage Ratio · LTM · debt held flat

The three ratio covenants · computed, not transcribed

thresholds from the agreement's schedules, terminal values
covenantrequiredcomputedheadroomstatus

Compliance certificate · drafted by substitution

§5.01(c) · the model writes no numbers
human gate 2 · the app records what is on screen at signature

The frozen definitions · extract once, confirm once

verbatim clauses, abstentions and manual entries, all in the ledger

Clauses quoted verbatim from Amendment No. 3 to the Amended and Restated Credit Agreement, The Manitowoc Company, Inc. (SEC EDGAR, 8-K exhibit 4.1, January 2010) · SEC filings are US public records · the borrower applying them here is synthetic, trial balances seeded · the "model" is a deterministic stub, so the run reproduces exactly