01
Package Applicability
Applicable, Not Applicable, Potentially Applicable or Validation Required.
AIRRP separates enterprise-level relevance from detailed obligation applicability, then converts applicable requirements into a governed baseline for implementation and assessment.
This avoids starting every compliance programme with hundreds of questions. AIRRP first evaluates governed enterprise context against package-level applicability logic, then asks package-specific progressive questions only when more detail is required.
Applicable, Not Applicable, Potentially Applicable or Validation Required.
Ask only the additional governed questions needed for detailed obligations.
Show the exact applicable requirements with rationale, mappings and proof expectations.
Reuse normalized controls across multiple requirements and frameworks.
Freeze the approved implementation baseline with version and scope lineage.
Bind assessments to the published baseline so execution cannot drift silently.
For material progressive applicability decisions, AIRRP can require an authorised human Yes/No response. Existing context may support the user, but it does not silently replace a governed answer.
Once requirements are applicable, AIRRP connects them to Master Controls, evidence expectations and implementation work so teams can move from legal or framework text into operational action.
A governed baseline preserves which requirements, package versions, scope and applicability decisions an assessment was based on.
Move from “Does this apply?” to a governed, assessable implementation baseline.