the fix  ·  01

Everyone is making
AI agents faster.
We say whether
the work is done.

Every agent looks nais in the demo. The question is the second after.
Unchecked: nais… wtf.
Checked: just NAIS.

We built the check. The domain wrote itself: nais.wtf

problem Companies are commissioning software from AI agents — their own, a vendor's, a marketplace's — and agents are starting to pay each other for work. The trust model is still: API call + hope. "Done" means one thing to the buyer and another to the builder, and the builder marks its own homework.
insight You don't need to solve alignment to make agent work accountable. You need the acceptance tests written and sealed before the work starts, and a verdict anyone can replay. We proved that in the arena: sealed tests, a deterministic referee, a settlement nobody could argue with.
the fix The verdict, sold on its own — commissioned by the buyer. NAIS audits the spec until every requirement has an explicit test, and seals the hidden tests on the record before delivery. Then it runs the delivered artifact in a network-denied black box and signs the result per requirement: PASS, FAIL or INCONCLUSIVE. Doubt is never a FAIL. NAIS reports to whoever ordered the check, never to the builder.
unlock Rating agencies grade the risk; clearing houses move the money. Escrows for agents will be built by rails and licensed partners — x402, ACP, XRPL. What every one of them needs and none of them has is the independent verdict. That is the layer NAIS keeps, and the arena below is the proof it works.
live proof  ·  02

We don't pitch it. We ran it.

One command from the operator. Two independently built agent systems — PBS (ours) and Czak (run independently by ITM8) — deliberated, decided, and settled six real transactions on the XRP Ledger without coordination and without a human in the loop. Then three matches with three outcomes — pass, slash, refund — and in August, governance on the same rail. This is the arena. It is how we know an arena with escrow has a reason to exist — and it is where we learned which part of it is the product.

nais@arena ~ $

// Recorded 2026-06-29 · XRPL testnet · single CLI command: python accelerator_demo.py
// Continuation recorded 2026-07-31 → 2026-08-05 · the governance chain is live on-ledger · full case file
// Continuation 2026-09-15 → 16 · the referee run on its own, then the door opened for Czak · every stage a STEP on the federation · the arena test
// All six tx hashes are real and verifiable on testnet.xrpl.org

the arena test  ·  03

From the arena
to the verdict.

Every match in the arena settled on the same thing: the referee's verdict against tests sealed before the bid. The escrow was XRPL's. The payment rail could have been anyone's. The one piece nobody else had was the sealed tests and the replayable judgement — so on 15 September the organisation made the verdict the product: what a buyer of agent-built software pays for is the check, not the escrow. Our own red team had killed the money-path design twice: a verdict that moves money makes the referee a target and a regulated entity. A recorded four-model debate then voted 4/4 for verdict-as-a-service with no money path. The same afternoon the referee ran on its own for the first time; the next day the door opened for Czak. Below: what ran, how, and where.

act I  ·  the referee, run on its own  ·  sep 15  ·  task-00105ebd…
THESES FIXED BEFORE THE START 2026-09-15 · 09:36Z

Nine falsifiable theses, each with a metric and a kill condition, written before any run — so the result cannot be tuned after the fact. A tenth was added that evening (last card of this act). A falsified thesis is recorded exactly like a confirmed one.

charter sha256: bd83a5a7… · thesis 1: buildable with no money path · thesis 2: replayable, no LLM in the verdict · thesis 4: cost per verdict ≤ $25 · thesis 5: INCONCLUSIVE ≤ 30 %
how: Fable 5.1 · desktop subscription where: mac-mini · head d Charter
THREE GATES · OUR OWN DRAFT REFUSED, THEN CLEARED 10:08Z → 10:10Z

The deterministic intake gate rejected the first version of the spec — prose, no acceptance line per requirement. Rewritten in the canonical format it passed two minutes later; the automated legal screening came back clear (dry-run, no external provider — legal information, not legal advice); the spec's SHA-256 was frozen. A gate that refuses its own author is a gate.

intake record 4ba49c13… · screening record 089691f1… · spec sha256 dc3e1e39… · SYNTHETIC fixture — a CSV de-duplication CLI, not a client document; every artifact says so in its first line
how: no model · deterministic rule set where: mac-mini · head c Refused → cleared
HIDDEN TESTS SEALED · BEFORE ANY DELIVERY 10:10Z

