REGULIS / OPS
CONN OK
AUTH OK
SYNC LIVE
12 ALERTS
TENANT · SVA
ENV · PROD
UTC --:--:--
ReGulis
Aviation Compliance Intelligence
Connecting to API...
ReGulis / Command Center
COMPLIANCE READINESS D-263 to audit
0:00
Command Center
Your compliance posture, what ARIA found, and what to do next
// 01 Canonical Compliance Pipeline
8 STEPS
// 02 Coverage Posture by Section
D/I/E ENGINE
// 03 Priority Alerts
// 04 Module Health
11 MODULES
// 05 Recent Activity

COMPASS — Requirements Browser

Select a requirement to view details

VAULT — Document Intelligence

Folder-sync · ARIA classification · OCR detection · Pipeline ingestion
📁
Set Your Compliance Document Folder
Point Regulis to your local compliance documents folder. ARIA will scan it, classify each document, and ingest everything automatically.
💡 Recommended Folder Structure
📁 Compliance Documents/
  📁 01-Standards/ → IOSA, ICAO, FAA, EASA
  📁 02-Operations/ → OM-A, General Ops
  📁 03-Dispatch/ → OM-B, Dispatch
  📁 04-Training/ → OM-D, Training
  📁 05-Safety/ → SMS, Safety reports
  📁 06-Technical/ → MEL, AOM
  📁 07-Cabin/ → Cabin crew manual
  📁 08-Security/ → Security manual
  📁 09-Evidence/ → Audit records
  📁 10-Scanned/ → Old scanned docs (OCR)
Subfolder names help ARIA pre-classify documents accurately. Flat folders also work.
Uploaded Documents
Loading documents...

Composer v2.0

Operator-tailored manual section drafter. Pick a manual + section — ARIA reads your Operator Profile, the regulatory requirements, and any existing operator prose, and drafts the section in your voice. Cites every paragraph. Marks any operator-specific fact still missing as a red [OPERATOR-*] placeholder. On-demand only — sections drafted only when you open them.

Loading templates…

Select a section to draft

Pick a manual on the left, then a chapter, then a section. ARIA will draft the prose tailored to your operator. Drafts are cached — switching to another section keeps prior drafts.

REHEARSAL — Audit Simulation

Audit simulation using ISM 18 data. Answers are deterministic (D/I/E scoring engine). History securely stored.
Audit Configuration

REPORTS — IOSA Readiness Reporting

Generate IOSA Readiness Report

Corpus Health

How well the regulatory corpus and operator manuals were digested. Grades A-F. Refresh to recompute.

Loading…

Contradictions & Completeness

ARIA-detected conflicts between your operator manuals and the regulatory requirements they map to. Every finding cites the clause and the conflicting manual text.

Loading…
Severity:
Manual: Section: Sort:
No contradiction results yet. Click Run Sweep above to start the ARIA audit (requires ARIA Advisor key in Settings).

Workflow Guide

What reGulis does, end to end. Eight canonical stages plus five cross-cutting capabilities. Click any card to jump there. Status pills show how complete that stage is given your current corpus.

Canonical 8-Stage Workflow

Cross-cutting Capabilities

What reGulis is NOT

reGulis is the compliance reasoning engine — it tells you when your manuals fall out of alignment with regulations, drafts the fixes, and tracks them through closure with an auditor-visible signature trail. It is not an EFB content distribution platform (Comply365 owns that), an SMS hazard-reporting product (iQSMS owns that), or a crew rostering / training-records system (Air Maestro owns that). Use reGulis alongside those, not instead of them.

CAPA — Corrective & Preventive Action

Walk every recommendation and contradiction through assignment → evidence → closure with an immutable audit trail. Auditor-visible signature on every transition.

Status: Owner:
Loading CAPA records…

Sign-off Inbox

Read-and-sign attestations awaiting your acknowledgement. Every signature is recorded with role, timestamp, and IP — auditor-visible immutable trail.

Role:
Pick a role above to load pending sign-offs.

Publish Audit

Cross-manual immutable timeline of every revision ever published. Stable revision IDs in ${MANUAL}-Rev${N}-YYYYMMDD format span audit / attestation / rollback.

Show:
When Revision ID Manual Action Location Source Accepted by
Loading audit trail…

SME Review

Stratified sample picker + printable validation packet for third-party Subject Matter Expert review. Decisions land in the immutable audit log.

