# STEWARD — Hospital & Clinic Administrator Complete AI OS

## Install one file only

This distribution contains the standalone STEWARD setup for hospital and clinic administrators. Give Hermes the complete file:

`Hospital-and-Clinic-Administrator-Complete-AI-OS-with-STEWARD-SuperPowers-Hermes-Program.md`

Do not split, reorder, merge, or install the source components one at a time. The source pack is included for inspection and audit; it is not a second installation path.

> **Installation may take a while.** This is a substantial setup and may require several Hermes turns. Nothing continues in the background. Save the S0, S1, and S2 receipts, remain in the installation conversation, and wait for the final **STEWARD Activation Report** before treating setup as complete.

## Safe setup instruction

> Install STEWARD from this complete program in a new or verified-isolated `hospital_clinic_administration` lane. Begin with read-only preflight, show one combined Activation Card, and wait for my exact approval. Keep my exact title, organization, site, service, active administrative or clinical hat, delegated decision rights, thresholds, and named human owners separate; infer no authority. Default to Private Administrator OS, where only my minimum professional identity and authority metadata may be stored. Do not accept PHI, patient-level data, other-person employee/applicant/practitioner data, sensitive operator employment records, personnel files, real incident or event narratives, claim-level data, vendor-confidential, contract-confidential, security-sensitive, or nonpublic financial data. Keep conversation/model memory session-only, connectors and actions Off, all 24 powers Available Inactive, and all 10 agents PERM-P0 Disabled. Create S0, S1, and S2 receipts; execute the 160 runtime release criteria with explicit status and evidence; stop on every failed, blocked, or unsupported critical criterion; and finish only with the STEWARD Activation Report.

## What installs

- One isolated lane: `hospital_clinic_administration`
- One route: `/hospital-clinic-administrators`
- One namespace: `hcadmin_steward.*`
- One accessible home: **My STEWARD**
- Core Four: Orient Mandate & Priorities; See Operations & Risk; Align People, Resources & Change; Decide, Escalate & Close
- CHART for authority, data, risk, and action boundaries
- ALIGN for human-owned organizational orchestration
- ORBIT and PERM-P0–PERM-P5 for governed software agents
- 24 optional powers, all **Available Inactive**
- 24 runnable workflows
- 30 functional cards and templates
- 18 typed administrator-owned schemas
- 10 suggested agents, all **PERM-P0 Disabled**
- 160 evidence-bearing runtime release criteria, specified but not pre-passed
- Pause All, Safe Reset, kill, rollback, purge, power removal, overlay removal, and full uninstall

## What STEWARD does—and does not do

STEWARD helps administrators prepare strategy, governance, access, flow, operating-model, financial-scenario, workforce, quality, accreditation-readiness, policy, equity, resilience, cybersecurity, and AI-governance work. It organizes evidence, assumptions, questions, owners, decision packets, bounded drafts, and human follow-through.

It is not an EHR, patient-flow command system, HRIS, credentialing system, finance ledger, billing or claims system, contract or procurement system, legal/compliance authority, incident-reporting system, cybersecurity control plane, or board record. A polished draft is never an official record.

STEWARD must not autonomously make or execute clinical or device decisions; patient contact; staffing or scheduling assignments; hiring, evaluation, discipline, termination, compensation, credentialing, or privileging decisions; payments, pricing, coding, billing, claims, or ledger entries; legal, compliance, reportability, accreditation, or audit conclusions; vendor selection, contract signature, purchase order, or procurement commitments; security access or production-configuration changes; external messages; or public releases.

## Exact authority matters

An administrator title is not universal permission. During setup, provide the exact organization, ownership or governance context, site, service, job title, active hat, delegated decision rights, approval and dollar thresholds, allowed data, official systems, and named clinical, HR, finance, compliance, legal, privacy, security, quality, research, procurement, and executive owners.

Unknown, stale, conflicting, or cross-hat authority becomes a question and human escalation. Installing STEWARD never creates authority, platform approval, compliance, accreditation, legal sufficiency, or permission to use sensitive information.

## Private starting state

Private defaults are explicit: no PHI, no patient-level data, no personnel files, no claim-level data, no real event or incident narratives, and no confidential contract, vendor, security, or nonpublic financial content.

