PCProvider ComplianceRegulatory findings
Discovery finding · not legal advice

Current external authority outranks internal guidance.

Harrison’s guides and mappings are valuable operating aids, but they cannot silently become law. Every application rule needs a source class, effective version, applicability condition and reconciliation path.

Authority orderMaster-pack findingsCommission guidance ↗

Source precedence

  1. 1
    Current legislation and Rules

    Highest external authority, with jurisdiction and effective dates.

  2. 2
    Exact current Commission forms and official guidance

    Controls the questions, declarations, category applicability and submission evidence.

  3. 3
    Approved internal instructions and mappings

    Controls firm workflow only where it does not conflict with current external authority.

  4. 4
    Prior cases and external research

    Fixtures and orientation; never current-case facts or binding requirements.

Internal absolutes requiring reconciliation

The January 2026 guide makes several broad claims that were not substantiated by the current Commission pages reviewed in this run. They remain assumptions until the exact current form pack or authoritative source confirms their scope.

100-point identity verificationthree-month police certificate rule30-day ASIC extract freshnessfixed screening logicblanket PDF restrictionsCategory 6 delivery scopeevery appendix for every applicant
Do not implement these as global validators yet.The correct result may depend on the person, role, category, application question and form version.

Every evidence rule needs a type

TypeMeaningSystem behaviour
official-requiredDirect current authority requires it.Block when applicable and absent.
form-requiredThe pinned application form requests it.Block the relevant question or stage.
conditionalRequired only under explicit facts or categories.Evaluate applicability and preserve the result.
internal-policyProvider Compliance chooses a stricter delivery control.Label it honestly; never present it as legislation.
helpfulImproves quality but is not mandatory.Recommend without blocking.

Regulatory change is a version event

A monitored source change creates an observation, not an automatic production rule. A reviewer compares it to the current source pack, updates mappings and validators, runs the fixed case corpus and releases a new authority version with rollback metadata.

Case safetyAn in-flight application remains pinned to known source versions until a reviewer explicitly migrates it and records the effect on claims and artifacts.