Skip to content
Tredy · AXA PoC

Architecture & platform

Every AXA use case runs on the same platform. Nothing is one-off code — the same engine, playbooks, and governance power all of them.

The building blocks

Service engine

A service-agnostic runtime that executes each service as a staged run — with pause, resume, retries, timeouts, and durable state.

Playbooks

Best-practice templates (regulatory / policy / security-control gap analysis, regulatory monitoring) that bring a proven tool chain, quality gates, and a deliverable format to every generated service.

Capability registry

Read-only capabilities (search, document extraction, retrieval) are freely composable; anything that distributes or exports is reachable only through an approval-gated stage.

Governance & evidence

Maker–checker sign-off, signed deliverables with content hashes, and immutable gate results — an audit trail on every outcome.

How work flows

  1. Author — a plain-language need is matched to a playbook and assembled into a governed service definition.
  2. Lifecycle — the definition moves draft → validated → submitted → approved → published → installed, fully audited.
  3. Run — the engine executes the service against real sources, grounding every finding in a citation.
  4. Approve — a human reviews and signs before any distribution or export.

How answer quality is measured

The compliance engine’s answers are scored on an 8-dimension review rubric (0–16) by the audit_compliance_service harness, against real regulation records and internal policies.

See Results & maturity for the current scores — including the honest headline that no sampled output has yet passed the production-acceptance gate.

The AXA workspace

The PoC runs against a dedicated workspace: a document corpus, a vector index for retrieval, and org-scoped configuration. The compliance capabilities exercised here — gap analysis, evidence checks, regulatory horizon, and the rest — are documented in Services & capabilities.