For builders

Build the product,not the rails.

Identity, Intelligence, Value — wired into your product, signed by your users, settled on-chain. The regulated parts are primitives you call, not systems you build.

northwind · build mode
>_
developer
Build a $25M facility with @priya — SOFR + 625.
YF agent · wired
@yieldfabric/wallet
@yieldfabric/sdk
@yieldfabric/terminal
>_
hash 0x9c4f…e21a
preview live
Credit facility
Northwind · v1
READY TO SIGN
M
maria
lender
P
priya kapoor
sponsor
Facility$25,000,000
MarginSOFR + 625
CouponQuarterly
hash 0x9c4f…e21a
01In-house

The product wasn’t the hard part.

Your team shipped the platform. Then came the regulated core — custody, multi-party signatures, confidential settlement, an audit trail that reconciles. Assembled from vendors it drifts: the legal terms, the workflow, and what settles on-chain stop matching.

Three sources of truth — and they drift
Project · Northwind Credit
Month 18 · in-house build
STALLED · 18 mo
Product + UI · credit platformshipped
Custody + escrowblocked · no multi-party provider
Multi-party signaturesblocked · bespoke, per deal
Confidential settlementblocked · no off-the-shelf ZK
Compliance · audit trailpending · reconciled by hand
Legal ↔ workflow ↔ chaindrifting · three sources of truth
·First settled dealwaiting on all of the above
The product shipped. The settlement layer is still a project.
02Integrated

One signed object. Live.

Same platform. Identity, structuring, and settlement called as primitives — one canonical signed object, so the document, the workflow, and the on-chain settlement all derive from the same hash. The first deal settles in days, not quarters.

Identity · Intelligence · Value — proven in Project Acacia
Project · Northwind Credit
Week 2 · integrated
LIVE · wk 2
Product + UI · credit platformshipped
Identity · sign-in + signing@yieldfabric/wallet · one sign-in
Payments · atomic@yieldfabric · atomic · ZK-confidential
Escrow · multi-party@yieldfabric · first-class · no custom code
Signed agreements@yieldfabric · AI-structured · one hash
Compliance · audit trailon-chain by default
First settled deal$25M facility · just settled
Week 2. The hard part is now a primitive.
What you wire in

The deal layer. In three.

Install the wallet, call the gateway, and make the first deal executable — without building custody, escrow, or a settlement backend.

01

Your customers, signed in.

A wallet that doubles as identity. One sign-in handles auth, signatures, and on-chain action without starting from a separate identity stack.

02

Your deals, structured by AI.

The work

Agents that know deal structure — terms, comps, multi-party flows, collateral and repo. Describe the deal; the agent produces the signable, canonical plan.

03

Your money, atomically settled.

Payments, escrow, swaps, multi-party — all on-chain, all atomic, all audited, with less bespoke glue around payouts, approvals, and escrow.

deal.canonical.json
>_
Draft a $25M facility with @priya — SOFR + 625, quarterly.
deal counsel · structuring canonical-JSON
1
2
3
4
5
6
7
{
"type": "facility",
"parties": ["maria", "priya"],
"cap": 25_000_000,
"cadence": "quarterly",
"hash": "0x9c4f…e21a"
}
Rendered as documentagreement.md0x9c4f…e21a
Running as workflowpipeline · multi-sig0x9c4f…e21a
Settled on-chainatomic tx · ZK confidential0x9c4f…e21a
Identity · Intelligence · Value
one hash · signed

Build on proven rails.

The same rails proven in Project Acacia — the Reserve Bank of Australia’s wholesale-CBDC pilot — as an SDK and a GraphQL gateway. Start with the docs, or bring the first workflow you want to make executable.

IV of V·End of chapter