Private Credit & Lenders

You can't lend against a promise.
You can lend against a proof.

Automated decisioning increasingly generates the cash flow a private credit book is lent against. This makes that cash flow a monitorable asset: a control below the operator, a record that travels, and a covenant drawn where the action happens.

In design · seeking lender and covenant design partners

Break the bound → What you monitor on ↓

The lender's problem

Governance by declaration is the only record you have.

The compliance certificate is a representation: the borrower's own word that the system generating the cash flow is inside policy. It has always been a necessity, never a preference, because no independent instrument existed. This is the first asset class where it doesn't have to be.

The exposure already exists

Scorecards, not instruments.

Automated decisioning already generates the cash flows being lent against, pricing, claims handling, underwriting, allocation, through systems nobody outside the borrower can inspect. 2026 internal portfolio reviews defending software books against AI-disruption fears run on financial statements and management data. That is a scorecard, not an instrument.

The four conditions of lendability

When a promise becomes a proof.

A control below the operator

A prevention mechanism the borrower cannot quietly disable.

A record that travels

Per-action evidence a third party can inspect, attached to the action itself.

A covenant drawn at the control

The rule that makes the market: the covenant references the mechanism.

Loss experience that accrues

A stream of measured outcomes that lets monitoring price on evidence.

Precedent Hartford · steam / UL · electricity / factory mutuals · fire / IIHS · automobile The precedent →

The test for AI, honestly scored

Two met, one at the Rules tier, one accumulating.

Condition	Status	Reading
2 · Record that travels	Met	A per-action attestation token bound to a signed rule version. Specimen on request.
1 · Control below the operator	Rules tier today	Deterministic enforcement logic, proven and in production. The hardware-rooted appliance is patent-filed and designed; integration to be built and validated.
3 · Covenant at the control	Yours to draft	The covenant references the mechanism. That is your instrument, not ours.
4 · Loss experience	Forming now	Scrutiny-first, with EU AI Act per-decision logging operational from Aug 2026.

Three artefacts a lender can monitor on

Frequency, exposure, accumulation.

Calibrate, not test

Frequency → Certified Miss-Rate

A distribution-free ceiling on how often a violation gets through, read as a default-precursor frequency bound.

Ships now · Rules tier

Exposure → the attestation stream

Telematics for the cash-flow engine: counted exposure, not certified narrative.

Established statistics

Accumulation → Aggregate Drift

Early warning before deterioration reaches the P&L, the mark, or the rating.

The telemetry feed

Each token field, read as covenant relevance.

Token field	Covenant relevance
rule-set version + hash	What the action was measured against, a signed policy release.
constraint class	Obligation family / covenant mapping.
verdict + timestamp	Compliance frequency and timing.
model identity + version	The change-point that triggers notice.
appliance attestation state	Is the control itself intact, the condition precedent.

Aggregate-only by design, property, not configuration. Rates, mixes, drift statistics; never decision contents, never person-identifiable data.

In the lender's language

constraint = covenant condition

library = declared operating policy, machine-checkable

calibration set = compliance evidence

drift monitoring = continuous monitoring

rule-set version + hash = a signed policy release, never an unversioned edit

The proposition: carrot and proof

Adoption is self-motivated, so the covenant recognises it.

The borrower receives

The full disposition record, a safe-but-novel review queue, blocked items and why, and an outbound-egress log. The appliance earns its place before any covenant exists, so adoption is self-motivated.

The lender receives

Rates, mixes and drift across the four dispositions; rule-set and model-identity change-points; attestation state; and the aggregate-drift analysis as portfolio intelligence. Never: decision contents · person-identifiable data · the model.

Why proof commands a premium. The Premium on Proof →

Feed events → policy events

Machinery a lender may map to covenant conditions.

Machinery in the system	Covenant analogue
Guarantee-invalidation event	A notifiable change in the evidence basis.
Re-certification (model change / shift / calendar)	A dated reset of the measurement.
Drift threshold breach	An accumulation signal at portfolio level.

Analogues a lender may adopt, not covenant terms Triodian sets.

Break the bound

Your credit quants run it inside your walls. We never see the data.

The frequency bound is pre-registered and falsifiable: on a corpus you choose, the certified threshold holds the realised miss-rate at or below your stated α, or you have falsified the measure before you ever covenant on it.

The Blind Validation Protocol →

Status, without varnish

The complete integrated system is not yet built and tested; research risk is concentrated in semantic governance. The USPTO application was filed 6 January 2026.

Triodian is not a lender, credit rating agency, valuation agent or financial adviser, does not hold an Australian Financial Services Licence, and does not issue, arrange or advise on credit or rating products.