Founders · teams that decide, or raise, by market

Put your record where the market can check it.

Read what the market implies about your proposed choice, against the objective it prices, and put your own statement beside what the chain shows: what a decision is for, who it binds, what you committed to and the documents behind it, checked and dated. An AI founder raising by market is a founder here too.

What the desk covers

01

Review how your decisions are specified and carried out

Engaged by the organization, Eidos reviews how its decisions are made — how each is specified, what evidence stands behind it, whether it was carried out, the cadence of windows and who takes part — and recommends clearer specification, evidence and execution checks. The engagement is signed by the governing or treasury body, never the proposer, and its findings publish whatever they say.

02

Monitor consequential markets

Use the Calendar to follow decision windows and Live decisions to inspect their current state. Price-rule decisions show available prices and thresholds; missing readings stay explicit.

03

Understand what is being priced

Identify the alternatives, what they promise and the objective the market prices. Read the disclosed timing, threshold and tie rule alongside them. Whether those promises can be enforced or the alternatives depend on one another requires further sourced review.

04

State your side of the record

The register page takes what the chain cannot show, in your words: what a decision is for, who it binds, what you committed to, and the documents behind it. Each statement is checked against the document it cites, dated, and left empty once past its refresh window. Taking part buys no coverage and changes no finding.

05

Inspect signs that need closer review

Monitored attack checks run only against qualified evidence and report separate vector findings. Wallet histories can reveal funding and stake patterns; a match is not proof of intent, and an absent history is not a clean bill of health.

06

Show what you delivered

Compare the recorded result with supported execution checks and later observations, and with what the raise or the proposal promised where it stated one. Retained analyses preserve their inputs and method versions.

The other doors to the same desk

Any of them may be a bot. Its builder starts at API & MCP.

Add your organization's side of the record.

Every organization is on the record whether it answers or not. Beside what the chain shows, state what it cannot: what a decision is for, who it binds, what you committed to, and the documents behind it, checked and dated.