LOGIC OR NOT — Control financiero periódico
Monitor Runtime — v0.1.1
Canonical Product Key: SP-GEN:P073
Governance Class: GOV-TEMPORAL
Modifiers: PERSISTENT_STATE | DATA_DEPENDENT


PURPOSE
Ejecutar recurrentemente el método gerencial AGT.0001 / Business Health sobre fuentes financieras accesibles, preservando definiciones, período/base, provenance de cálculos, restatements y separación entre runtime temporal y analytical finance state.


BOUNDARY
AGT.0001 / Business Health own managerial-finance definitions, classifications, derived metrics and analytical state. P073 owns recurrence, preflight, source coverage, run ledger, materiality/silence/delivery and runtime state. P073 is managerial/non-statutory and cannot imply accounting/tax/audit certification.


RUN TRANSACTION
1. Load MONITOR_CONFIG + MONITOR_STATE.
2. Capture config_revision + expected_runtime_state_revision.
3. Read configured finance analytical state and capture analytical_state_revision + metric_definition_version + classification_version + period_set_version.
4. Verify trigger/delivery/source bindings.
5. Acquire source snapshots with source_ref, source_revision/as_of and coverage status.
6. Resolve reporting basis: entity_scope, currency, period, close status, management basis, tax/gross-net treatment and sign convention where material.
7. Classify each period/source as COMPLETE | PARTIAL | MISSING | PROVISIONAL | CLOSED | RESTATED.
8. Compute only metrics supported by the configured analytical contract; preserve formula, source periods, units, currency and provenance.
9. Test comparability before calculating variance.
10. Separate BUSINESS_MOVEMENT from RESTATEMENT_EFFECT / DEFINITION_CHANGE / CLASSIFICATION_CHANGE.
11. Classify material exceptions and supported drivers.
12. Compute finance_delta_fingerprint.
13. Alert/silence/failure.
14. Update monitor runtime state transactionally.
15. If analytical finance state should change, emit FINANCE_STATE_DELTA or use explicit owner route with expected analytical_state_revision.


RUN STATUS
SUCCESS_NO_MATERIAL_CHANGE
SUCCESS_MATERIAL_CHANGE
PARTIAL_SOURCE_FAILURE
SOURCE_FAILURE
INCOMPLETE_PERIOD
COMPARABILITY_FAILURE
RESTATEMENT_RECONCILIATION_REQUIRED
ANALYTICAL_STATE_STALE
NOT_CONFIGURED
BLOCKED
RUNTIME_WRITE_CONFLICT


PERIOD / BASIS INTEGRITY
Missing or provisional values are not zero.
A restated prior period preserves the pre-restatement snapshot and restatement_ref.
Variance must state whether it uses original or restated comparator.
A basis/classification/currency/tax-treatment change must be versioned or surfaced; never treat definition drift as business movement.


CALCULATION PROVENANCE
Every material derived metric retains metric_id, formula/version, input refs, periods, units/currency and rounding/basis notes.
A calculation tool is execution aid, not authority.
Unsupported precision is forbidden.


MATERIALITY
Materiality applies to comparable managerial-finance changes or material deterioration in data quality/completeness.
Possible domains include cash, margin, cost, working capital, receivables, budget variance and other configured management metrics.


SILENCE
Only after required source coverage, period completeness policy and comparability policy allow a valid SUCCESS_NO_MATERIAL_CHANGE.


WRITEBACK
Runtime-state write uses optimistic revision control.
Analytical finance state update requires exact owner revision/authority.
Without write access return FINANCE_STATE_DELTA with exact changes/readback requirement.


STATUTORY BOUNDARY
Output is managerial analysis only. Do not present as statutory accounting, tax determination, audit/assurance or certification. Route those needs separately.


OUTPUT
run_id; analytical state/definition/classification/period versions; source coverage; reporting basis; comparable metrics; business vs restatement/definition effects; material exceptions; fingerprint; limits; runtime writeback; finance-state delta/result.