# Phase 10.6.6 — Executive Review Governance, Ownership & Follow-up Management

## Purpose

Phase 10.6.6 turns each Executive Action into an accountable management item with durable ownership and follow-up controls that survive operational-day rollover.

## Governance fields

- Accountable owner
- Assigned to
- Due date
- Follow-up date
- Escalation level: none / watch / high / critical
- Resolution status: active / resolved
- Resolution note (required when resolved)
- Resolved by / resolved at
- Update count and immutable audit history

## Oracle storage

Current durable state:

- `DASH_EXEC_ACTION_GOV`

Immutable governance audit history:

- `DASH_EXEC_ACTION_GOV_AUDIT`
- sequence: `DASH_EXEC_ACT_GOV_AUD_S`

All Oracle identifiers introduced by this phase are 30 characters or fewer.

Run once:

`database/executive_action_governance.sql`

Then verify:

`public/executive-action-governance-storage-check.php?hospital=njch`

## Management behavior

The system derives these accountability states automatically:

- unassigned
- assigned
- due soon
- follow-up due
- overdue
- escalated
- resolved

The Governance Dashboard shows:

- active and resolved actions
- overdue actions
- follow-up due items
- unassigned actions
- escalated actions
- owner workload
- accountability queue
- current action governance state
- recent governance audit history

## Production purity

Automated governance QA actors are excluded from the management recent-activity feed by default. Their immutable audit rows remain stored and readable for technical evidence.

Optional extra QA actor patterns:

`EXEC_ACTION_GOVERNANCE_QA_ACTORS=robot_*,nightly_qa`

## QA

Read-only QA:

`public/executive-action-governance-qa.php?hospital=njch`

Optional controlled write proof:

1. Add to `.env`:
   `EXEC_ACTION_GOVERNANCE_QA_TOKEN=YOUR_PRIVATE_TOKEN`
2. Open:
   `public/executive-action-governance-qa.php?hospital=njch&write_test=1&token=YOUR_PRIVATE_TOKEN`

The controlled proof saves a test governance state, verifies it, restores the original values, and keeps the two audit rows as evidence.

PowerShell evidence tool:

`powershell -ExecutionPolicy Bypass -File tools\E22_H1066_Governance_Ownership_Followup_QA.ps1 -BaseUrl http://localhost -Hospital njch`

With write proof:

`powershell -ExecutionPolicy Bypass -File tools\E22_H1066_Governance_Ownership_Followup_QA.ps1 -BaseUrl http://localhost -Hospital njch -WriteTest -Token "YOUR_PRIVATE_TOKEN"`
