Skip to content
AIRA Pathfinder and ADA header
AIRA Twin Terminal · Governed AI live

Watch AI investigate. See why the answer holds up.

Frame complex questions with Pathfinder, analyse documents with ADA, or use Evidence Lab to inspect how AIRA exposes public sources, inferences and assurance.

One governed decision intelligence core · three applications · one inspectable interface with human control.

Open full-screen live demo →

Live public data · Evidence lineage · Human review remains required

AIRA Twin Terminal Console

Structured first assessment

Describe a situation, policy question, AI-adoption challenge or document text. AIRA returns a first structured assessment in terminal form.

TEST EVIDENCE LAB Use the built-in Twin Terminal analysis or open the visual live showcase.
Language: Auto
AIRA Pathfinder
Question intake
Pathfinder
PATHFINDER.INPUT
Input limit 0 / 12000

privacy: do not paste confidential personal data unless you are authorised to process it.

AIRA Terminal
Structured output
Live
PATHFINDER.RUN

aira:pathfinder$ waiting_for_input

Type input, press Enter or Run analysis, and receive structured AIRA advice here.

status: ready

profile: Pathfinder · structured first assessment

language: auto · same as input

enter: execute

shift_enter: new line

commands: /help · /clear · /demo · /kernel · /pathfinder · /ada

Desktop: twin cockpit. Mobile: swipe left for output, swipe right back. Enter = execute.

TECHNICAL DUE DILIGENCE

Inspect the system boundaries before judging the demo.

AIRA is not a foundation model or generic chatbot wrapper. The technical thesis is a provider-neutral governed decision intelligence layer that brings context, evidence, authority, interoperability and verification together. This public baseline gives CTOs, enterprise architects, CISOs and technical investors enough to assess the architecture without exposing proprietary implementation details.

01System boundary

Architecture

AIRA sits between users and workflows on one side and models, data, agents and enterprise systems on the other. The governed intelligence core controls routing, context, evidence, policy, human authority and verification; underlying models remain replaceable where practical.

02Execution

Runtime flow

The public core sequence is: Prompt → Route → Mode → Lens → Knowledge/Memory → Validate → Card → Attest → Learn. Twin Terminal exposes a concrete runtime route through the Laravel layer to the AIRA analysis service; internal routing rules remain non-public.

03Evidence

Evidence & assurance

Outputs are designed around provenance, evidence lineage, uncertainty and reconstructability. AIAR provides execution-proof objects; ADEC structures claim-evidence-argument relationships. External attestation is an assurance adapter, not the intelligence core.

04Authority

Security & human authority

Human authority remains explicit: review gates, bounded actions, escalation and deployment-specific policies determine what AI may advise, prepare or execute. Security, privacy and access controls are designed as system constraints rather than labels added afterwards.

05Integrations

Interoperability

AIRA is MCP-first where suitable, but not MCP-dependent. APIs, webhooks and adapters can connect existing ERP, CRM, document and case-management environments. Authentication, tenants, roles, retries, idempotency and observability belong to the integration boundary.

06Deployment

Assurance adapters

Attestation is configurable per deployment: Hyperledger Fabric, Hedera, both or off. Fabric supports permissioned governance and endorsement; Hedera can optionally provide public timestamp/order attestation. The use case determines whether a ledger layer is needed.

07Maturity

What is proven?

The live interfaces demonstrate working product and integration components; they do not automatically prove the full platform thesis. AIRA is in structured pilot validation, so claims about value, governance fit and scale become stronger only when they repeat across independent customers.

08IP boundary

Public vs proprietary

System roles, interfaces, governance principles and architecture contracts needed for technical scrutiny can be public. Proprietary routing logic, protected prompts, scoring rules, orchestration policies, source code and other trade-secret implementation details remain outside the public layer.

How to get better Pathfinder output

Describe context, actors, tension and the desired outcome

Pathfinder works best as a first intake for AI adoption, SME questions, digital strategy, policy questions, process improvement, area development and multi-party collaboration.

Include at least
  • • who is asking the question
  • • what is happening
  • • which actors are involved
  • • where tension or risk sits
  • • what you want to achieve
What improves
  • • sharper framing
  • • better complexity assessment
  • • more relevant focus areas
  • • a more concrete first step
  • • usable for discussion or intake
Prompt recipe
Prompt recipe for Pathfinder:

Turn my situation into one strong Pathfinder prompt. The prompt should support a first assessment of a complex question, choice or situation.

Use this structure:
1. Who is asking the question?
2. What is happening in concrete terms?
3. Which actors are involved?
4. Where are the tension, risk or uncertainty?
5. What should the first assessment deliver?

Then write one compact prompt I can paste directly into Pathfinder. Use plain language, no marketing language. Keep it concrete, sober and practical.
First assessment

A fast first structured assessment of a complex question

Three modes

Pathfinder and ADA as applications; Evidence Lab as the live evidence mode

Practical

Not an open-ended chatbot response, but direction, focus areas and a next step

Agent-ready

Prepared for connectable AI-agent workflows and an MCP-ready architecture

What Pathfinder is for

Pathfinder helps frame AI adoption, SME questions, digital strategy, organisational, policy, process and collaboration challenges and determine a first direction.

What ADA is for

ADA helps with existing documents such as memos, policy notes, proposals and reports. The output identifies document type, risks and next steps.

Human review

AIRA supports professional judgement. Its output is a first machine-generated assessment and remains subject to human review.

Need a deeper advisory session?

Pathfinder and ADA are concrete applications; Evidence Lab exposes the research and evidence process. For a deeper strategic, policy or AI assessment, AIRA can take the analysis further.

PRIVACY · GOVERNANCE · CONTROL

Trust is a system requirement.

AIRA treats data minimisation, purpose boundaries, human review, traceability and deployment-specific governance as design constraints—not as a legal badge added afterwards.

We avoid blanket claims that every deployment is automatically GDPR- or AI Act-compliant; applicable obligations depend on the organisation, data, role and use case.

Information security

ISO/IEC 27001 readiness

Security management, access, risk and operational controls are developed against an ISO/IEC 27001 readiness baseline.

AI management

ISO/IEC 42001 informed

AI governance, human oversight and accountable lifecycle management are designed with ISO/IEC 42001 as a relevant reference framework.

AI risk management

ISO/IEC 23894 informed

AI risk identification, assessment, treatment and monitoring are informed by the ISO/IEC 23894 risk-management framework.

Reference frameworks and readiness direction only; this does not claim certification.