COMMAND
One objective
A token, an event, a comparison, or a sequence. QUEEN takes the whole of it.
THE AI COURT FOR ONCHAIN INTELLIGENCE
Stop piecing together onchain activity by hand. Give QUEEN an objective. Let specialized agents investigate the evidence and bring the findings together.
PROCEDURE
ONE OBJECTIVE · ONE REPORT
COMMAND
One objective
A token, an event, a comparison, or a sequence. QUEEN takes the whole of it.
QUEEN
One report
Evidence, findings, and the uncertainties SENTINEL would not let through.
The drawing is the procedure. The terminal below runs it. Demonstration fixtures are labelled. A question with no data source stays unanswered.
DEMONSTRATION
Four commands run on labelled fixtures. Anything else is accepted as an objective and returned without invented chain data. No blockchain API is connected.
COURT TERMINAL
NO CHAIN API CONNECTED
The Court is standing by.
Standing by.
Choose a demonstration command, or write an objective. The Court will show QUEEN receiving it, the three roles taking their turn, and then a report — or a clear refusal to invent one.
THE COURT
QUEEN does not replace the seats. She gives them one objective and returns what they can actually say together.
QUEEN
QUEEN receives the objective, assigns SCOUT, ANALYST, and SENTINEL, and presents one consolidated report. In this demonstration that handoff is scripted, so you can see the shape of the Court. It is not an autonomous system, and no model is reading a chain behind the page.
01
Finds what matters
SCOUT is the discovery role. Given an objective, it is meant to gather the activity and the labels that bear on it, and to leave out the rest.
02
Connects the evidence
ANALYST reads what SCOUT brought back. It orders events, states the relationships the records support, and keeps a reading separate from a conclusion.
03
Challenges the findings
SENTINEL looks for gaps, weaker joins, and claims the record cannot carry. Its job is to keep an unsupported conclusion out of the final report.
In the terminal, these roles narrate a fixed procedure. On a demonstration command they work a labelled fixture. On any other objective they stop where the missing data source begins.
Three founding seats are in the procedure you can run. The others are named and not operational.
Discovery and evidence
Interpretation
Challenge and uncertainty
Relationship maps
Historical baselines
Briefings for non-specialists
TOKEN
$QUEEN is intended to become the economic coordination layer connecting tasks, users, and agents.
That intention is not a live mechanism. This site does not sell, stake, or require $QUEEN. Holding a token, if one is issued later, would not by itself guarantee access, profit, or future value.
The denied list is here so those mechanics are not implied. When the token rules are actually specified, this section should be rewritten to match them — not decorated in advance. Nothing here is an offer to sell a token.
ROADMAP
Only the first step is in front of you. The rest is direction, not a claim that the work is done.
One objective, three roles, one report. The terminal on this page runs that procedure on labelled fixtures, and it says so when a question has no source behind it.
Connect a blockchain data API so discovery can return real records. Until that exists, the Court does not pretend a lookup happened.
ANALYST and SENTINEL would then work from what was retrieved, with the same duty to separate a link from a guess. That step is not live, and the roles are not autonomous.
Cartographer, Archivist, and Counsel are named so the direction is visible. They are not in the procedure you can run today.
$QUEEN is reserved as the economic layer between tasks, people, and agents. No fee, incentive, or access rule is in force, and none is promised here.