Policy and Regulation Watch with every version kept
A watch on the official sources you name, OSFI's guidance among them where it applies: it records each version, reports real changes with links, and never reports “no change” when a source failed.
The problem it answers
Changes in rules are noticed late, by chance, and iSystematic's Policy and Regulation Watch replaces chance with a deliberate check of named official sources.
What it does
The watch checks a list of named official sources, records the date and version of each, and reports real changes with links to the originals. It tells a true change in a source from a change in its formatting.
When a source cannot be read, the run says so: a failed source produces a failure notice, never a “no change” report.
It gives no legal advice and changes no policy. A person interprets each change and decides what follows.
For a federally regulated financial institution, the list can include OSFI's guidance pages, so a change to Guideline E-23, which takes effect on 1 May 2027, is recorded with its version and a link.
Municipalities use it as a legislation watch.
Built from
It is built from one catalogue workflow and three catalogue patterns.
| Id | Name | What it brings |
|---|---|---|
| W21 | Public Policy Watch | Checks sources, records date and version, detects a change and summarises it; interpretation stays with a person |
| P05 | Research, Compare, Decide | Primary sources inspected and compared before anything is reported |
| P08 | Fail Visibly | An unreadable source produces a failure notice, not a “no change” report |
| P11 | Keep a Workflow Receipt | Each run records its sources, dates, result and failures |
What it is built on
Three parts of the framework corpus decide how the watch behaves, and each leaves a record the client keeps.
| Framework | In this solution | Client keeps |
|---|---|---|
| PARA | Perception reads official sources read-only; Reasoning compares versions; there is no Action faculty; Adaptation (adding or retiring a source) needs the owner's authority | Agent registry entry |
| Boundary Invariant | “Never report no change when a source failed” is the boundary; summary style is the optimiser | BOE Declaration; failed-source list per run |
| Five-Gate Deployment Model™ and AI Incident Response Protocol (AIRP)™ | A material rule change becomes a trigger at G5 and can reopen validation of the systems it affects (loop-back to G2) | Version ledger per source; trigger register |
Five parts apply to every build and are not repeated here: decision rights, the five gate records, a BOE Declaration per control, a vendor assessment for every vendor, and incident response. How we build sets out all of them.
The evidence it leaves behind
Every run leaves records the client keeps.
- A version ledger for each source
- A failed-source list for every run
- The agent registry entry
- A BOE Declaration for the boundary
- A trigger register
- The five gate records, as for every build
Typical buyer
The typical buyer is a compliance, legal or public affairs team.
Status
Proposed, as of 9 October 2026. A solution becomes Piloting or Released only after a documented pilot, and no result is shown for it before then.
How to start
Most organisations start with the Automation Assessment. A federally regulated financial institution starts with the E-23 Readiness Review, or runs it beside the Assessment; OSFI E-23 on nabeelkhan.com explains the guideline.
Where to go next
Compliance and procurement
Compliance and procurement leads: run the AVRF vendor questionnaire yourself for free, run it with iSystematic, or govern the AI programme through readiness.
Read more →Municipalities
Municipalities: iSystematic starts with a staff AI-use policy or an Automation Assessment, then prepares council packages and resident answers you approve.
Read more →Vendor Intake and AI Diligence
Vendor Intake and AI Diligence runs the AVRF questionnaire on each new AI tool and drafts a gate decision, with OSFI Guideline E-23 in view for FRFIs.
Read more →Knowledge Desk
The Knowledge Desk answers staff questions only from approved, versioned documents, cites the section, and refuses when the source is missing or retired.
Read more →How we build
How iSystematic builds: every solution uses the same deposited frameworks. See what each part decides, what the client keeps, and each specification's DOI.
Read more →Conformance is self-declared; no regulator endorses this work.
Start with the Automation Assessment
Two weeks, a fixed fee shared on a short call, ten candidate tasks scored and three solutions recommended.