Challenge design previewThe local browser verifier, CLI, and frozen test pair exist. Signed child export, submissions, and enrollment are not open.

Portable proof for agentic investing

Don’t trust the screenshot. Verify the process.

Runbook is being built to turn a bounded investing experiment into a portable proof capsule: the charter written before the result, agent and human decisions, rejected actions, policy versions, outcomes, disclosures, and an evidence map you can inspect locally.

Verify a capsule locally Trace a local file set Study Verify → Clone

The browser-native verifier processes one .runbook locally and emits exact JCS receipt bytes. It does not upload or render capsule content.

SYNTHETIC · REFERENCE SPECIMEN

RUNBOOK / PROOF CAPSULEminimal-synthetic-root

expected
intact

DATA CLASSSYNTHETICdeclared

MANIFESTrunbook.proof-capsule.v1draft profile

AUTHOR KEYself-asserted referencenot identity

SOURCE TRUTHnot establishedno broker record

LINEAGEroot · no parentssigned declaration

SIGNED CHECKPOINT ID · SAME IN BOTH TRANSPORT FILES66b200560e20f723ece402931277043b85316687aac30f73c4da6a4d5a323578

“Runbook artifact verified” is an integrity statement—not verified returns.

Proof before pitch

One green shield is not enough.

Runbook keeps separate assurance dimensions visible so package integrity can never silently become a claim about brokerage truth, completeness, or investing skill.

DimensionQuestion answeredHard limit

01Package integrityvalid / tampered / unsupported

Do every declared byte and schema entry match the signed manifest?

Integrity does not make the claims true.

02Author signaturevalid / invalid / absent

Was this artifact signed by the holder of the displayed key?

A self-asserted key is not legal identity or broker ownership.

03Time evidenceanchored / self-declared / absent

Is there independent evidence that a digest existed by a stated time?

A timestamp does not prove an event happened then.

04Source coverageclaim-specific

Which claim cites included bytes, a commitment, or a trusted attestation?

A user-supplied export is not automatically broker-issued.

05Completenesscomplete / gaps / partial / unknown

What named accounts, sources, asset classes, and dates were reconciled?

Nothing outside the declared scope is evaluated.

06Data + policysynthetic / live-author-declared

What execution class is declared, and did recorded actions match the included policy?

Conformance does not prove safety, skill, or suitability.

Synthetic reference pair

We changed one byte on purpose.

The frozen conformance corpus pairs an intact minimal synthetic artifact with a transport-valid copy whose payload changed after signing. There is no experiment result in either fixture; verifier behavior is the product test.

SYNTHETIC GOLDEN · FROZEN FIXTURE

{"dataClass":"synthetic"}Expected: artifact intact

Declared bytes match the author-signed manifest. Source truth and identity remain separate questions.

Outer archive SHA-256:
4a11da34f4f8ed3dcea6167f93e729dbbde7d69246e665d0b8616656eda74191

one payload byte changed after signing

SYNTHETIC TAMPERED · FROZEN FIXTURE

{"dataClass":"synthetix"}Expected: verification fails

Byte 22 changes from ASCII “c” to “x”; transport remains valid, but the manifest digest does not match.

Outer archive SHA-256:
eed412e23ce2a4c51c3e216a451585b8a82d9ad761e7dbfbe885f515b3a465e4

How it works

One experiment. Three moves.

Commit before the outcome

Write the question, benchmark, window, capital boundary, approval rule, and stop conditions before the first in-scope action.

Preserve the whole process

Keep proposals, rejections, approvals, corrections, cash flows, source coverage, outcomes, and known gaps in one append-only record.

Target: proof anyone can check

The intended workflow is to export one author-signed portable artifact, verify it locally, publish a readable report, and let another person clone the charter without copying a trade.

Proposed 30-day challenge

Fork the rules, not the trade.

The proposed challenge would ask an author to change exactly one declared assumption and publish a signed synthetic child capsule that cites its verified parent. Today’s frozen charter is only the minimal conformance root, and the product cannot yet create signed child capsules. Paper and mixed evidence require a future schema decision.

Draft an unsigned starter Run the capsule verifier

An unsigned starter is not a proof capsule, does not create valid lineage, and is not a challenge submission.

DAY-30 GATES · TARGETS, NOT RESULTS

0110

independent people verify the golden fixture

025

valid local child capsules created

033

independent authors publish a child

041+

child preserves a failure, rejection, correction, or null

Real-money trading to enter or improve a submission is prohibited.

OPEN THE TRUTH FORMAT

Schemaportable

Verifierlocal

Fixturesadversarial

Testsdraft-profile

Open-format moat

Verification stays free.

A recipient should never need a Runbook account, a working Runbook cloud, or a payment to validate an existing capsule. The schema, local verifier, synthetic fixtures, and conformance tests are designed to stay open.

The paid moat is the hard operational work around the standard: experiment design, local evidence mapping, collaboration, continuity, review, publication, and a growing opt-in lineage of credible child artifacts.

Inspect a normative receipt

Proposed Founding Creator Lab

Publish the bounded record—including known gaps.

$499target priceFive target pilots · enrollment not open

A proposed 30-day concierge implementation for finance creators, educators, and agent builders who already publish and want an inspectable recurring evidence workflow. The offer is a validation target, not a currently enrolled program.

One 45-minute experiment-design session
A written charter and evidence plan
Local Runbook setup and first recorded event
One portable proof capsule and public proof page
Four weekly report drafts with losses and limitations preserved
A final evidence review and export

Run the local-answer fit check Inspect the validation gatesThe fit check asks for no identity or account data, stays in your browser, and takes no payment.

Portable process proof

Evidence should travel farther than the claim.

Open the local capsule verifier Run the local-answer fit check