# STEWARD Hospital & Clinic Administrator Mission Control — Product Specification

## Product identity

- **Name:** STEWARD — Hospital & Clinic Administrator Mission Control
- **Product ID:** `steward-hospital-clinic-administrator-mission-control`
- **Target version:** `2.0.0`
- **Hermes lane:** `hospital_clinic_administration`
- **Route:** `/hospital-clinic-administrators`
- **Namespace:** `hcadmin_steward.*`
- **Home:** My STEWARD
- **Primary mode:** Private Administrator OS
- **Distribution:** downloadable local full-stack web application in a ZIP, with loopback launchers for macOS, Windows and Linux

## Purpose

STEWARD helps hospital, clinic, service-line, health-system and practice administrators turn fragmented goals, evidence, constraints and decisions into governed missions, owned workflows, reviewable artifacts and repeatable improvement cycles. It supports strategy, access, flow, resources, workforce, quality, compliance preparation, equity, resilience and responsible digital/agent governance while preserving exact human authority and official-system boundaries.

It prepares, compares, rehearses, drafts, tracks and evaluates. It does not become an EHR, command center, HRIS, scheduling system, billing/claims platform, finance ledger, contract or procurement system, incident-reporting system, cybersecurity control plane, legal/compliance/accreditation authority, emergency-management system or autonomous executive.

## STEWARD pillars

1. **S — Set strategy and steward the mission**
2. **T — Transform access, flow and operations**
3. **E — Exercise sound economics and resource stewardship**
4. **W — Strengthen workforce and workplace**
5. **A — Assure quality, compliance, equity and trust**
6. **R — Build resilience, risk intelligence and readiness**
7. **D — Govern digital systems and ethical agents**

The pillars organize 24 SuperPowers, 24 paired workflows and 30 functional templates defined in the canonical domain corpus. Their IDs and titles must remain stable unless a versioned migration explicitly changes them.

## Intended users and settings

The first-run Role and Setting card supports:

- health-system or enterprise administration;
- hospital, facility or service-line administration;
- clinic, ambulatory, practice or multi-site administration;
- independent or small-practice administration;
- academic, public, nonprofit or community settings;
- critical-access, rural or limited-redundancy settings;
- FQHC, look-alike, RHC or safety-net settings;
- Tribal, IHS or sovereign settings;
- transition, turnaround, merger, closure or crisis planning; and
- dual clinical-administrative identities.

The user may select several contextual lanes, but exactly one **active hat** governs each mission or workflow. A clinical license never creates administrative authority; an administrator title never creates clinical authority. Cross-hat work is split into separately owned artifacts joined only by a named human handoff.

## First-run outcome

If no approved derived Discover Packet or Soul result exists, onboarding asks the minimum safe questions rather than inventing answers:

- preferred display name;
- exact administrator title or `Unknown`;
- legal entity/setting/site or `Unknown`;
- current active hat;
- authority source, scope, threshold and expiry or `Unknown`;
- selected role/setting lanes;
- current priorities and desired outcomes;
- values and non-negotiable boundaries;
- strengths, growth areas and current situation (steady state, transition, turnaround, merger, closure, crisis, growth, new role or learning);
- preferred communication, learning and decision style;
- presentation, visual-density and accessibility preferences;
- time/cadence constraints;
- memory consent and retention preference;
- accessibility and visual-density preferences; and
- desired AI support, with all agents still Disabled.
- recommended STEWARD workflows, powers, templates, capabilities, dashboard modules and agents as reviewable candidates only, with tools left empty until real capability discovery.

Show a proposed Mission Profile with field-level provenance and uncertainty. The user may edit, reject, approve, export or delete it. Persist only after approval. Never store raw Soul Quiz answers or duplicate Hermes `SOUL.md`.

On approval, create:

- one personalized My STEWARD home;
- a workspace for each approved role/setting lane;
- separate approved priorities, goals, situation overlays and recommendation candidates for each workspace;
- one editable Starter mission per active lane;
- one first Assess → Define/Diagnose → Plan → Implement → Evaluate cycle;
- a Start Here checklist;
- a Hermes connection checklist;
- initial onboarding progress that is not yet an earned professional badge; and
- controls to Adopt, Clear or Restore Starter content.

Use `implementation/STEWARD-Starter-Workspace-Crosswalk.md` as the deterministic starter catalog for every workspace and situation overlay. Do not invent baselines, performance, organizational facts or authority to make a starter appear personalized.