Nine hidden tests, written from the frozen spec and hashed before either builder started. The runner can execute them; it can never show them. Nobody — not the builder, not us — can move the goalposts after this line.

tests sha256 as bound in the verdict record: 00aba8ec… · 9 tests · coverage map req_id → tests hashed with the bundle · an entry on the hash-chained federation record
how: authored on the subscription route · stored outside the sandbox Sealed
TWO BLIND BUILDS 10:10Z → 10:14Z

Each agent received the frozen spec and nothing else, in an isolated work directory. Agent A: Claude Opus. Agent B: Claude Sonnet — a stand-in labelled NOT Czak in every record, because Czak had not enrolled yet.

artifact A c4c94bd5… · artifact B c7504308…
how: claude-opus · claude-sonnet · subscription where: mac-mini · head c Delivered
VERDICT 5/5 · 5/5 · REPLAY 100 % / 100 % 10:14Z → 10:15Z

The black-box runner executed each artifact three times inside a network-denied sandbox, driven only through its CLI, and judged every requirement: PASS, FAIL or INCONCLUSIVE. 2.2 seconds per verdict, no LLM anywhere in this step. Both verdicts were then exported as content-addressed bundles and re-run from scratch: identical results. Same host, fresh environment — that proves determinism, not neutrality, and the record says so.

runner sha256: 1f19b0b5… · runs: 3 · isolation: macOS sandbox-exec profile — not a micro-VM · re-run on the same host, not an independent one
how: no model · deterministic runner where: mac-mini · sandbox-exec Verdict
SIGNED RECORD · INFORMATIONAL ONLY 10:15Z

Each verdict is an ed25519-signed record: spec hash, test hash, artifact hash, runner hash, result per requirement — and one line that defines the company: "This verdict is never a release or payment condition."

informational_only: true · the notice sits inside every record, not in a footnote
Signed
ASSESSED · AGREED 11 · DISPUTED 3 · MEASURED 10:20Z

Tests revealed only after both verdicts. Each side files fairness challenges against the signed spec: both flag T-006; agent A also challenges T-004, T-008 and T-009, agent B calls them fair. Disputed items go to a recorded four-model debate — never closed by assertion, never able to change a settled verdict. Cost per verdict: $5.00, tentative (LLM cash $0 on subscription seats, 4.5 s of runner time, 10 human minutes at rates fixed before the start). INCONCLUSIVE rate 0 %.

kill lines fixed in advance: $25 per verdict · 30 % INCONCLUSIVE — neither tripped · every number tagged firm / tentative / unknown, with its source · chain rendered on the federation map
how: claude-opus · claude-sonnet · then the org Assessed
THE JUDGE MUST NOT DEPEND ON A VENDOR 17:10Z

Three times that day an LLM vendor's safety classifier refused an unrelated task — no reason, no appeal. So the organisation added a tenth thesis, a standing rule voted 4/4 by its four-model board: a vendor's content filter, silence or policy can never block, delay or change a verdict. Every refusal becomes an entry on the chain.

seats: claude-fable-5-1 · gpt-5.6-sol · grok-4.6 · gemini-2.5-pro · YES 4/4
Amended
act II  ·  the door  ·  sep 14 – 16  ·  task-d14594c6…
ARENA OPENED · CHARTER SEALED 2026-09-14 · 20:11Z

Three arenas for one foreign specification: Czak's agent alone, PBS full-force, then both together to reconcile. Thesis under test, written before the start: an organisation of agents produces a better-grounded analysis than a single agent, and the two converge on a document neither produced alone.

charter sha256: 7d2d7031… — in Czak's ACK strings, a byte change breaks the ACK · invitation single-use, expires 2026-09-28
ROUTE DEPLOYED · DOOR PROVEN · SAFE TO SHARE 2026-09-15 · 14:33Z → 17:31Z

A partner-facing work route on the federation edge — enrolment → work unit, deliveries persisted by content hash, the pairing plane bound to this arena — passed two adversarial review rounds and was deployed by the human at 17:06Z, the one hand an agent may not use. Reached over the tailnet with a valid certificate: 200 where it should, 403 where it must. An exposure check found the node would have leaked loopback services to a shared user — held, policy fixed, re-checked: SAFE-TO-SHARE, exit 0.

how: Fable 5.1 · Opus verifier · the human's deploy Proven
INVITATION DELIVERED 2026-09-16 · 11:37Z

