Operational meaning is now enforced.

Purpose: Show whether the operating environment is trustworthy now.

Current state: local-runtime is authoritative for offline workflows; web is a view of cross-device user-facing truth.

Trust boundary: Authority is named per panel; KBM facts require reviewed evidence.

Next action: Open the blocked mission or evidence ref before approving advancement.

Consequence: If unattended, alpha-gate-runtime will record blocked when real operator evidence is missing.

Safe to ignore: Cosmetic preview captures can be ignored unless a capture failure is blocking release evidence.

Purpose: Show dependency, trust propagation, replay implication, and governance boundaries.

Current state: runtime-evolution is authoritative for proposal state; topology is a view of runtime contracts.

Trust boundary: Topology explains authority; it does not promote changes.

Next action: Use trust, replay, synchronization, governance, or distribution overlay before acting.

Consequence: If unattended, operators may approve a proposal without seeing replay or sync implication.

Safe to ignore: Decorative relationships can be ignored; authority and sync boundaries cannot.

Purpose: Govern observe, propose, sandbox, validate, replay, compare, and approve state.

Current state: runtime-evolution is authoritative; proposals remain needs_review until a human approval record exists.

Trust boundary: The workspace cannot mutate production directly.

Next action: Open replay and comparison refs before approve.

Consequence: If unattended, release-runtime must not promote the proposal.

Safe to ignore: Low-confidence proposals can be deferred with a recorded reason.

Purpose: Show release readiness, update eligibility, rollback state, and evidence obligations.

Current state: release-runtime is authoritative for release tags and manifests.

Trust boundary: Auto-update remains disabled unless provider metadata exists.

Next action: Review alpha gate blockers and rollback plan.

Consequence: If unattended, alpha-gate-runtime will refuse promotion.

Safe to ignore: Stable-channel controls can be ignored during internal alpha.

Purpose: Move artifacts through import, parse, review, accept or reject, then KBM promotion.

Current state: KBM is authoritative only for reviewed knowledge facts.

Trust boundary: Unreviewed artifacts remain outside trusted answers.

Next action: Open review for low-confidence or conflicting records.

Consequence: If unattended, production-session-runtime cannot consume the artifact as trusted knowledge.

Safe to ignore: Metadata-only parser limits can be deferred if the artifact is not required for the active session.

Purpose: Prepare audio metadata, lyrics, preview, unlock readiness, and release evidence.

Current state: release-runtime is authoritative for release manifest truth; payment success is not claimed without provider evidence.

Trust boundary: Radio previews are operational surfaces; payment providers remain external authority when configured.

Next action: Keep checkout blocked unless webhook verification exists.

Consequence: If unattended, operators may confuse preview unlock contracts with verified payment readiness.

Safe to ignore: Pro subscriber language can be deferred while payment env vars are absent.

Purpose: Run production sessions, stages, tasks, artifacts, and evidence-backed transitions.

Current state: production-session-runtime is authoritative for per-session state.

Trust boundary: Local offline state is authoritative until reconciliation.

Next action: Record tasks and transitions with evidence refs.

Consequence: If unattended, schedule and KBM context may become stale for the active session.

Safe to ignore: Investor or billing summaries can be ignored during local dry-runs.

Purpose: Show readiness scores, blockers, evidence refs, and false-claim risks.

Current state: governance is authoritative for readiness claims.

Trust boundary: Completion does not promote releases; it informs approval.

Next action: Resolve blocking findings before increasing scores.

Consequence: If unattended, readiness may drift from evidence and create false operational claims.

Safe to ignore: Production-proven labels can be ignored until real field history exists.