LOGIC OR NOT P079 — MONITOR RUNTIME
Version: v0.1.1-CANDIDATE
Status: CONFIGURED_NOT_ACTIVE / TEST-READY / UNPROVEN
Governed object: provider/product/capability knowledge baseline + rollout/access envelope + tracked-use-case impact.


PRIMARY TEMPORAL FRAME
Trigger/preflight -> verify host/source/state access -> load provider/capability/use-case baseline -> acquire current provider evidence -> normalize capability identity/lifecycle/availability -> compute knowledge delta -> map to tracked dependency/use-case impact -> materiality -> alert or silence -> transactional knowledge/runtime writeback -> continue/stop.


RUN RULES
1. Read MONITOR_CONFIG and MONITOR_STATE. Missing trigger, provider/capability registry, source route, state binding, delivery route or expected revision is NOT_CONFIGURED / SOURCE_FAILURE / BLOCKED; never NO_CHANGE.
2. Resolve stable provider_product_id / model_or_tool_id / capability_id / edition_or_surface_id before comparison. Marketing names alone must not merge or split capabilities without evidence.
3. Preserve source_id, source_revision/version, publication/effective dates and source role. Prefer official product docs/changelogs/pricing/status/support evidence for provider facts when configured; secondary evidence remains attributed and cannot silently override a stronger authority.
4. Separate lifecycle states: ANNOUNCED, DOCUMENTED, ROLLING_OUT, GENERALLY_AVAILABLE, LIMITED_PREVIEW, DEPRECATED, RETIRED, UNKNOWN. An announcement does not prove general availability or access to this user/workspace.
5. Maintain an access envelope distinct from ecosystem capability: account/plan, workspace/admin policy, region, client/device, model/tool availability, connector/app authorization and other configured prerequisites. Classify USER_ACCESS_CONFIRMED / USER_ACCESS_UNAVAILABLE / USER_ACCESS_UNKNOWN separately from provider availability.
6. For price/limit changes, preserve currency, billing unit/dimension, plan/edition, region, effective date and source revision when material. Do not compare price/limits across incompatible units or plans.
7. Version the tracked_use_cases and dependency map. A provider change is material only when it affects a tracked workflow/configuration or a configured watch criterion; generic AI-news noise is outside scope.
8. Classify delta before materiality: CAPABILITY_NEW, CAPABILITY_UPDATED, ROLLOUT_STATUS_CHANGE, ACCESS_ENVELOPE_CHANGE, DEPRECATION_OR_RETIREMENT, PRICE_OR_LIMIT_CHANGE, SOURCE_CONFLICT, SOURCE_COVERAGE_CHANGE, DEPENDENCY_DEFINITION_CHANGE or DATA_QUALITY_CHANGE.
9. If current sources conflict, preserve the conflict with source authority/freshness; do not choose the newest source by recency alone.
10. Maintain baseline_current, baseline_history and baseline_candidate separately. Adoption requires configured authority.
11. Commit a run ledger atomically: run_id, provider_capability_set_version, tracked_use_case_version, dependency_map_version, host_capability_envelope_version, source coverage/freshness, provider revisions, baseline version read, expected state revision, delta classes, impact map, materiality, notification, owner/runtime writeback and resulting revision.
12. Build change_fingerprint from stable provider/capability/surface identity, lifecycle/access state and normalized material use-case impact. Suppress only an unchanged already-notified fingerprint.
13. Runtime state is not the authoritative reusable knowledge asset/configuration state. Direct owner writeback requires an authorized route; otherwise emit KNOWLEDGE_STATE_DELTA_TO_APPLY with expected owner revision.
14. Do not automatically switch models, tools, providers, plans, connectors or configurations. Adoption/change remains HUMAN_OR_SEPARATELY_AUTHORIZED_SYSTEM.
15. Silence is valid only after required source coverage/freshness and valid comparability show no material tracked-use-case impact. Source conflict/failure or unknown access needed for the conclusion forbids no-change.


OUTPUT ON MATERIAL CHANGE
Provider/product/capability identity; lifecycle/availability/access state; source/revision; prior/current state; affected tracked use cases/dependencies; material impact; price/limit basis if relevant; confidence/conflicts/unknowns; action/review if supported; fingerprint; writeback result.


OUTPUT ON FAILURE
Name failed source/host/access/comparability condition, last successful run if known, and what cannot be concluded. Never translate failure into no change.