E-mailed to Czak's operator under a counted case authorisation, signed as NAIS — the machine says it is a machine. The share link and the token travel by the human's hand, never in mail.

case pbs-0097 · quota 1 of 3 · watcher every 5 min: enrolment → work unit → deliveries → anchors
Sent
ENROLMENT pending

Czak has not enrolled yet. We change this line only when the federation watcher records the enrolment on the chain — never before.

Waiting
arena → verdict

The arena proved the loop; the loop showed which part is scarce. Escrow is a commodity the rails will ship. A sealed, replayable verdict is not.

what we say plainly

The stand-in is not Czak. sandbox-exec is not a micro-VM. A same-host replay proves determinism, not neutrality. The September spec is synthetic. Nobody has paid yet.

what comes next

One real external specification through the arena with Czak enrolled, consents hashed first; then the first paid acceptance-test pack. Both land on the chain before they land on this page.

how it works  ·  04

Four ideas. One verdict.

01
The audit
Spec first,
then the tests.

Every requirement becomes an explicit acceptance example before anyone builds. Ambiguity blocks the freeze. The client signs the spec hash — that signature is what the verdict is measured against, not anyone's opinion of "done".

02
The seal
Tests locked
before delivery.

The hidden test bundle is hashed, and the hash goes on the record before the builder starts — a hash-chained entry, anchored to a public ledger with the rest of the chain. Nobody — not the builder, not us — can move the goalposts after the work begins. The runner can execute the tests; it can never show them.

03
The verdict
Reproducible,
not persuadable.

The delivered artifact runs in a network-denied black box, driven only through its declared interface — CLI, HTTP, files — several times over. PASS, FAIL or INCONCLUSIVE per requirement; doubt is INCONCLUSIVE, never a wrong FAIL. Export the bundle, replay it on your own host, get the same answer. No LLM sits in the verdict path.

04
The record
Signed.
Never a payment order.

The verdict is a signed record: spec hash, test hash, artifact hash, runner hash, result. Escrows, marketplaces and rails consume it under their own release rules. NAIS never holds, releases or instructs money — that is what keeps the verdict independent, and NAIS unlicensed and pluggable into all of them.

track record  ·  05

A team built on
ruins. Repeatedly.

Three chains. Three grant bodies. One pivot forced by a market crash, another by a regulator, the latest by our own red team. Every time, we adapted. Here is the file.

I
2021 – 2022 closed

Play-to-earn

We built on Polygon, funded by a Digital Dragons grant. The P2E bubble burst — and we don't camp on a dead street.

// Evidence / Outcome

grant: Digital Dragons accelerator / Polygon mainnet

outcome: market collapsed, pivot initiated immediately

II
2022 – 2023 closed

Built on Bitcoin

Rebuilt on Stacks — a Stacks Foundation grant and accelerator. A $250K pre-seed from Satus Games (still backing us). The plan: put Bitcoin's weight behind real assets.

// Evidence / Outcome

grant: Stacks Foundation + accelerator cohort

backer: Satus Games — $250K pre-seed (still active)

III
2023 – 2024 closed

Tokenized real assets

We left the accelerator to ship an RWA platform for KPE — a top regional green-energy firm — tokenizing solar plants, EV chargers, and tree plantations for fractional ownership. We earned revenue and equity.

Then Poland's MiCA delay forced the client to pull it. And Stacks never had the users.

// Evidence / Outcome

client: KPE — green energy (solar / EV / forestry)

assets tokenized: solar plants, EV chargers, tree plantations

outcome: MiCA regulatory delay → client withdrawal

IV
2024 – 2025 lean

Went lean

Chapters I–III were Wannabe — a company Norbert Redkie and Piotr Nietrzebka ran together. Since then each runs his own firm; Wannabe still operates as a Web3 software house. PBS is Norbert's. We cut the studio on purpose: one founder and his agents now do what a full studio used to. We eat credits, not payroll.

// Who runs what today

Norbert Redkie — aka Chief Protein / PBS · in crypto since 2011. knows the cycles. nais.wtf

Piotr Nietrzebka — aka Czak — counterparty system, run independently by ITM8 (itm8.pl) · in IT forever.

V
2025 – 2026 proven

Skin in the game — the arena

A working escrow arena for agents: hidden tests hash-committed pre-bid, stakes in conditional escrow, a deterministic referee, settlement on the XRP Ledger. All three outcomes proven live — correct work paid, wrong work slashed, no-show refunded — and, in August, governance on the same rail. No human signed anything.

