Architecture
ARQEN is organized into system layers that keep quality records, evidence references, lifecycle gates, review actions, and traceability context connected through local source-basis contracts. The current public product proof is demo/local and read-only where production-shaped routes exist; production operation requires the gates below.
Local records, review signals, evidence references, and non-durable traceability context across modules.
Reusable control patterns across inspections, NCR/CAPA, supplier quality, audits, document review, risk, change, training, and complaints.
Lifecycle gates, missing evidence, owner/due status, blocked states, and review readiness are evaluated before advisory AI is involved.
Management Review, Reporting, Traceability, and Review Actions turn source records into review-ready local summaries.
Validation signals and system logs are local review signals; they are not production audit evidence or immutable audit evidence.
ERP, supplier, customer, and workflow automation surfaces show planning/source-basis context while production exchange remains gated.
Production gates
Backend-ready contracts exist for future durable operation, but the public system does not enable production writes until these gates are implemented, verified, and approved.