Technology architecture

ARIADA is the agentic compliance architect for the modern web — multi-agent orchestration that architects compliant systems from L0 Mindset, detects drift continuously across eleven sequential scanner-axes, and remediates at source through autonomous pull-request generation. Instantiated through nine integrated pipeline modules; modules combine into products, products share a single engine, and the same engine scales across all eleven scanner-axes. Source-level remediation only — PRs require client merge; we are not a legal certification body. This page is the architectural overview for technical due diligence.

Agentic compliance architect — eleven scanner-axes

Eleven sequential scanner-axes (L0 Mindset → L10 Legal), with L4 Runtime/Overlay intentionally not built (anti-overlay strategy — conflated detection and runtime remediation is what fined accessiBe). All axes connected by the Ariadne gold thread. We test, we control — agentic suggestions are not autonomous deployments; for accredited certification, customers consult a notified body or registered auditor.

Nine modules — one platform

Each module is a focused capability that snaps into the platform. Marketplace standalones (blamer.ai, clamper.ai, reverter.ai) ship one module each; the umbrella platform ships all nine under one contract. Application numbers, claim counts, and PCT deadlines are disclosed to accredited investors on request via the Legal & IP page.

Module summary. Pipeline stages (P1–P7) are scanner internals — distinct from the eleven scanner-axes (L0–L10) shown above.
Module Capability Pipeline stage
Multi-domain scanSingle-pass multi-domain scan — emits evidence across WCAG, EAA, EN 301 549, Section 508, ADA, DOS-lagen in one passP1 Scanner
LLM remediationTiered LLM remediation — cheap-to-expensive cascade emits source-code patches with cache and reuseP4 Remediation
CI/CD gateDifferential CI/CD gate with policy DSL — stricter thresholds for AI-authored codeP5 CI gate
Regression detectionCross-deploy diff engine that clusters root causes and tracks per-component trendsP2 Diff
Canonical scoringCross-tool canonical scoring — normalizes axe / Lighthouse / Siteimprove / WAVE / Pa11y into one signed scoreP3 Compliance
Backlog optimizerPredOpt MIP + ML backlog optimizer — schedules fixes under sprint capacity, severity, and budgetP4 Remediation
AI authorship attributionMulti-signal classifier identifying Copilot, Cursor, Claude Code, Windsurf, Devin and othersPipeline-wide
AI artifact auditAI artifact audit (HAES) — tamper-evident event ledger with EU AI Act Art. 50 evidence packageP7 Audit trail
Scan visualizationReal-time character-themed visualization for stakeholder reports — same engine as draculascan.comP6 Visualization

Integrated pipeline

Every ScanEvent emitted by the multi-domain scanner flows downstream to attribution (who wrote it), canonical scoring, and the AI artifact audit (EU AI Act compliance). The regression detector trends violations across deploys; the CI/CD gate blocks non-compliant PRs; the LLM remediation cascade suggests source patches; the backlog optimizer schedules the fix queue under sprint capacity; the visualization module turns the numeric report into stakeholder-comprehensible narrative. 

Multi-domain scan ─▶ AI attribution ─▶ Scan visualization
        │                   │
        ▼                   ▼
Canonical scoring    AI artifact audit
(cross-tool score)   (HAES / Art. 50)
        │                   │
        ▼                   ▼
Regression detection   CI/CD gate
(trend + cluster)      (policy DSL)
        │                   │
        └──────────┬─────────┘
                   ▼
        LLM remediation (tiered cascade)
                   │
                   ▼
        Backlog optimizer (MIP + ML)

Scanner-axis coverage

The same engine that scans web accessibility today scales across eleven sequential axes. Each axis adds a rules package and a domain-specific reporter; the scanner, attribution engine, scoring normalizer, and audit trail are reused unchanged.

L0 Mindset, L1 Design, L2 Dev Tools are shipped foundation tier; L4 Runtime/Overlay is intentionally not built (anti-overlay strategy). Adjacent verticals (QMS, document compliance) sit outside the current scanner-axis set.

Engineering stack

Legal & IP → Back to investor overview