Founding thesis · M2 Argued · 2026-09-22

The wallet authorization plane

An agent that can be given real spending authority is worth more than one that can only draft a request for a human to execute — but only if the organisation can still say afterward, to itself and to anyone who asks, exactly what was authorized, what happened, and why the two matched. Separating who-may-spend from what-just-happened is what makes that answerable; a faster approval workflow bolted onto a hot wallet does not.

Formed2026 — when FlashyOS agents needed real spending authority, not just an approval queue
OriginOriginated by the studio
GradeM2 Argued — The reasoning is sound and falsifiable and the thing exists. Nobody has used it yet.
WrittenReconstructed from the repositories and the commit record, not from a memo written at the time
Dated2026-09-22
Surface@flashyos/wallet-wdk on npm
§ 01

Why then

A thesis with no timing argument is an observation. This is what changed that made the company possible in that year and not three years earlier.

Agent runtimes became competent enough to be trusted with a real financial capability in the same period this estate already had to solve consent for non-financial coordination — the plane is the money-specific instance of a problem ‘Consent is the product’ already names for the rest of the mesh — and Tether WDK gave a wallet SDK worth building a separated architecture on top of, rather than a limit configured inside a single hot wallet.

§ 02

The wedge

The narrow first thing. A thesis without one is a market map, and a market map is not a company.

Authorization is a signed verdict from the plane over a described OperationRecord — ALLOW with a signed SpendAuthorization, ESCALATE to a human, or DENY with a code. Execution is a second, isolated process, the signer, which never trusts that description: it re-derives the real operation from the actual call — the transaction, the swap, the EIP-3009 typed data — and refuses any mismatch. A compromised caller can ask the signer to execute anything; it can only get what the plane already signed off on for that exact call, which a spend cap on a hot wallet cannot ask.

§ 03

What has to be true

Each assumption stated so it can be checked rather than agreed with. A reader who disagrees with one of these disagrees with the company, which is the point of writing them down separately.

01A re-derived operation checked against a signed authorization is a materially different security property from a spend cap on a single key, not the same protection with extra steps
02Organisations will trust a testnet-proven, off-by-default plane enough to turn it on, rather than demand mainnet evidence before taking it seriously
03The audit trail a settlement report leaves behind is worth more to an organisation than the throughput lost to the escalation path it requires
§ 04

What would kill it

One falsifier, not a list. A thesis with five has none, because no one of them ever quite happens and the company survives every partial version.

Given the choice, organisations provision agents with a hot wallet and a spend cap instead, and a year after testnet the separated signer is running nowhere real — meaning the extra architecture bought a verifiability nobody needed enough to adopt.

§ 05

What dates it

The earliest artefact that could only exist if the thesis already did. It bounds the thesis from above rather than dating its formation — the belief precedes the commit, always.

2026-09-22 — to the day.

c35d7b40, PR #137 “Reconcile the wallet plane and Flashy Mind onto main (Phase 33)” — 619 files changed, +63,027/−151, merged onto main.

github.com/FlashyLabs/flashyos/pull/137

§ 06

How far it has got

The grade, and the register the grade was read from. A grade with no basis is an opinion wearing a badge.

M4

Proven

Running against a population outside this estate, with a number that moves without our help.
M3

Evidenced

Running in production. Every consumer is inside the estate, which is the ceiling until somebody outside adopts it.
M2

Argued

This company is here
M1

Pre-thesis

A real observation about the world. Not yet a company, and named here rather than dressed as one.

Basis. @flashyos/signer, @flashyos/wallet-wdk and @flashyos/wdk published to npm at 0.1.0 on 2026-09-22, confirmed against the registry rather than the repository, with 91, 117 and 34 of their own tests passing per PR #137’s own table. `TESTNETS` in the signer is the whole list of chains it will construct a backend for — Base, Ethereum, Arbitrum and OP Sepolia, Nile and Shasta — and a mainnet chain id throws `MainnetNotEnabled` by construction, not behind a flag. In production, `authorizationKeys()` throws if `WALLET_AUTHZ_PRIVATE_KEY` is unset rather than minting an ephemeral key, so the plane cannot sign anything in production until an operator sets it — read from `packages/api/src/lib/wallet/authorization.ts`, not asserted from a doc. flashyos.com/wallet 404s as of 2026-09-23; PR #137’s own body says the public surface is Phase 34, gated on this merge and not yet shipped. Argued rather than evidenced: the thing exists, is tested, and runs on testnets — nobody, inside or outside the estate, has yet spent through it in production.

§ 07

What has actually been learnt

Append-only and dated. A lesson edited after the fact is a description, and this file has a rule against those.

2026-09Refusing a mismatch is not the same claim as refusing a risk. The signer’s third line — reading a Safe Allowance Module before execution — only fires when an operator has actually installed one and configured `onChainLimit`; it is optional in the package, so an unconfigured deployment collapses to two lines rather than three, and nothing in the code forces the third.
§ 08

Where this goes next

The vocabulary this thesis is written in, the cycle it was formed against, and the properties it touches. Every internal link is checked against the register that generates it, so a renamed term fails a test rather than becoming a 404 somebody finds later.

FlashyOSThe coordination layer this plane is the money-specific proof for — the same consent doctrine, applied to spending rather than to introductions.
Scoped authorityWhat an agent may do, bounded — the mechanism a spend envelope narrows into a signed, single-use authorization.
Audit trailThe record a settlement report has to leave so “why was this allowed” is answerable after the fact, not only before it.
Delegation chainAttenuation, never inheritance — the same rule the signer enforces about what an authorization may narrow into.
@flashyos/signer on npmThe published package — check the version and publish date against the registry directly, not this page.
§ 09

The other theses

Every venture, its grade, and the register the grade came from. The ladder is on the ventures index.

VentureGradeOrigin
FinanceOSM1 Pre-thesisInherited
Flashy GoldM3 EvidencedInherited
Flashy NetworkM3 EvidencedInherited
Flashy GroupM3 EvidencedInherited
FlashyOSM3 EvidencedInherited
CountersignM3 EvidencedStudio
Flashy IDM3 EvidencedInherited
Flashy MindM2 ArguedInherited
IntentMeshM2 ArguedStudio
AssetMeshM2 ArguedStudio
MagicianM2 ArguedStudio
RitualOSM2 ArguedStudio
BuildOSM2 ArguedStudio
rare.funM1 Pre-thesisStudio
NFT CapitalM2 ArguedStudio
h3alth GroupM2 ArguedStudio
Flashy AcademyM3 EvidencedInherited
ClaimYour.GoldM3 EvidencedInherited
Metaverse GroupM4 ProvenInherited
BitMap HoldingsM4 ProvenInherited
NFT BAZLM3 EvidencedInherited
The Agency LayerM2 ArguedStudio
Portable AuthorityM2 ArguedStudio
Declared ExistenceM2 ArguedStudio
Published IntentM2 ArguedStudio
Consented TrustM2 ArguedStudio
The Machine DoorM2 ArguedStudio
Chartered OrganisationsM2 ArguedStudio
The MeshM2 ArguedStudio
Policy-Bound ValueM2 ArguedStudio
Sealed RecordM2 ArguedStudio
Fewer Businesses Than BrandsM2 ArguedStudio