REF: sovereign-agent-starter · 6bfd8e9 · 2026-08-01

Build What
Cannot Be Taken

Your portfolio lives on a platform that can delete it. Your channel takes a cut it sets and re-sets. Your runtime belongs to an entity with an exit clock you cannot see. This is the alternative.

Work Receipt
Appending
Ledger depth: 4
Event
feat: add export bundle — third-party replay verified
Hash
a3f9c1e2b8d4f7a1c9e3b5d2f8a4c6e1
Previous
b7d4a0f1c2e8b3d9a5f1c7e4b2d9f3a6
Author
michael · verified key
Timestamp
2026-08-01T06:24:00Z
Replay
✓ Byte-identical · no access to our systems required
Append-only · hash-chained · tamper-EVIDENT
Alteration does not erase. It shows.
SEALED
& FILED

What this is, and what it is not

Start here.
It is not
  • A chain, coin, or token that floats
  • A listing, airdrop, presale, or raise
  • A consensus layer you must secure
  • A gas market or MEV surface
  • Composable with existing DeFi
  • A liquid exit — there is no venue
It is
  • A private ledgered entry derived from signed receipts
  • Minted and redeemed under published rules
  • Every balance recomputable from receipts on your own node
  • Verifiable by a third party with no access to our systems
  • Yours physically — your machine, open formats
  • An exit that keeps your records, customers, and code

Where the work leaks

Check against your last 3 years.
The Portfolio
Attested by a platform that can delete it, de-rank it, rate-limit the API, or go away. Your commit history needs someone's permission to be a claim about your life.
The Channel
A marketplace, store, or registry sets the cut — and re-sets it. You don't negotiate the rate. You learn it.
The Runtime & Registry
Each belongs to an entity with a lifecycle shorter than your career and an exit clock you cannot see.
The Web3 Version
Not exempt. A fork doesn't carry the liquidity or the record. Front ends run on few providers. Governance concentrates when the governance instrument is purchasable.

A shared chain relocates the dependency. It does not return the authority. Neutrality is a governance property, not a technology property.

Your node, concretely

Status on every item.
T1
Portfolio Receipts
Record a delivery, seal it, export as a self-verifying bundle. A third party replays it to a byte-identical result with no access to our systems. What actually runs today. The git hook that automates this is the first bounty — it's not built yet, which is why it's the first bounty.
Cheat-test: a portfolio that needs a platform's permission to display is capture.
Runs Today
T2
Prepaid Retainers
Client prepays sprint capacity. Burns per delivered receipt. Terms locked at mint — repricing after mint is a named breach, visible in the audit trail.
Cheat-test: re-pricing scope after mint shows in the trail.
Designing
T3
Compute Credits
Idle machine sells attested compute or CI hours at published unit prices. Units a human cannot recount from receipts are a hidden meter.
Cheat-test: units unrecountable from receipts are a hidden meter.
Designing
T4 ‡
Builder Stake
Merged bounty work becomes permanent principal with fading yield over ~4 years. Structured under real co-op, mutual, or trust statute. Counsel before anyone signs. This gate is named at every appearance.
Cheat-test: a bounty priced after submission shows in the audit trail.
Designing

‡ Anything security-, loan-, insurance-, or pooled-investment-shaped is structured under real statute with counsel before anyone signs. Named at every appearance without exception.

The Invariant Gate

13 tests · 8 CI-checked · 5 not yet
01
Local key custody
CI Checked
02
No mandatory external identity
CI Checked
03
Open formats, locally verifiable
CI Checked
04
Receipts both sides
CI Checked
05
Local record authoritative
CI Checked
06
Replaceable implementation path
CI Checked
07
Clean exit, no kill switch
CI Checked
08
The human yes
CI Checked
09
No original-media egress
Not Yet
10
No outbound monitoring
Not Yet
11
Forgetful by design
Not Yet
12
Honest proof meaning
Not Yet
13
Durable operating rights
Not Yet

Pass = eligible for canon and payment. Fail = a published finding. A published finding automatically becomes a bounty. The network's self-criticism is the builder's order book.

Two lanes

Lane 1 is the default.
Lane 1 — Default
Sell Private Work
Anything you build and sell is yours: 100% of revenue, your pricing, your customers, inheritable by your children. The network's only touch is the same thin published fee everyone pays. No builder is ever required to open private work.
→ Revenue yours. Always.
Lane 2 — Opt-in, per artifact
Contribute to Canon
Chosen at the point of contribution — after which uniform published rules govern, irrevocably. A commons cannot be un-shared any more than it can be captured. Yield fades over ~4 years unless you keep building. Your record is permanent. Your yield is not.
→ Record permanent. Yield earned.
The ceiling — computed in front of you, because you would compute it anyway
Epoch share caps at 30% while the co-op is tiny · ~7.5% at N≈20 · 5% from N≈30.
Pool-scale ceilings ≈ $25–75/month. District scenario ≈ $100–300/month at the 5% cap.
The epoch column is never the offer. Today assume stake-only — a declared pre-revenue condition, not doctrine.

What breaks this

Named, not rounded.
Cold start
No users, no production deployment anywhere. Lane 1 doesn't depend on the network. Lane 2 is explicitly a bet on something that does not exist. No mechanism substitutes for the network effect that hasn't been earned yet.
Unsolved
Fee pool never reaches cash
Lane 2 stays stake-only indefinitely. There's no mechanism that fixes this — only the disclosure, which is why the pre-revenue condition is stated in every artifact. Judge lane 2 on whether you'd do the work anyway.
Disclosed
Key loss
Local custody means local loss. No social recovery, no support line. Records can be re-attested by counterparties who hold their copy — because receipts land on both sides.
Disclosed
No liquidity
Said in the first section and repeated here because it is the objection that should end the conversation if it is going to. There is no market and none is planned.
Disclosed

Your ledger

Append-only. Hash-chained.
Connect your repository
Merges become receipts. Receipts become your record.
Receipt Ledger
4 receipts · 499 tests passing
#
Hash
Event
Author
Seal
#4 a3f9c1e2… feat: export bundle — third-party replay verified michael Sealed
#3 b7d4a0f1… fix: invariant gate — press_seal_key fixture gap filed michael Sealed
#2 c2e8b3d9… feat: append-only hash-chained record core michael Sealed
#1 d5f1c7a4… init: sovereign-agent-starter · 499 tests · 498 passing michael Sealed
Verify any receipt — no account required
The ask

One bounded build.
Not a pilot. Not a raise.

One module or one bounty. Your machine. 2–6 weeks. Against the invariant suite. Success is measured in your terms, not ours.

✓
Does it pass the 8 CI-checked invariants?
✓
Can you export everything and walk, losing nothing but the connection?
✓
Is the receipt verifiable by a third party with no access to our systems?
Would you ship it to a paying client?
Standing statements — every artifact, without exception
The node records and attributes. It never moves, custodies, or settles value.
No autonomous finance path exists or is proposed.
Nothing here has been endorsed by any regulator.
Deployed as a live system of record nowhere yet. No production business runs on it. Not one.
All economics are modeled, not measured. No revenue earned, no payout made.
Contribution is opt-in, per artifact. No builder is ever required to open private work.
Nothing here is an offer. No named customer, partner, or firm appears in any artifact.
The record is tamper-EVIDENT: it does not claim to be unalterable. It claims alteration shows.