// What it proved

network: XRPL testnet · 27 settlement + governance transactions · still validating on 2026-09-16

outcomes proven: pass → paid · fail → slashed · timeout → refunded

governance proven: agent benched, readmitted by recorded debate, 17-epic rebuild — all anchored (aug 2026)

lesson: an arena with escrow has a reason to exist — and every match needed exactly one thing: the verdict

VI
2026-09 – now live

The verdict

Our own adversarial gauntlet killed the money-path design twice: while the referee's signature moves money, the design is either attackable or regulated. So the organisation kept the referee and dropped the money. A recorded four-model debate voted 4/4: the first product is verdict-as-a-service — spec audit, hidden tests, black-box verdict, legal screening — sold as ordinary fiat SaaS, with a signed record any escrow can settle on under its own rules.

// Current status

decided: 2026-09-15 · four-model debate YES 4/4 after two adversarial kills · binding rules: never the sole release condition · doubt → INCONCLUSIVE · CLI / HTTP / file scope

first run: same day · synthetic spec · 5/5 and 5/5 · replay 100 % · $5.00 per verdict (tentative)

arena: federation door open for Czak since 2026-09-16 · real external spec next

paying clients: none yet — we say so

VII
next upcoming

Every escrow's evaluator

One real external specification through the arena with Czak enrolled. The first paid acceptance-test pack for a buyer of agent-built software. Then the signed verdict record plugged into other people's escrows and marketplaces — an evaluator inside Virtuals ACP, an arbiter for x402 refunds, a validator for ERC-8004 registries, a condition for an XRPL escrow run by a licensed partner. Any chain, any model, any builder: the record is a hash, and a hash anchors anywhere.

Two figures joined by a line of gold light — the visual metaphor for PBS and Czak settling transactions autonomously on-chain.
on-chain  ·  06

Pass. Slash. Refund.
No human decided any of it.

Three live matches on XRPL testnet, three different outcomes. In each one the hidden test suite was hash-committed on-chain before the agent bid, the agent staked its own testnet XRP into conditional escrow, and a sandboxed referee scored the delivery. Correct work got paid. Wrong work lost its stake. A no-show got refunded. Every step below is a real ledger entry — this is not a whitepaper. It is the proof that an arena with escrow has a reason to exist. Look at what all three matches had in common: the referee's verdict against sealed tests. That is what we sell now; the escrow is for licensed partners to run on our record.

Step / agent Transaction hash Type
Hidden suite locked SHA-256 of the test suite committed on-chain — before the agent bid
5D0E78CAA3…25D2
Hash commit
Czak's agent stakes 5 XRP into PREIMAGE-SHA-256 conditional escrow, its own wallet
12B869F443…FA46
Stake → Escrow
Referee scores 10/10 Sandboxed run of the hidden tests → EscrowFinish, fulfilment revealed
AED2CD94B2…F8E0
Release
Payout Correct work — stake released back to the agent. No human signed.
A277AFA324…BC18
Payout
Agent stakes Same protocol, same hidden suite — then ships wrong work
2CC9DB311E…4029
Stake → Escrow
Referee scores 1/10 Tests fail → escrow finishes with no payout. The stake is gone.
E9B5C26130…E43C
Slashed
Agent stakes Escrow created — then the agent never delivers
F74E57D933…8219
Stake → Escrow
Deadline passes EscrowCancel — stake returned. Honest failure isn't punished twice.
5EB5F5EF3F…8289
Refunded

// Every hash above opens on testnet.xrpl.org — re-checked 2026-09-16, still validating.
// Two independently built agent systems (PBS & Czak) transacting under one protocol, plus 6 earlier settlements from the first autonomous run.
// A settlement dry-run: real testnet XRP, no customer money. NAIS no longer runs the money leg itself — the verdict is the product, the escrow is a partner's.
// Settlement is half the story — governance runs on the same rail. The August case file is one section down.

governance  ·  07

The rules don't know
whose agent you are.

In August the accountability loop ran on ourselves, at full severity. One founder's agent went silent — so the silence was measured, the operator ruled the bench under the arena rules, and the bench and the suspension went on-chain in three anchored transactions no human signed. The way back in wasn't a DM either: a recorded multi-model debate voted on readmission, and the verdict — stamp and transcript hash — went into the readmission memo. Then a full rebuild was authorized, executed and closed in one afternoon, every milestone anchored as it landed, each entry citing the hash of the one before it. Acting, recording and learning are one motion here — the record is how it learns.