Starter records must be visually labeled `Starter content`, remain editable, never contain invented authority or organization facts, and remain excluded from operational metrics and achievements until explicitly adopted and subsequently completed with real evidence.

## Information architecture

### Home / My STEWARD

- permanent Private/Institutional mode and data-boundary banner;
- exact identity, entity/site, active hat, authority source and expiry bar;
- global connection, EDENA, CHART and Pause state;
- Core Four launchers: Orient Mandate & Priorities; See Operations & Risk; Align People, Resources & Change; Decide, Escalate & Close;
- an intentionally unused fifth launcher slot;
- Focus Now, capped at seven: Role, Strategy, Access/Flow, People, Quality/Risk, Money/Resource and Human/Agent;
- current priorities, active missions, next actions, upcoming reviews, blockers and recent progress;
- role and agent selectors;
- quick capture and Continue Last Session; and
- connection/setup checklist.

### Mission Workspace and Improvement Loop

Each mission stores its owning workspace, goal, desired outcome, scope, boundaries, active phase, evidence, assumptions, measures, milestones, tasks, owners, dates, decisions, risks, safeguards, reviews, references and activity history. The five stages are stateful and editable. Revising a material earlier-stage field reopens affected downstream reviews and clears stale approval.

The user can create, edit, duplicate, pause, archive, restore and delete missions; begin a new iteration after Evaluate; and import/export permitted records. These operations work offline.

### STEWARD Studios

Expose the 24 powers/workflows and 30 templates from the canonical pack. Every power begins `Available Inactive`. Preview and activation are separate. A one-run activation requires current CHART and EDENA results, a named owner, exact input/output/data/tool/destination boundaries, a receipt, time/cost limit and safe exit. It returns Inactive after review.

### Evidence Center

Support user references, retrieved sources, claim mapping, version/freshness, appraisal/confidence, verification queues and citation export. Clearly distinguish user-supplied facts, retrieved evidence, AI synthesis, user interpretation and required human confirmation. Do not render a citation unless retrieval actually produced and validated it.

### Agent Console

Show the 10 frozen agents, selected agent, routing reason, current permission, objective, prohibited actions, session, tool events, approvals, time/cost limit, Stop, Kill and retirement state. The default is `PERM-P0 Disabled`. A UI selection cannot grant permission.

### Capabilities and Mastery

Build this page from `config/STEWARD-Capability-Mastery-Criteria.v1.json` and `implementation/STEWARD-Capability-and-Badge-Evidence-Model.md`. Track Basic, Intermediate and Advanced development in 17 capability domains, plus the governed global AI Agent Orchestration Master capstone, from saved, reviewable evidence. Display criteria, evidence, date earned, next challenge, governance behaviors, currency and correction/revocation history. Never imply licensure, certification, CE credit, employer authorization or clinical privilege.

### Memory and Data Controls

Display each structured memory item, source, purpose, consent, creation time, expiry and retention. Support Remember, edit, forget, delete and export. Keep temporary sessions separate. Never expose raw Soul, secrets or prohibited data.

### Guide and Setup/Diagnostics

Provide first-run instructions, contextual help, multi-role/active-hat explanations, improvement-loop guidance, Hermes/Soul/Mission Profile distinctions, evidence and badge rules, privacy/safety/accountability boundaries, backup/update/rollback/uninstall and redacted diagnostics.

## Offline functional requirements

Without AI, the user can complete all mission/project/task/note/decision/measure/review CRUD; navigate and filter; use starter content; save/restart/resume; export/import/backup/restore/delete; inspect Guide/governance; and calculate evidence-based progress. AI-only controls show `Setup required` or an honest failure state.

## Connection states

Derive from recent authenticated checks: Connected, Connecting, Setup required, Offline, Authentication failed, Hermes unavailable, Provider unavailable, Limited capabilities and Reconnecting. A timer alone never creates Connected state.

## Success measures

The final release succeeds only if:

- a nondeveloper can install and launch it from the included guide;
- first run creates useful, clearly labeled starter work;
- every visible control works or is disabled with an accurate reason;
- offline records survive refresh and process/computer restart;
- role/workspace boundaries are enforced;
- real AI streams only after backend health/capability success;
- Stop cancels a genuine stream;
- no provider secret reaches the browser or export;
- citations have genuine provenance;
- memory is consent-controlled and deletable;
- EDENA and CHART–ALIGN–ORBIT behavior is consistent across screens and agents;
- tests and the control matrix show no hidden placeholders; and
- the final readiness statement is evidence-based.
