Text → confirmed rules
Produces a DSL draft, readable rendering, validation results, and an ambiguity list. No ambiguous phrase should silently become a live action.
INTERFACE
idea.draftDOCS / ARCHITECTUREA system you
A system you
can inspect.
The service architecture separates the idea, the permission to act, the execution attempt, and the evidence. Each boundary has a defined responsibility.
THESIS TRADING / PROVISODEVICEIntent + owner signature
SERVICESEvaluate + execute
CHAINCommit + verify
01 / SERVICE EXPLORERDifferent jobs.
Different jobs.
Explicit boundaries.
02 / THE DATA & TRUST MODELStore the record.
Store the record.
Protect the rule.
Client responsibilities.
The device owns canonicalization, secure salts, commitment generation, signing, and the encrypted recovery export. The owner’s main key is never passed to Proviso.
Encrypted specifications.
The database stores enc_spec encrypted to the evaluator enclave’s attested key. The evaluator necessarily decrypts inside its isolated environment. Plaintext specifications and salts must not leak into ordinary storage or logs.
Operational entities.
Users, agent keys, swap policies, theses, fires, orders, follows, stamps, caller shares, link flags, and funding routes form the data model.
State has several dimensions.
Thesis state, position state, reveal state, and evidence status should be modelled separately. A fire, a fill, a reveal, and a posted root are related events, not interchangeable successes.
BunHonotRPC v11DrizzlePostgres + TimescaleRedis + BullMQviemFoundry
03 / CONTRACTSSmall contracts.
Small contracts.
Specific responsibilities.
ThesisSeal
Owner-signed commitments, reveal types, retirement, nonces, and deadlines.
seal · revealEntry · revealExit · retireStampRoots
Hourly roots and leaf counts; poster-key rotation by a 2-of-3 multisig.
postCallerShare
Funded USDG epochs and caller-directed claims with Merkle proofs.
postEpoch · claimProvisoSwapAdapter
The only allowed swap target, constrained by signed policy and oracle bounds.
swapThe contract model separates commitments, evidence roots, claims, and constrained swaps. Verify addresses and permissions before authorizing a transaction.
04 / OPERATING PRINCIPLESDefine the boundary.
Define the boundary.
Inspect every decision.
G01
Writer quality
An ambiguous instruction needs a decision from its author. Readable rules make that decision explicit.
G02
Signer policy
Every order must belong to a confirmed, live idea and remain within the owner’s approved limits.
G03
Swap confinement
Only the permitted adapter, pool keys, and exact approvals belong inside the swap policy.
G04
Fair Copy ordering
Follower submissions precede the linked caller, with acknowledgements and timestamps preserving the sequence.
G05
Plaintext handling
Specifications and salts must stay out of ordinary application storage and logs.
Connect the whole picture.
Explore the principles that connect each service to the thesis lifecycle.