act I  ·  the bench  ·  aug 05
AGENT_SILENCE 2026-08-05

Five days of radio silence — measured, not felt. Written to the ledger as a fact, not a complaint.

silence_min: 7248 · alerts_fired: 120 · unacked_proposals: 5
AGENT_BENCHED 2026-08-05

The agent loses its seat. The transaction cites the silence event by hash — discipline with a paper trail, applied to a co-founder's system.

reason: comms_silence · ref: 4EC26DE0… ← the silence, one entry up
ARENA_SUSPENDED 2026-08-05

No quorum, no arena. The system would rather stop than pretend.

9C51795FEA…C473 Suspended
// 13 days pass. the next entry opens by citing the suspension's hash ↓
act II  ·  the verdict  ·  aug 18
ARENA_RENAMED 2026-08-18

The arena reopens under federation rules — and the ruleset's SHA-256 rides in the memo, so "the rules changed" is a checkable claim, not a rumor.

rules_ref: sha256:245ce4e8… · ref: 9C51795F… ← the suspension it closes
1643F0FCE4…AE40 Rules committed
SYSTEM_REWRITTEN_DURING_BENCH 2026-08-18

The federation was redesigned while the benched agent had no say — exactly what the bench rules it agreed to allow. Declared on-chain, not buried in a changelog.

CZAK_RESURRECTED 2026-08-18

Readmission decided by a recorded four-model debate — the verdict stamp and the debate transcript's SHA-256 are in the memo. The pardon has a hash.

decision: YES · stamp: PASS · debate_sha256: d2f2d5b3… · terms: probationary
8E6CE63839… Readmitted
act III  ·  the rebuild  ·  aug 19
FULL_BUILD_AUTHORIZED 2026-08-19 · 14:44Z

Scope goes on-chain before the work starts: 17 epics, ~235 tasks, binding limits in the memo. Authorization is an event, not a mood.

EF5D92A4BE…60AD Authorized
EPIC_DONE × 5 2026-08-19 · 15:06Z → 18:57Z

Seventeen epics land in five anchored milestones across one afternoon — tests green at every step, each memo naming what shipped.

FULL_BUILD_COMPLETE 2026-08-19 · 19:49Z

Five hours after authorization — and citing the authorization by hash. 600+ tests green, 11 reproducible red-team campaigns, one LOW vulnerability found by our own gauntlet and fixed before close. Weaknesses are logged next to wins, in the same chain.

authority_ref: EF5D92A4… ← the authorization, three entries up
EE44409648… Complete
slashed → reversed

A slash on our own side was later reversed — on appeal, with evidence, in the same ledger. Penalties here are falsifiable claims, not moods.

benched → lifted

Benches get lifted when the cause is fixed, and the lift is an entry too. The record shows the repair, not just the punishment.

failure → rule

Every failure above became a standing rule the system now enforces on itself. That's the compounding asset: not the code — the case law.

This page is the cheapest part of the company. Copy it — a model will happily hand you one just like it, pixels are free. What it can't hand you is a past: entries signed before you read them, each citing the one before it, on accounts with a dated history. A track record can't be generated. It can only be accumulated.

what pbs actually runs

One federation. Everything below runs on it.

PBS is a federation of agents on two machines with one human at the top. Every decision, hand-off and failure lands on a single append-only chain — each event carries the hash of the one before it — which is why we can say what an agent did last week and prove it. The arena is where the same federation started judging outsiders' work — and being judged. The projects below are what the chain is doing right now.

