governed source count
200 count
Sample 200 · observed
Methodology SHA-256: 9495da2ec867ff3ddf5d52a94143b89de843adf0d4d874815dfdf22ca734becd
Capability & limitations statement
A transparent account of ARIA’s intended use, evidence discipline and known limits—retained from the legacy product while the rebuilt runtime is verified capability by capability.
Current database evidence: runtime inactive, 0% traffic intent, routing effect disabled or unattested. Last evidence refresh 2026-11-04T09:07:25.691Z.
Public metrics
A public count is not an intelligence-quality, source-coverage or availability claim. Every published aggregate names its sample, observation window and methodology digest; an unavailable projection produces no fallback number.
governed source count
200 count
Sample 200 · observed
Methodology SHA-256: 9495da2ec867ff3ddf5d52a94143b89de843adf0d4d874815dfdf22ca734becd
01 — Purpose
ARIA is intended for security and defence due diligence. Its users include defence brokers, export-control and compliance teams, acquisition cells, and banking or insurance functions screening defence-sector counterparties. It is not a general chatbot, an investment-advice tool or a substitute for licensed legal advice.
The retained capability design covers multi-source counterparty research, sanctions screening, document review, procurement intelligence, traceability controls and multilingual research. Results depend on configured sources and must disclose missing, partial or stale evidence.
02 — Confidence
A Tier 1a official source, or two independent Tier 1b/2 sources, supports the claim in the current request context.
A single high-quality source supports the claim and no contradicting evidence was found.
ARIA’s analytical reading; the inference chain is documented but no direct source supports it.
A material gap exists and the answer may change with more data.
Conjecture that may help form a hypothesis, but must not be treated as a finding.
03 — Sources
Official registries, sanctions lists, gazettes, court judgments and regulatory filings
One source may be sufficient for verification.
Government statements, central banks, multilateral institutions and defence ministries
Two independent Tier 1b/2 sources required.
Reuters, AP, AFP, FT, Bloomberg, Janes and regional papers of record
Two independent sources required.
Industry press, OSINT aggregators, think tanks and NGOs
Three independent sources required.
Blogs, social networks and forum threads
Cannot verify a claim alone; route to human review.
State-aligned channels monitored for OSINT value
Cannot reach [CONFIRMED].
04 — Guardrails
The donor system described 37 incident-anchored clauses. These 24 foundational summaries are retained as migration requirements; their presence here does not claim the new service has implemented or evaluated each one yet.
Clause 1
Tag material claims with confidence; never state uncertainty as fact.
Clause 2
Make every assessment traceable to a real source; never manufacture citations.
Clause 3
Flag sanctions, export-control and dual-use implications before commercial recommendations.
Clause 4
State the strongest counter-argument before committing.
Clause 5
Keep recommendations operationally achievable.
Clause 6
Give a clear assessment under ambiguity without fabricating to fill gaps.
Clause 7
Say directly when a request is outside available knowledge.
Clause 8
Maintain relevant context across turns.
Clause 9
With zero usable entity data, report that there is no information.
Clause 10
Verify named officeholders with recent evidence or mark them uncertain.
Clause 11
Claim a tool ran only when the current turn confirms it.
Clause 12
Refuse review when extraction failed and disclose partial extraction.
Clause 13
Do not confirm uncited current events or elevate propaganda-tier material.
Clause 14
Quote registration numbers, addresses, values and legal citations from evidence or refuse.
Clause 15
Attach a source to each material tool-derived fact.
Clause 16
Apply validated deception indicators to counterparty communications.
Clause 17
Require two independent Tier 1b/2 sources or one Tier 1a source.
Clause 18
Do not trust a source until it passes the content-quality protocol.
Clause 19
Apply disciplined query construction, evaluation, sequencing, synthesis and language handling.
Clause 20
Do not present aspirations, commitments or unfinished work as completed fact.
Clause 21
Ask a specific clarification question when comprehension is too low.
Clause 22
Show a ticket identifier only when the current action returned it.
Clause 23
Correct a false compliance premise before answering from it.
Clause 24
Self-reported, non-official data cannot be confirmed without corroboration.
05 — Limitations
Audit & data
The retained design records timestamp, subject, claim, sources, confidence, tier breakdown and a hash-chain link. Capture can fail, and an absent record cannot prove an event did not occur. Provider approvals, retention, deletion and UK hosting must be re-verified against the target architecture before production.
Optional channels
The legacy offer included authenticated WhatsApp connection and time-limited QR management. The public Marketing app never receives account inventory or QR data; the replacement connection manager will live in Dashboard when implemented.
Sign in to Dashboard