ARQdocs
ARQdocs now has an early local/demo packet workspace inside the platform. It lets teams stage module-linked draft packets for inspection plans, FAIR readiness, NCR/CAPA forms, review packets, and evidence-reference packages while preserving source-basis, readiness gaps, and human review boundaries. Controlled production forms remain a future gate.
Quality teams often rebuild forms and packets from the same records they already reviewed. The current workspace is a local draft-packet surface, not a controlled record engine. It helps expose the shape of future ARQdocs forms without creating controlled records, certified forms, final controlled copies, e-signature approvals, controlled evidence storage, durable repositories, production writes, or durable cross-module links.
Current local workspace
Template catalog
Early local/demo packet templates cover inspection plans, FAIR readiness, NCR/CAPA forms, management review packets, and evidence-reference packages.
Local packet readiness
Each draft packet evaluates required fields, source-basis coverage, evidence-reference coverage, and missing review gates before human review.
Source-basis and evidence references
Draft packets can carry source records and evidence-reference metadata without claiming controlled storage or durable cross-module links.
Local Review Action staging
Blocked or incomplete packets can stage a local Review Action that keeps owner, due-date, evidence, and boundary context visible.
Value streams
Inspection and FAIR readiness
Inspection plan forms, reviewed drawing characteristics, local FAIR readiness drafts, and source-basis references can stay tied to the records that produced them.
NCR and CAPA forms
Nonconformance, containment, disposition, root-cause, corrective-action, verification, and effectiveness fields can be shaped into guided local review drafts.
Review packets
Management review, supplier quality, audit finding, and document-control summaries can carry the same source-basis and evidence-reference boundaries as the operating modules.
Evidence-reference packages
Evidence references can be organized for human review without implying controlled evidence storage, immutable audit, certified reporting, or final controlled-copy release.
Truth boundary
- ARQdocs v0.1 exists as a local/demo draft-packet workspace, not a standalone document-control authority or controlled form system.
- Current public pages and platform surfaces do not claim controlled records, e-signature, certified forms, audit-grade packets, controlled evidence storage, final controlled-copy release, or production write capability.
- Review drafts remain human-controlled and must preserve source-basis, owner, due-date, evidence-reference, and missing-gate context.
- Production use would require production auth, tenant isolation, durable persistence, controlled evidence storage, audit-event persistence, and release governance before stronger claims.