Blueprint · careervector.blueprint-graph/v7

Graph explorer

Twenty composable top-level diagrams plus recursively nested 21×21 semantic layers. Nodes descend; boundary arrows cross to neighbours.

Cell 5.4 · operations · governance · control · evidence

14 · Management accountability

Management closes the loop from policy and observation through controlled change, release, recovery, audit, and accountable review.

  • Change decision to Controlled release: approve + execute
  • Controlled release to Incident + recovery: observe or restore
  • Incident + recovery to Audit + review: account
approve + executeobserve or restoreaccount
processtarget

Change decision

Intent, owner, scope, approval, preconditions, expected evidence, and rollback.

Accountable owner
boundarytarget

Controlled release

Implementation, migration, rollout, compatibility, and provenance follow an owned plan.

Owning product
processtarget

Incident + recovery

Detection, containment, compensation, communication, and restoration remain distinct and visible.

Management + product
storetarget

Audit + review

Receipts, tests, runtime evidence, outcomes, exceptions, and lessons close accountability.

Management
release and recovery evidenceexperience closes accountability
  1. 01 · process · target Change decision

    Intent, owner, scope, approval, preconditions, expected evidence, and rollback.

    Accountable owner
  2. 02 · boundary · target Controlled release

    Implementation, migration, rollout, compatibility, and provenance follow an owned plan.

    Owning product
  3. 03 · process · target Incident + recovery

    Detection, containment, compensation, communication, and restoration remain distinct and visible.

    Management + product
  4. 04 · store · target Audit + review

    Receipts, tests, runtime evidence, outcomes, exceptions, and lessons close accountability.

    Management

Flows

  • Change decision → Controlled release approve + execute
  • Controlled release → Incident + recovery observe or restore
  • Incident + recovery → Audit + review account

Canonical architecture note

Open note ↗

Management Accountability

Outcome

Close the operating loop so every material change or incident has an owner, declared intent, approval, evidence, recovery path, and review rather than ending at a dashboard or deployment.

Lifecycle

decision -> implementation -> release/migration -> observation
         -> success evidence or incident -> recovery/compensation
         -> audit receipt -> accountable review -> policy/architecture update

The owning product executes changes. Management defines ceremony, collects bounded evidence, coordinates communication and recovery, and records accountability. CareerVector workspace and device actions remain link-holder-scoped; JobCache corpus and session actions remain JobCache-owned.

Completion evidence

For a JobCache change and a CareerVector browser/TUI/Tauri change, prove approval, provenance, rollout, compatibility, verification, rollback or compensation, incident communication, immutable receipt, accountable review, and a linked update to policy, architecture, tests, or runbooks.

Source: architecture/modules/management-accountability.md