ARQEN Docs
Reference architecture, module documentation, current proof boundaries, and validation posture. When served from docs.arqen-ai.com, it's routed here automatically.
Each page explains what a buyer or evaluator can inspect today, what remains local/demo, and what production gates are still required. ARQEN documentation is meant to support pilot evaluation and technical review; it is not a compliance certificate, audit report, final controlled-copy release, or SOC 2 report.
What ARQEN is, what it connects, and what remains demo/local or gated.
Screenshot-guided flows for current proof surfaces and planned workflow coverage.
How source records, deterministic logic, advisory AI, and review surfaces fit together.
Evidence references, source-basis context, and the future controlled-storage gate.
Local/demo draft-packet workspace plus future-gated controlled forms, templates, review drafts, and evidence-reference packages.
Why deterministic quality logic comes before advisory AI and human authority stays intact.
How to scope a controlled workflow evaluation without implying production operation.
AS9100-style and AS9102-readiness workflow support without certification claims.
Current trust posture, planned production gates, and what is not yet implemented.
Quality signals, source-basis drillback, and local review-action routing.
Risk and trend signals as local review context, not automated mitigation authority.
Process signals and chart context for review, with production validation still gated.
Effectiveness signals tied to source context and local review decisions.
Drawing characteristics, inspection plans, results, failed characteristics, and Proceed Check.
Local nonconformance lifecycle gates, source basis, and bounded follow-up paths.
Corrective action, verification, effectiveness review, and local action staging.
Local change review context and approved-demo boundaries, not production change approval.
Audit findings, evidence references, staged follow-up drafts, and local Review Actions.
Local risk register workflows and source-basis review, not certified risk acceptance.
Rollups, review pressure, source basis, and local action capture for review meetings.
Complaint intake, investigation, evidence references, and follow-up visibility.
Document review gates and approved-demo state, not final controlled-copy release.
Local training assignments and evidence references, not controlled personnel records.
Local source-basis summaries and exports, not certified reporting.
Local workflow queue context and blocked production automation boundaries.
Integration planning and writeback-disabled boundaries for ERP-connected quality work.
Supplier approval, quality events, staged follow-up, and local evidence references.
External collaboration path remains unavailable until auth, tenant, and data gates exist.
Customer-facing submission and evidence exchange boundaries for future deployment paths.
Local QMS readiness reference context without production certification output or compliance approval.
Module maturity, proof surfaces, roadmap labels, and current limitations.
Local validation posture and future production validation gates.
Local/demo module enablement and import/export boundaries, not production governance.
Module checks and source-basis signals without certified validation packages.
Local Nova harness source-basis checks, not production model validation.
Local engine capability context without production monitoring claims.
Local orchestration steps and review events, not a durable source graph.
Local/dev logs and review actions, not immutable or tamper-evident audit storage.
Local users and roles with production auth and tenant isolation still gated.
Local preferences, LLM route hints, and unavailable production gates.