Skip to content

Scope

What deeplinq does — and what stays with you.

deeplinq is middleware. The decisions that bind you remain yours. This page consolidates the boundary statements that appear, in context, across vertical pages — grouped by category for procurement, compliance, and audit teams who want them in one place.

Section 1

Compliance & certification

deeplinq is architected for compliance. It does not certify, license, or validate the institution's regulatory posture.

  • deeplinq does not certify GxP compliance — no platform can. Compliance is a property of your validated system, your quality organization, your QP, and your regulatory function.
  • deeplinq does not certify MDR or IVDR conformity and does not submit to regulators. It produces documentation drafts and surfaced-evidence indices regulatory affairs reviews, validates, and submits.
  • deeplinq does not certify telecom regulator compliance — no platform can. Compliance is a property of the operator and of the operator's existing certifications.
  • deeplinq does not certify procurement compliance or sovereignty qualification — no platform can. Qualification is a property of your sovereign-cloud posture, your procurement process, your data-protection officer, and your oversight relationships.
  • deeplinq does not certify that a HACCP posture will pass an audit — no platform can. The audit-readiness work stays with the quality team.

Section 2

Adjudication & decisions

Adjudication, approval, and authorization stay with the institution's licensed staff. The platform retrieves, surfaces, and archives — humans decide.

  • deeplinq does not adjudicate quality decisions, does not sign batch releases, does not own pharmacovigilance signal closure.
  • deeplinq does not own the QMS, does not adjudicate CAPAs, does not certify inspection-readiness.
  • deeplinq does not adjudicate signals, does not author the medical review, does not author the PSUR.
  • deeplinq does not adjudicate supplier qualification status, does not approve change notifications, does not close audit findings.
  • deeplinq does not detect fraud and does not decide on fraud. It enriches the analyst's view.
  • deeplinq does not auto-resolve, does not auto-credit, does not modify the contract.
  • deeplinq does not push configuration, does not auto-rollback, does not raise change tickets.
  • deeplinq does not adjudicate safety decisions, does not bypass the change-management process.
  • deeplinq does not auto-route, does not auto-allocate inventory, does not auto-issue purchase orders.
  • deeplinq does not adjudicate sustainability metrics, does not certify scope-3 calculations, does not replace the customer privacy framework.

Section 3

Federation across organizations

By design, deeplinq does not aggregate or federate data across customers. Sovereignty is preserved at the institution's perimeter ; intelligence is built from the institution's own archive, not from a network.

  • deeplinq does not federate pharmacovigilance data across organizations, does not build networked safety intelligence, does not pull signal patterns from outside the sponsor's own archive.
  • deeplinq does not federate citizen data across administrations, does not build cross-service citizen intelligence, does not reach into systems operated by other public institutions.
  • deeplinq does not federate inter-service knowledge work across administrations, does not build cross-agency policy intelligence, does not pull note-preparation patterns from outside the institution's own archive.
  • deeplinq does not aggregate research data across institutions ; sovereignty is preserved at the institution's perimeter.
  • deeplinq does not ask suppliers, CDMOs, or downstream partners to integrate, federate, or exchange. It does not reach into their systems.

Section 4

Sector-specific authority

Sector-specific authority — quality release, lawful interception, regulatory submission, safety-management ownership — remains with the institution's existing functions. The platform supplies the evidence trail those functions expect to see.

  • deeplinq does not replace the Qualified Person ; it surfaces archive intelligence the regulatory and quality functions verify.
  • deeplinq does not own pharmacovigilance signal closure ; the safety function decides which signals to escalate.
  • Lawful-interception is out of scope and stays with the operator's dedicated LI system.
  • deeplinq does not author the regulatory submission ; regulatory affairs reviews drafts, validates, and submits.
  • Safety compliance stays with the operator, the safety management system, and the certifying staff under licensure.
  • Auto-rebooking and auto-compensation stay with the customer-service agent — the system drafts, the team approves.

These boundaries are intentional. They protect your authority, not deeplinq's flexibility.