SP.COMPOSITION.SYS04-v0.1.1 — BUSINESS_CONTROL_STATE TEMPLATE
schema_version: SYS04-state-v0.1.1
state_status: PROPOSED_UNTIL_ADOPTED
state_authority: THIS_ARTIFACT_WHEN_ADOPTED
updated_at: PENDING


BUSINESS IDENTITY / SCOPE
- entity_or_business_scope: PENDING
- management_objective: PENDING
- current_period_or_as_of: PENDING
- currency_units_calendar: PENDING


METRIC CONTRACT
- metric_definitions: PENDING
- metric_owners: PENDING
- comparability_rules: PENDING
- source_data_refs: PENDING
- known_data_gaps: PENDING


CURRENT BUSINESS CONTROL STATE
commercial:
  status: PENDING
  source_refs: []
financial_management:
  status: PENDING
  source_refs: []
cash_receivables:
  status: PENDING
  source_refs: []
operations:
  status: PENDING
  source_refs: []


DERIVED METRICS / VARIANCES
- metric: PENDING
  value: PENDING
  formula: PENDING
  source_refs: []
  data_quality: PENDING
  comparison_basis: PENDING


MANAGEMENT STATE
- adopted_management_decisions: []
- open_items: []
- risks_watch_items: []
- proposed_actions_or_replans: []
- next_review_or_gate: PENDING


HISTORY / SUPERSESSION
- superseded_metric_definitions: []
- superseded_baselines_or_decisions: []
- change_log: []


WRITE OWNERSHIP
- P007: top-level scope, period, metric contract, adopted management state.
- P008: financial_management namespace only.
- P003: commercial namespace only.
- P023: cash_receivables namespace only.
- P035/P038: operations namespace only.
- P004/P046/P051/P052/artifact modules: no direct CURRENT write authority by default; return deltas/views.


STATE RULES
1. One current authority only; no specialist side ledgers.
2. Authority/definition/provenance outrank recency.
3. Missing values remain UNKNOWN/DATA_GAP.
4. Scenario/proposal never overwrites CURRENT.
5. Conflicting metric definitions produce CONFLICT until reconciled.
6. Preserve superseded definitions/decisions; do not erase history.
7. If direct write is unavailable, emit BUSINESS_CONTROL_STATE_UPDATE_REQUIRED instead of claiming a write.
8. Rehydrate this state before longitudinal analysis; provider memory alone is not authori


T23 STATE VERSION / REPORTING BASIS
- state_version: 1
- state_revision_policy: OPTIMISTIC_STATE_VERSION
- last_write_id: NONE
- last_readback_status: NONE
- metric_definition_version: PENDING
- reporting_basis_version: PENDING
- period_id: PENDING
- data_snapshot_id: PENDING
- data_as_of: PENDING
- restatement_state: NONE | RESTATED | PENDING | CONFLICT
- prior_metric_definition_versions: []
- prior_reporting_basis_versions: []


Durable-write precondition:
- expected_state_version: REQUIRED
- observed_state_version_before_write: REQUIRED
- precondition_status: MATCH | WRITE_CONFLICT | NOT_OBSERVABLE
- post_write_state_version/readback: REQUIRED_ON_SUCCESS


A change in metric definition, reporting basis, currency/unit/calendar or restatement must be classified separately from business performance. No period comparison is valid until comparability is established.


Temporal extension bindings, when later configured:
- P072_runtime_state_ref: NONE
- P073_runtime_state_ref: NONE
Monitor state is evidence/runtime only and never replaces BUSINESS_CONTROL_STATE.
ty.