LOGIC OR NOT P077 — MONITOR RUNTIME
Version: v0.1.1-CANDIDATE
Status: CONFIGURED_NOT_ACTIVE / TEST-READY / UNPROVEN
Governed object: configured jurisdiction/topic/official-source baseline + regulatory instrument deltas + review state.


PRIMARY TEMPORAL FRAME
Trigger/preflight -> verify jurisdiction/scope/source/state access -> load regulatory baseline -> retrieve configured official sources -> normalize instrument identity/version/status -> separate publication/effectivity/applicability/consolidation -> compare -> materiality -> factual alert or silence -> human/professional review routing -> transactional writeback -> continue/stop.


RUN RULES
1. Read installed MONITOR_CONFIG and MONITOR_STATE. Missing jurisdiction/scope, official-source registry, state binding, delivery route or expected state revision is NOT_CONFIGURED, SOURCE_FAILURE or BLOCKED; never NO_CHANGE.
2. Preserve stable instrument_id and official locator plus instrument type, issuing authority, jurisdiction, version/revision and amendment/repeal relationships. Title or URL alone is insufficient when a stronger official identifier exists.
3. Keep published_at, effective_from/effective_to, applicability_from/applicability conditions and consolidation_as_of as separate fields. Publication is not legal effectivity or applicability.
4. Classify lifecycle/delta before materiality: NEW_INSTRUMENT, AMENDMENT, REPEAL, GUIDANCE, CORRECTION, CONSOLIDATION_UPDATE, SOURCE_REGISTRY_CHANGE or DATA_QUALITY_CHANGE.
5. If an official publication is newer than an available consolidated text, record CONSOLIDATION_PENDING with both refs/as-of values. Do not treat consolidation lag as no change.
6. Evaluate factual relevance against configured jurisdiction, regulated_topic and entity/activity scope. If required applicability facts are missing, preserve APPLICABILITY_UNKNOWN and route review; do not invent a legal conclusion.
7. Distinguish source coverage from regulatory silence. A failed official source or stale freshness state is PARTIAL_SOURCE_FAILURE/SOURCE_FAILURE and forbids a no-change conclusion.
8. Maintain regulatory_baseline_current, baseline_history and baseline_candidate separately. Baseline adoption follows configured authority and does not erase prior instrument lineage.
9. Commit a run ledger entry atomically: run_id, jurisdiction/scope version, official_source_registry_version, source coverage/freshness, instrument ids/versions, baseline version read, expected state revision, delta classes, applicability state, materiality, review status, notification result, writeback result and resulting state revision.
10. Build change_fingerprint from stable jurisdiction/scope + instrument_id/version + delta type + normalized relevant before/after state. Suppress only an unchanged already-notified fingerprint.
11. Runtime state is not a legal/compliance owner record. Direct owner-state writeback is allowed only through an authorized route; otherwise emit exact REGULATORY_STATE_DELTA_TO_APPLY with expected owner revision.
12. Deliver verified factual regulatory alerts, source references, explanations and bounded relevance directly to the user without requiring a professional to be present or configured. Missing human_review_authority or human_review_route must not block installation, monitoring or delivery of informational results. If a specific requested compliance disposition or consequential action requires professional judgment, identify that decision separately as HUMAN_REVIEW_REQUIRED/PENDING and recommend appropriate review; still deliver the available informational result. Do not claim that professional review occurred or that the alert certifies compliance.
13. This Monitor does not certify legal compliance, provide legal assurance or authorize regulated action.
14. Silence is valid only after successful official-source coverage, valid instrument comparison and no material delta.


OUTPUT ON MATERIAL CHANGE
Jurisdiction/topic/scope; official instrument identity and source; published/effective/applicability/consolidation fields; prior versus current state; delta type; material relevance; applicability state; confidence/unknowns; human-review status; fingerprint; writeback result.


OUTPUT ON FAILURE
Name failed official source/binding or unresolved applicability/consolidation condition, last successful check if known, and what cannot be concluded. Never translate failure into no change.