Private Administrator OS may store only the operator's minimum professional identity and authority metadata required for setup: exact title, active hat, entity/site, written authority source, decision boundary, named human routes, and expiry. Public information and unmistakably synthetic examples may be used for bounded drafts, but they do not expand the private identity store. Do not enter other-person employee, applicant, practitioner, or performance information; sensitive records about the operator's own employment; or a real patient, incident, event, vendor, contract, security, claim, or nonpublic financial story—even if someone believes it is deidentified.

Institutional use requires separate approval for the exact organization, platform, vendor/model, purpose, data, partition, reads, writes, logging, retention, deletion, security, incident response, human owners, and manual fallback. The base Complete Edition remains aggregate- and process-level even in an institution-approved workspace. Patient-, encounter-, event-, claim-, employee-, applicant-, and individual-practitioner-level rows or narratives require a separate purpose-built governed product, schemas, tests, release ledger, and human approval. Personal whole-life information requires a personally controlled isolated store and stays disabled in an institution-managed context; hiding a panel is not separation.

## Runtime release criteria are not pre-passed

The package specifies 160 evidence-bearing runtime release criteria. Foundation installation executes 40 criteria: `RA-A01`–`RA-D08` plus `RA-I01`–`RA-I08`. After S1, the overlay binds and verifies the 18 foundation-owned schemas—it never recreates, overwrites, or silently migrates them—then executes the remaining 120 overlay and integration criteria.

Every criterion must be recorded as `specified`, `executed`, `passed`, `failed`, `blocked`, or `unsupported`. `Specified` is not executed, and `unsupported` is not passed. Every failed, blocked, or unsupported critical criterion blocks activation. Static artifact validation can prove files, IDs, links, embedding, checksums, and archive integrity; it cannot prove runtime isolation, permissions, action denial, accessibility of the installed dashboard, pause, kill, rollback, purge, or uninstall. Those require the target platform adapter, versioned fixtures, state probes, evidence, and an independent reviewer.

## Package map

| Item | Purpose |
|---|---|
| `Hospital-and-Clinic-Administrator-Complete-AI-OS-with-STEWARD-SuperPowers-Hermes-Program.md` | The only file to give Hermes for installation |
| `Hospital-and-Clinic-Administrator-Complete-AI-OS-with-STEWARD-SuperPowers-Setup-Guide.docx` | Polished benefits, setup, safety, governance, and recovery guide |
| `Hospital-and-Clinic-Administrator-Complete-AI-OS-with-STEWARD-SuperPowers-Setup-Guide.md` | Accessible Markdown guide and fallback |
| `Hospital-and-Clinic-Administrator-STEWARD-SuperPowers-Pack-v1.0/` | The 17 embedded source components plus source-pack README for audit |
| `SHA256SUMS.txt` | SHA-256 integrity values for every packaged file except the checksum file itself |

The package contains exactly 23 files. `SHA256SUMS.txt` contains exactly 22 entries.

## First safe use

Wait for the final Activation Report. Then use only the operator's minimum professional identity and authority metadata, public sources, approved aggregate/process information in the correct institutional partition, or an explicitly synthetic example to create one low-risk artifact with a named human owner and expiry. Good first choices include a mission-and-priority card, KPI definition and source ledger, synthetic decision brief, aggregate process map, meeting close-loop card, public-source policy question, leader-capacity plan in a personally controlled store, or preview of a source-and-claim agent that remains PERM-P0 Disabled.

Activating no powers is an acceptable outcome. Preview one power at a time. Do not connect, persist, share, send, schedule, publish, release, write an official system, or run an agent without a separate exact approval.

## If setup is interrupted

Use the saved S0, S1, or S2 receipt and the exact resume command in the complete installer. Revalidate owner, lane isolation, active hat, delegated authority, data partition, human decision routes, sources, permissions, CHART, ALIGN, ORBIT, My STEWARD, kill switch, and recovery controls. Do not repeat completed mutations or assume missing state.

## Verify this package

Compare every packaged file with `SHA256SUMS.txt` using a SHA-256 utility. The release tooling also verifies checksum syntax and coverage, exact source-pack inventory, packaged/original parity, ZIP member inventory, in-ZIP checksums, and ZIP CRC integrity.

STEWARD is a working product name for an independent organizational concept. It is not endorsed, certified, accredited, or approved by any cited source organization. Current law, regulation, contracts, payer requirements, ownership and governing documents, medical-staff bylaws, labor agreements, local policy, official systems, and decisions by authorized humans remain controlling. No operational, financial, workforce, compliance, accreditation, security, patient, or community outcome is guaranteed.
