Plan the run.Keep it linked.
Shape a public-web task into a local route, then keep three questions separate: what was planned, which evidence set belongs to the run, and which receipt closed it.
A matching digest or receipt can support integrity and linkage checks. It does not prove that page content was true, a task actually ran, a source was trustworthy, or a wallet was anonymous.
A task becomes a route.
A run becomes three linked records.
Plan. Execute deliberately. Prove the run.
Local deterministic planner · no browsing, credential access, or remote execution
Read address + chain ID only.
Create a real SHA-256 plan + receipt pair.
Write the run ID and plan hash to the plan registry.
Commit the ordered plan evidence root in its own contract.
Anchor the final receipt after the evidence root exists.
Query verifiable runs
Deterministic local planning
Create a transparent 3–5 step demo route without sending the full task or plan to a server.
Honest AI boundary
The MVP labels its planner accurately. It does not claim cloud-browser or AI execution when those services are not configured.
Three deliberate records
Keep the run plan, ordered evidence root, and final receipt distinct, with a separate preview and approval for each public write.
Linked integrity checks
Hash canonical local records with SHA-256, then use the shared run ID to inspect how plan, evidence, and receipt records relate.
Three linked records.
Three different audit questions.
1await runPlanRegistry.registerRunPlan(2 runId,3 planHash,4 { value: 0n }5)67// audit question: what was planned?
These records support checks that digests stayed intact and belong to the same run. They do not establish that webpage content was true, that the task actually executed, that a source was trustworthy, or that a wallet or run was anonymous.
Local by
default.
Full task details remain in browser state for this MVP. The planned public path prepares only run identifiers, digests, and an evidence-item count, with a separate wallet action for each record.
Claims you
can inspect.
Built from open
browser primitives.
No account is required for local planning. A compatible wallet is only needed for optional network actions.
Consent is
non-negotiable.
A wallet address is identity, not permission. Traceora separates connection from every consequential action and shows the details first.
Local task context
The full prompt and route remain in browser storage for this MVP.
Read-only connection
Connecting a wallet requests an address and network only—never a payment.
Separated approvals
Plan, evidence-root, and final-receipt writes each require a separate, previewed wallet action.
Truthful finality
Submitted, confirmed, rejected, and failed states are kept distinct.
Small surface.
Clear guarantees.
The prototype uses standard browser capabilities and three compact contract interfaces. Each record has one role, one audit question, and one explicit wallet action.
Browser native
Web Crypto and EIP-1193 primitives.
Canonical records
Stable key ordering before hashing.
Minimal disclosure
Identifiers, digests, and evidence count—not the full task.
Inspectable states
Preview, pending, confirmed, and failed.
registerRunPlan(runId, planHash)// role: runPlanRegistry// value: 0 BOT// asks what was planned
“A receipt should support integrity checks without being mistaken for truth.”
Principle 01
Design tenet, Evidence boundary
Integrity + linkage, not truth
Designed around verifiable boundaries
Three records,
three questions
The three contracts are active on BOT Chain mainnet. Register a plan, commit its evidence root, then finalize the receipt, with separate wallet approval for each action.
BOT Chain mainnet · three contracts active
0 BOT for every call
Network fee shown by your wallet
Run plan
Names the intended route for a run
role / runPlanRegistry
- Question: what was planned?
- Run ID + plan hash
- Exact call: registerRunPlan
- 0 BOT call value
- Network fee shown by your wallet
Evidence root
Binds an ordered evidence set to the run
role / evidenceRoot
- Question: which evidence set?
- Run ID + root + item count
- Exact call: commitEvidenceRoot
- Requires the registered run owner
- 0 BOT call value; network GAS applies
Final receipt
Closes the linked record path for a run
role / finalRunReceipt
- Question: which receipt is final?
- Run ID + receipt hash
- Exact call: anchorFinalRunReceipt
- Requires prior plan and evidence
- 0 BOT call value; network GAS applies
These are planned Traceora record operations—not payments, point claims, or token transfers. A digest can support integrity and linkage checks; it cannot prove content truth, actual execution, trusted provenance, or anonymity. Read the terms
Ready to map
a run you can inspect?
Start with the local planner. Review the run-plan, evidence-root, and final-receipt calls without treating any digest as proof that the task really ran.
Local mode needs no account · BOT Chain mainnet · three contracts active