The mesh is the single most differentiated capability in Manera, and the reason a Mesh Tier subscription replaces $544K-$2M/yr of incumbent terminals. This article explains what a mesh query is, why no incumbent terminal can offer it, how to ask one, and what it produces.
A mesh query is a single natural-language question that is automatically routed across two or more flagships, with the answers stitched into one synthesized response. Every fact in the response carries a source URL and timestamp. The synthesis itself is SHA-256 hash-stamped for audit replay.
Example. The CFO asks:
"What is our FX exposure on the Brazilian receivables given the current sanctions environment?"
A traditional Bloomberg + Refinitiv workflow would require:
Total time: 2-4 hours. Total cost: 4 incumbent terminals + 1 Excel sheet + analyst hours.
Manera's mesh query produces the same synthesis in under 60 seconds:
``` BRL/USD: 1-σ tail expanded 12% in last 14d (FXWatch) Brazil EMBI sovereign spread widened 38 bps (CreditPulse) Brazil flagged in 3 secondary-sanctions cascades from US OFAC + EU + UK (NEIP) Customer ticker shows 14-day narrative arc tilting bearish (SentimentDNA)
Synthesis: FX exposure has materially worsened. The sovereign spread widening is consistent with the sanctions secondary effects. Bear narrative is forming faster than usual. Recommend reviewing the hedge designation on the BRL receivables before next exec sync.
[SHA-256: 3a8f...] [Source URLs: 12] [Generated: 2026-05-04 09:42 EDT] ```
The structural reason no Bloomberg / Refinitiv / FactSet / S&P Capital IQ can offer a mesh query is simple: they sell raw data, not synthesis. Their economics depend on per-seat licensing of data feeds. Cross-domain synthesis is what their human users do — they are the customer's analyst, not the customer's tool.
A few have tried bolt-on synthesis layers (Bloomberg's "Bloomberg GPT", Refinitiv's "Workspace AI"). All hit the same architecture wall: cross-domain synthesis requires:
Manera was built mesh-first. Every petal publishes to shared/event_bus.py. Every fact card carries provenance. Every synthesis is signed. The architecture is the product.
Open the NexusAI War Room at https://nexusai.maneratech.com/war-room. Type your question. The router decides which flagships are relevant, fetches the data in parallel, and stitches the synthesis.
```
What is our FX exposure on Brazilian receivables given the sanctions environment?
[Routing to: Treasury (FXWatch + CreditPulse + SentimentDNA), Strategy (NEIP)] [Synthesis ready in 47 seconds] ```
The router is conservative — it explains which flagships it consulted and why. You can override the routing if you want to constrain the query (e.g. "only Treasury, not Strategy").
If you want to be precise about which flagships participate, prefix the query:
`` [Treasury][Strategy][Legal] What is our FX, sanctions, and breach-clock exposure for the Brazilian customer onboarding? ``
The bracketed flagships are the only ones consulted. The synthesis is constrained to that scope.
Each flagship ships with mesh playbooks — pre-built mesh queries that map to common operational patterns. Treasury ships with these:
Cyber ships with:
Legal ships with:
See the full playbook list at The Swarm Doctrine.
These cross-flagship combinations are the headline reason customers buy Mesh Tier instead of buying single petals:
Every mesh query produces three artifacts:
The audit hash matters when SOX or SOC 2 auditors ask "where did this hedge designation come from?". You export the lineage as PDF; the auditor verifies the hash; the chain is intact.
To set expectations:
Mesh Tier subscribers ($999/mo) get unlimited mesh queries. There is no per-call meter, no token surcharge, no "pro-rated for cross-mesh usage". This is a deliberate choice — meter pricing on synthesis would re-introduce the procurement-friction problem Manera was built to dismantle.
Standalone-petal subscribers can run mesh queries scoped to their subscribed petals, but cross-flagship synthesis requires Mesh Tier.
← Back to knowledge base · NexusAI War Room · Pricing · Trust Doctrine