The ARC™ Framework is built on a validated configuration of Atlassian Cloud products and controlled software components. Our architecture follows two core principles that ensure your QMS remains stable and easy to manage as you grow:

• Modular Stability (Weak Coupling): We keep the different parts of your system—like your login security, your core settings, and your specific quality processes—separate from one another. This means if you want to improve your CAPA process, you don't have to worry about breaking your login system or re-validating your entire IT foundation. It makes maintenance simple and keeps your "validation burden" low.

• Process Focus (Strong Cohesion): Every tool in the framework is laser-focused on one specific job. The Risk Management tools only contain what is needed for Risk; the Training tools only contain what is needed for Training. This prevents "feature clutter," making the system intuitive for your team and ensuring that auditors find exactly what they are looking for without wading through irrelevant data.

In the ARC™ Framework, traceability is defined as the Digital Thread of Design Input Requirements. 

It is not a static document, but a bidirectional link that ensures every technical decision is grounded in a requirement and confirmed by evidence.

• Design Input Flow: We maintain a direct link from User Needs (PRS) to Functional Requirements (SRS), ensuring that every business and regulatory goal is translated into a technical specification.

• Integrated Risk: Every requirement is linked to its corresponding Hazard Analysis or Cybersecurity Threat, ensuring that mitigations are built directly into the Architecture and Technical Design.

• Verification Evidence: The thread concludes with a link to Test Executions, providing absolute proof that every design input has been verified and every risk has been mitigated.

The ARC™ Framework utilizes a comprehensive set of 36 pre-configured issue types to enforce process rigour and data integrity. These work items form the "Digital Thread," ensuring that every action—from a high-level quality objective to a granular test execution—is attributable, traceable, and audit-ready.

Every workflow in the ARC™ Framework is designed around the principle of State-Based Edit Restrictions. By leveraging Jira workflow properties, we can ensure that once a record reaches a terminal or approved state, it becomes read-only.

• Lifecycle Gates: Mandatory transitions (e.g., Assessment → Approval) ensure that no design change or quality event can bypass the required regulatory oversight.

• Electronic Signatures: Integrated with eSign for Jira, critical transitions require a 21 CFR Part 11 compliant signature (Username + Password + PIN) to proceed.

• Evidence Capture: Transition screens are configured to mandate the entry of objective evidence (e.g., verification results, root cause analysis) before a status can be advanced.

The ARC™ Framework includes a comprehensive library of fully-authored, ISO-aligned procedures. 

These are not empty templates; they are substantive documents orchestrated by the Quality Manual to provide a complete regulatory roadmap.

• Regulatory Coverage: The library covers all clauses of ISO 13485:2016 and is aligned with primary standards including ISO 14971 (Risk), IEC 62304 (Software Lifecycle), and IEC 81001-5-1 (Cybersecurity).

• Operational Flexibility: These procedures are generic enough for immediate use but are designed to be tailored, extended, or replaced to fit your specific organisational needs.

Exclusion: Note that manufacturing and production processes are not included, as these are bespoke to each customer's specific device and operations.

The ARC™ Framework is built on the principle of Freedom to Operate. Unlike traditional multi-tenant eQMS platforms that function as "Black Boxes," the ARC™ Framework is deployed directly into your own Atlassian Cloud instance. This architecture ensures that your regulatory data remains under your absolute control.

• Total Data Sovereignty: You maintain 100% ownership of your Design History File (DHF), Medical Device File (MDF), and all Quality Records. TrueNorth has no "kill-switch" and no back-door access to your data post-deployment.

• Perpetual Asset Ownership: Your investment in the ARC™ configuration is a permanent organisational asset. You receive a perpetual, royalty-free license to use, adapt, and extend the framework as your product and team evolve.

• Validated Baseline & CSA: TrueNorth provides the initial validated baseline and configuration rationale. Because the system resides in your instance, you own the ongoing Computer Systems Assurance (CSA) and maintenance, ensuring your QMS remains fit for its intended use without external vendor dependency.

• Infrastructure Transparency: By leveraging your own Atlassian infrastructure, you eliminate the "SaaS Tax" often associated with regulated software, benefiting from Atlassian’s enterprise-grade security and uptime at a transparent, predictable cost.