Manera Knowledge Base · Getting started

Mesh queries: ask one question, get answers across 9 flagships

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.

What is a mesh query?

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:

  1. Pull BRL/USD on Bloomberg, eyeball the 14d move
  2. Switch to Refinitiv, look up Brazil EMBI sovereign spread
  3. Switch to a sanctions list (OFAC website or Lexology), check for Brazil cascades
  4. Switch to Bloomberg's narrative search, check for bear-thesis formation on the customer ticker
  5. Synthesise it in Excel by hand, with no audit chain

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] ```

Why incumbents cannot offer this

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:

  1. A unified schema — Manera's petals share a Common Fact Card schema; Bloomberg's data feeds do not
  2. Shared event bus — when NEIP flags a sanctions cascade, FXWatch + CreditPulse + CommodityWatch must pick it up automatically; this requires a publish-subscribe layer
  3. Provenance chain — every cross-app fact must carry source URL + timestamp + SHA-256 forward through the synthesis
  4. Single tenant — a mesh query crosses confidentiality boundaries; doing this safely on a per-seat-licensed feed requires fundamentally different licensing economics

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.

How to ask a mesh query

Method 1 — natural language (recommended)

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").

Method 2 — explicit cross-mesh

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.

Method 3 — saved playbooks

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.

The 7 unbeatable mesh combos

These cross-flagship combinations are the headline reason customers buy Mesh Tier instead of buying single petals:

  1. Cross-Border M&A — Treasury (FXWatch) + Strategy (NEIP) + Legal (LexiWorld). FX hedge + sanctions screen + jurisdiction-conflict analysis in one synthesis.
  2. EEOC-Defensible Hire — TalentIntel + Legal. Bias-checked candidate scoring + EEO-1 PDF + statute-citation defense in one workflow.
  3. AI Zero-Day Defense — AdversarialAI + NexusAI + ThreatPulse. 142-probe red-team + ATLAS mapping + active-exploit cross-match.
  4. Real-Time Attack Path + Reg Clock — Cyber (CloudPulse + EndpointPulse) + Legal (LexiWorld). Active attack path + 72-hour breach-clock countdown.
  5. Mesh-Triggered BCP — Cyber (ResiliencePulse) + Strategy (NEIP) + Treasury (CreditPulse). Sanctions cascade triggers BCP playbook + supply-chain credit risk re-scoring.
  6. Self-Improving Trading Desk — Trading (Oracle) + Treasury (FXWatch + EarningsIntel) + NexusAI. Brier-score outcome calibration + ±2 conviction adjust on next-trade.
  7. EU AI Act Conformity-by-Construction — Legal (LexiWorld) + AdversarialAI + NexusAI. Continuous evidence generation as the regulation evolves.

Provenance and audit

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.

What a mesh query does not do

To set expectations:

Mesh query pricing

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.

Related articles


← Back to knowledge base · NexusAI War Room · Pricing · Trust Doctrine

Start 30-day Mesh Tier trialAll KB articles
Manera Technologies Inc. · Knowledge base · Blog · Pricing · Trust Doctrine · Contact