Data contract boundaries resolved; idempotency keyed on webhook event ID.
RAdversarial Red Teamer
Replay vector on retry storm: debounce claim window to 30s.
PProduct & UX Strategist
First-run success signal: user copies spec within 90s of landing.
OImplementation & Operations
Ship order: contract tests before the dashboard UI. Gate: green CI.
ARPO
The Council
Four perspectives. One accountable brief.
Each juror examines architecture, risk, user value, or implementation. A separate quality review checks the plan and calls out unresolved issues.
A
Chief Systems Architect
System boundaries, data contracts, concurrency, and capacity.
R
Adversarial Red Teamer
Failure modes, security surfaces, races, and missed states.
P
Product & UX Strategist
User journeys, MVP scope, success signals, and friction.
O
Implementation & Operations
Delivery sequence, testing, telemetry, and release gates.
Inside your coding agent
Mantrana now speaks MCP.
Connect Claude Code — or any MCP client — and the council joins your agent's tool loop. Your agent files the brief with real evidence from your codebase, the same four jurors deliberate, and the reviewed plan lands in the session before code gets written.
1
Issue an API key
Sign in, open the account menu → Developer & credits, and create a key. Keys look like mk_…, are shown once, and revoke instantly.
Your agent calls mantrana_specify with the brief. The jurors deliberate — and can pause mid-run to ask you questions through your agent — then file the plan with its quality report straight into the session.
One wallet, every surface. A single USD credit balance funds plans on the website and through your agent — top up once, spend anywhere. Failed runs refund automatically.
A Markdown specification you can copy or download, the specialist reviews, and a quality report. The plan sets out implementation decisions, verification steps, and unresolved issues for you or your coding agent to review.
How long does a run take?
Allow several minutes; timing varies with review depth, queue load, and the complexity of your brief. Progress appears as the council works. Runs can pause for your answers, which adds time. A run still queued after 30 minutes is canceled and its credits return to your wallet.
Am I charged for a draft?
Yes. A completed plan with unresolved blocking issues is labeled “Draft — review required” and uses normal run billing. Failed runs and runs canceled while queued receive a credit refund.
How is my data handled?
Your brief and supplied context are processed by AI providers to prepare the plan. Runs are saved to your account. Publishing creates a public share of the plan and review text; raw planning context and private repository evidence packs are excluded, but quotations may appear in the output. Review the content before sharing and keep credentials out of your brief.
Describe it rough. Ship it right.
Sign in, bring your idea, and choose your review depth.
Specimen record
A filed Mantrana specification
ARPO
Four specialist filings converging into one record…