Multi-agent research platform · Since 2026
Consiliences AI

One engine. Four publishing arms. Desk-scale research.

live · as of 2026-07-13 Consiliences AI

The multi-agent system that runs everything else -- and the discipline that keeps it honest.

41agents
67tools
207souls
7528tests
5inference providers
Observe → Score → Discard → Surface

Most of what it sees, it throws away.

Each agent observes, scores against its standing goal, discards the overwhelming majority, and surfaces only what survives -- thousands of times a day, with no one watching. It is the loop many agents share; others do the work in the wall above.

Not chatbots waiting for a prompt

Everything one system does -- as a single wall.

Skim it as texture; hover or tap any tile for what that piece actually does. Five families -- Watch, Think, Make, Govern, Evolve.

Scan & surface
score, discard, surface
Read prediction markets
market-implied odds
Track readership
reads to lenses
Watch the macro
regime from FRED
Watch smart money
insider + 13F flow
Ingest market data
prices, ratios, factors
Cross-ref clinical trials
live trial registry
ENSO / climate data
cached climate indices
FAO / agri data
cached food-price data
Notice convergence
near-threshold signals
Detect drift
freshness gates
Web search
on-demand retrieval
Web fetch
direct source pull
VIX / vol series
cached vol data
COT positioning
cached CFTC data
Credit spreads
cached risk gauge
Cycle inputs
cached cycle data
Dedupe GUIDs
seen-before check
Scout patents
IP landscape watch
Probe coverage
source availability check
Decompose queries
query to sub-problems
Run research plans
multi-step reasoning
Synthesise domains
cross-domain merge
Falsify signals
designed to kill
Monte-carlo battery
bootstrap significance
Held-out battery
out-of-sample check
Robustness battery
sensitivity analysis
Detect clustering
echo not confirmation
Verify claims
source-anchored check
Build dossiers
structured evidence file
Debate contradictions
adversarial reasoning
Mediate debates
resolve disagreements
RALPH cycles
iterative refinement
Map mechanisms
cross-cluster links
Score & route
conditional dispatch
Rank candidates
momentum, value, catalyst
Whewell ceiling
evidence-tier cap
Tier signals
A / B / C classification
Embed & retrieve
semantic search
Detect bias
scoring-bias check
Recall across sessions
cross-thread grounding
Write digests
recurring briefings
Commission news
story to publication
Run the debate
multi-voice argument
Publish papers
long-cycle research
Publish essays
Phronopolis output
Gate teasers
B-tier public content
Rank & brief
daily equity brief
Keep a scoreboard
track record vs SPY
Reception notes
weekly engagement desk-note
Generate images
on-demand illustration
Generate charts
data visualisations
Build dashboards
ops stats JSON
Deliver to Telegram
live notifications
Maintain the sites
atomic Hugo publish
Trade-desk notes
daily structured note
Author disclosure
attribution gate
Compose OG cards
social meta images
Cross-wing links
site nav sync
Build sitemaps
sitemap + llms.txt
Notify on new
event-driven alerts
Render provenance
tool-level attribution
Caption honestly
as-of timestamps
Draft under review
Tier-A gated draft
Bundle papers
PDF + Telegram delivery
Paint its own art
local SVG lab-notes
Route to the frontier
quality-gated escalation
Sync a second brain
bidirectional vault loop
Audit itself
agent integrity check
Monitor Observatory
pipeline watchdog
Close findings
escalation-only closer
Gate by trust
four-tier model
Contain subprocess
hardened execution
Air-gapped mode
egress kill-switch
Log everything
human-auditable trail
Govern cost
circuit breaker
Quality-gate lenses
substance before publish
Gate publication
SP4 fabrication check
Lock supply chain
hash-locked deps
Pattern-sweep
bug-class guard
Startup invariants
boot-time assertions
Grade itself against the frontier
drift catch
Dedupe by state
condition-change alerting
HITL approvals
human in the loop
Housekeeping checks
post-edit integrity
Topic-diversity picker
anti-repetition gate
Persona-rights gate
safe attribution only
Verify before done
effect confirmed, not called
Concurrency lock
single-runner semaphore
Improve its own code
platform building platform
Mine its own gaps
self-diagnosis
Propose & apply
atomic change system
Rewrite its soul
performance-driven voice
Commission own fixes
gap to proposal
Promote with evidence
trust level up
Self-heal on restart
persist and restore
Learn from feedback
closed feedback loops
Reconcile registry
agent lifecycle CLI
Backoff failing models
per-model mute
Serialize commits
scheduled auto-commit
Tune its own gates
measured rollout
Distill its own lessons
cross-session learnings
Measure its own improvement
not just active -- working

…and this still isn't everything.

The single rule that keeps autonomy legible

Agents climb. Only a human promotes.

Tier 0 supervised
2
Tier 1 semi-auto
2
Tier 2 monitored
8
⚠ Tier 2 → 3 is a human decision -- never automatic
Tier 3 autonomous
29

Live registry counts as of the latest build — every Tier 3 promotion was a manual operator decision, never automatic.

Built safe and legible before fast

The sandbox is the contract.

Every agent writes only to its own sandboxed working directory. Every consequential action it takes is written to an append-only audit log. Subprocess calls run through a hardened helper with a scrubbed environment and a binary allow-list, and an air-gapped mode can sever all egress. When safety and speed conflict, legibility wins.

Local-first sovereignty

5 cloud providers. One endpoint that decides.

The only mandatory language-model endpoint is a local server the operator controls. Cloud routing across 5 providers accelerates the work but is never authoritative; the system degrades to local-only without losing correctness. It is both a consumer of data -- around three dozen external integrations -- and a provider of it, exposing three Model Context Protocol surfaces.

One engine · four publishing arms

The same engine. Four different voices.

ENGINE
The Institute0 papers / 30d · corpus → Observatory
Angles & Footnotes0 bulletins / 30d
Phronopolis0 essays / 30d
The Engineyou are here
One operator, one fleet

The engine is the artefact. The operator is the consistency mechanism.

The platform was built by a single operator working with a fleet of agents, and it is not separable from that operator: the operator decides what the engine does, what it kills, and what ships. That pairing is not a limitation the work is apologising for -- it is the demonstration the work exists to make.

Engage

Read the architecture, or get in touch.

This subdomain documents the system in depth: the architecture, what the engine does, methodology in code, and how to engage. The instrument above already made the case.

Drafted with AI assistance under operator supervision; substantive claims are operator-authored or operator-approved.