Past runs
Loading…

Retrieval Health

Synthetic gold set + hit@k + MRR scoring on the live retrieval pipeline. Run before AND after any retrieval-stack change.

Latest scores
Live query tester — classifier + full retrieval

  
Preference reranker (P8)
Loading…
Pipeline status (live)
Loading…

ARIA — Compliance Advisor

ARIA-powered aviation compliance intelligence

ARIA Configuration

Local

ARIA can run in Local mode (no external calls) or Advisor mode (connect one or more language-model back-ends below). ARIA Vision & Deep Understanding require at least one advisor with a valid key.

Additional advisors (optional)

Analyse my library

Finds gaps between your manuals and the regulations, detects contradictions, and drafts amendments. About 15 minutes for a typical airline.

// Advanced · run individual stages

For re-runs after fixing a specific step. The Analyse button above runs all of these in the right order.

INSPECTOR — Compliance Review

Review requirements against your manuals

Requirement Section Type Manuals Coverage % Review Action
v1 · DEPRECATED These amendments are from ARIA v1 and require careful review before acceptance
The 1,349 amendments listed below were drafted by ARIA v1 and have known quality issues: some are routed to the wrong manual (e.g. SMS requirements landing in IATA-DGR), section titles do not always match amendment content, and prose is often generic boilerplate rather than operator-tailored. Do not bulk-accept. Review each on its own merits, or wait for ARIA Composer 2.0 to re-draft from a stronger architecture.

ARIA Composer 2.0 (in active development) will produce tailored amendments with exact-paragraph anchoring, edit-before-accept, refuse-to-draft when grounding is thin, and Implementation Impact notices. View Composer 2.0 status →

Amendments what's this?

Review what ARIA drafted, accept or reject, then build a revision

v1 · REVIEW Publishing a v1 amendment commits its content into the manual revision log
Amendments shown for publishing here were drafted by ARIA v1 and may be generic, mis-routed, or low-confidence. Once published, they enter the operator manual’s formal revision history and an Implementation Impact notice is attached. If the amendment is generic boilerplate or routed to the wrong manual, reject it — do not publish. ARIA Composer 2.0 will re-draft these properly.

Publish what's this?

Release the accepted amendments · issue a new manual revision · export change-bar DOCX

// placeholder rule // Any text shown in [OPERATOR-*], XXXXXXXX or ??????? must be replaced with your operator-specific value (FDP cap, AE name, AOC number, etc.) before publication. ARIA cannot authoritatively assert these facts so it inserts placeholders that render red in both the app and the exported DOCX.

// manual versions

Each manual gets bumped one minor version per amendment. Published amendments advance the revision number; pending ones stay in draft.

MANUALS — Document Reader

Browse and search ingested manuals

Indexed Manuals

Manual Type Secs Reqs Open Status

BLUEPRINT — Manual Builder

Generate compliant manual sections from requirements

Operator Profile

Your operator identity, AOC, fleet, post-holders, FDP caps, and SMS policy. ARIA Composer reads this whenever it drafts a manual section or amendment — every [OPERATOR-*] placeholder is replaced with the real value from here. Empty required fields will be asked of you during drafting.

0%

Profile setup not started

Fill the required fields below. Until this is complete, ARIA Composer cannot draft tailored manual sections or amendments — it will fall back to asking you for each missing fact.

Profile is auto-saved on every change · persisted to apps/api/data/operator_profile.json

Amendments v2.0

Composer-drafted amendments — coverage-first (no draft if requirement is already covered), exact-paragraph-anchored (slot into a specific spot in the manual), edit-before-accept, refuse-to-draft when grounding thin (no boilerplate). Every accepted amendment generates an Implementation Impact Notice with named owners, deadlines, and verification checklist.

Select a requirement

Pick a requirement on the left to see (or generate) its amendment. Coverage check runs first — if your manuals already address it, ARIA cites the existing prose instead of drafting a new amendment.

DATA MANAGEMENT — Admin Console

Upload Standards

Upload a pre-parsed standards JSON file (e.g. ISM 18 digest with requirements array). Uses additive merge — safe to upload multiple frameworks.

Upload Manual Digests

Select one or more *_Digest.json files. Manual key and type are auto-detected from filename. Supports multi-select.

Activity Log

Notifications
No notifications