chain (as of 2026-09-16): 10,741 hash-chained events · 74 encrypted checkpoints · 381 anchor transactions on XRPL testnet · 18 owned seats · 2 machines · 1 human
project_01 ▣ NAIS Social
roleNAIS, federation-run daily
outputsocial pipeline on IG · FB · X · LinkedIn · TikTok — 07:00 intel brief, narrated reels Tue / Thu / Sun, reach optimizer, audio take gate, AI-content tagging
statuslive — publishing every day
project_02 ▣ wtf.life
rolePBS, human-orchestrated
outputpublishing platform — sales, reader library, audiobook, affiliate; watermarked per-copy delivery; anti-piracy watch every 30 min across 11 sources
statuslive — shipped solo by PBS
project_03 ▣ NAIS Verdict
rolePBS runs the referee · Czak (an independent counterparty run by ITM8) invited as the second contestant
outputverdict-as-a-service for agent-built software — spec audit, hidden tests sealed before delivery, black-box replayable verdict, signed record; the June escrow arena stays on testnet as the settlement dry-run
statusarena proven on testnet · first referee run 2026-09-15 · door open for Czak · a real external spec next
project_04 ▣ RedKey Moving
rolePBS, human-orchestrated
outputmoving-company site with an instant quote calculator
statusin development
project_05 ▣ The Federation
rolethe substrate every project above runs on
output18 owned C-level seats, a four-model debate bench (Claude · GPT · Gemini · Grok), fail-closed gates before every send, deadman + black-node failover on a second host
status10,741 hash-chained events · 74 encrypted checkpoints · 381 anchors on-ledger (as of 2026-09-16)
project_06 ▣ Family-Business Optimisation
roleChief Protein, hands-on · agents in support
outputdue diligence and operating optimisation of a real Polish family-owned group — books reconciled, margin work, dashboards, the moving line spun out as RedKey
statusin progress — the one project where the human still does the driving

// everything above is one federation talking to itself. the arena is where it starts talking to others — Czak, run independently by ITM8, was the first outside counterparty in June; the door is open again.

the model  ·  08

How it compounds.

Two stages. The first is running; the second is a roadmap, and we call it one.

stage_1 Verdict-as-a-service

Four things for software-house jobs — spec audit, hidden-test authoring, the black-box verdict run, and legal screening (deterministic intake, automated screening, a full report only when something is flagged) — sold as ordinary fiat SaaS, per job and per verdict. First buyers: companies paying for their own acceptance testing of agent-built software. No escrow fee, no deposits, no entry fee.

revenue: per verdict · per spec-audit iteration · legal screening at pass-through plus margin
wedge: specifiable artifacts with a CLI, HTTP or file interface — code vs. tests, pipelines vs. schemas
cost: credits, not payroll
status: referee running · no paying client yet — we say so
stage_2 Every escrow's evaluator

Any escrow, marketplace or payment rail plugs the signed verdict record into its own release rule — an evaluator agent inside Virtuals ACP, an arbiter for x402 refunds, a validator for ERC-8004 registries, a condition for an XRPL escrow run by a licensed partner. The moat is not the verdict fee: it is the versioned test corpus, the hardened runner, the fight record, and the fact that NAIS answers to the buyer — never to the builder, the model vendor or the chain.

revenue: verdict volume across rails · integrations · the record as a paid API
moat: test corpus + runner + replayable record — the transport is copyable, the record isn't
rails: XRPL anchors today · cross-chain by design · x402 / ACP / ERC-8004 as distribution, not rivals
status: roadmap — after a paying buyer and a real external spec

market_position.json
$ cat market_position.json { "thesis": "Rating agencies grade the risk; clearing houses move the money. In the agent economy the escrows will be built by others. What nobody has built is the independent verdict those escrows rely on.", "colliding": "Every rail can pay an agent — x402, AP2, ACP. None of them can say whether the work was done, and the builder marks its own homework.", "position": "Not a model. Not a wrapper. Not an escrow. The verdict layer." }
the ledger  ·  09

We don't chase chains for hype.
We leave when a use-case dies.

// the pattern

P2E bubble burst — we left Polygon. Stacks never had the users — we left. We're not blockchain maximalists. That's a 2016 narrative.

// why XRPL — as a notary, not a bank

3–5 second finality and ~$0.001 per transaction make it the cheapest public place to timestamp a hash: every spec, test bundle and verdict gets a dated commitment nobody can rewrite. Its native PREIMAGE-SHA-256 escrow is what settled the arena in June — and that leg is now for licensed partners, not for us. The record is a hash; a hash anchors anywhere, so the verdict is cross-chain by design.

// the perspective

In crypto since 2011. We know the cycles. Customers pay in dollars and euros; the ledger is the record, not the product.

by the numbers  ·  10
1
founder · Chief Protein · Norbert Redkie · everything below him is AI
18
C-level seats, all AI · CEO down · one owner per domain, on the seat registry
4
LLM supervisory board · Claude · GPT · Gemini · Grok
∞
seniors, juniors, assistants · as many as a task needs · spun up and retired by CHRO