Allometry / Technical overview
— The architecture

How the attested ledger is built.

Allometry sits above the existing stack and turns the operating record of a physical-revenue business into structured, signed, address-level evidence. Read-only in. Attested out. The same pipeline that runs the operator's day produces the asset a lender can underwrite.

▸ Connectors → canonical model → exception engine → write-time attestation → the vault → developer surface → enterprise security. No rip-and-replace; the stack is the on-ramp, not the competitor.

▸ 01 · Ingest

Connectors — read-only.

Recurring, read-only ingestion from the systems already in place: accounting/ERP, payroll, bank feeds, CRM, invoices and jobs. We read what exists, where it lives. We never replace the books, the bookkeeper, or the CPA.

QBO · Dynacom · Zoho · NetSuitepayrollbankCRM
▸ 02 · Normalize

The canonical model — the address graph.

Every source is resolved to one canonical model: account · entity · contract · unit · invoice · payment · holdback · renewal — keyed to the address. First-class: multi-entity linkage (conglomerate mapping, ownership-change re-routing) and multi-currency / multi-province tax. Five partial systems become one economic state vector per address.

address-keyedmulti-entitymulti-currency / tax
▸ 03 · Watch

The exception engine — the heart.

A library of deterministic rules runs over the canonical model and emits a risk-scored, prioritized queue: overdue AR, deposit-before-delivery, retainage aging, duplicate bills, unmatched payments, EST-to-invoice variance, payroll variance, tax mis-code, −60-day renewal, vendor cost creep, margin-leaking unit, cash-pressure. The high-stakes logic is deterministic — no room for interpretation; the rules are explicit, not inferred.

rule libraryrisk-scoreddeterministic
▸ 04 · Attest

Write-time attestation — we sign what was done.

Every atom — every quote, dispatch, bill, renewal, decision — is signed and hash-chained at write-time, each record linking to the prior one. Not a transcript of what was said; a tamper-evident record of what was done. This is the line: conversation exhaust makes a business smarter; an attested record makes it financeable.

hash-chainedwrite-timetamper-evident
▸ 05 · Accrue

The vault — time-locked.

The signed record accumulates into the operator's vault. Time-in-vault unlocks lender tiers: 6 months → working capital, 12 → infrastructure debt, 24 → insurance-linked, 36 → rated paper. A competitor can copy the endpoints in an afternoon; they cannot copy the months. The dataset is the moat — by construction.

T1–T4 tiersvintage-gatedoperator-owned
▸ 06 · Expose

The developer surface — Plaid-shaped.

The vault is exposed as a verifiable proof surface: MCP-callable atoms, zero-knowledge-attestable receipts, a REST surface. Lenders, insurers, agents, and downstream systems read from the same signed ledger — verify without revealing the underlying books. The underwriting fabric any counterparty connects to.

MCPZKP receiptsREST
▸ 07 · Govern

Security & reliability.

Per-tenant isolation, per-customer encryption, configurable retention, read-only scopes, and an audit trail on every decision. Built so an operator's CFO, their lender, and their auditor can all trust the same record.

tenant isolationencryptionaudit trail
— The atom

Every decision becomes a signed receipt.

An attested atom is small, verifiable, and chained. The score and the rule are visible; the underlying data stays in the operator's control. Verify the chain without ever exposing the books.

# atom · margin-floor decision · signed at write-time
{
  "atom": "quote", "ref": "Q-48213", "address": "addr_7f3a…",
  "decision": "margin_floor.pass", "score": 0.91, "rule": "margin-floor.alm@v3",
  "signed": "2026-05-22T14:03:11Z",
  "hash": "b8207ce5…", "prev": "6ba552b3…", // chained to the prior atom
  "verify": "zkp://receipt/…" // attestable without revealing the books
}
— Design principles

Built to be trusted, not just smart.

▸ Above the stack

On-ramp, not rip-out

We sit on top of the existing systems and read them. Nothing to migrate; the operator keeps their tools. The stack is the ingestion surface, not the competitor.

▸ Deterministic core

Explicit, not inferred

The money-moving decisions follow exact rules — margin floors, gates, tax logic — with the reasoning agentic where it helps and deterministic where it must be.

▸ Operator-owned vault

Their asset, by design

The attested record belongs to the operator. We make it portable, verifiable, and financeable — and only the operator decides who connects to it.

The pipeline that runs your day is the asset.

Read-only in, attested out. The same architecture that surfaces your exceptions and protects your margin is the one that turns your operating record into capital. That's the whole design.