# STEWARD Starter Workspace Crosswalk

**Contract ID:** `NAIO-STEWARD-STARTER-CATALOG-1.0.0`  
**Purpose:** create a useful first workspace without inventing identity, organization facts, authority, baseline performance or approval.

Every starter record is local, editable and visibly labeled `Starter content — not adopted`. It uses questions, `Unknown` values and safe completion measures. It is excluded from operational analytics and achievements until the user deliberately adopts it, replaces synthetic/unknown content with permitted real evidence, completes and evaluates it, and obtains any required human review.

## Common starter structure

Each approved role workspace receives:

- a Start Here checklist;
- a Hermes connection checklist that remains optional for offline work;
- one mission with a stable seed key and generated UUID;
- an Assess-stage prompt set and empty evidence slots;
- proposed outcome, process and safeguard measures that describe **review completeness**, not organization performance;
- Adopt, Clear and Restore controls;
- `source=starter_catalog`, catalog version, role workspace, situation overlay and `demo=false, starter=true` metadata; and
- no active power, agent, tool, connector, schedule or external action.

Default EDENA is `Unclassified` until the user supplies purpose, data, destination and action context. The starter may display a Yellow **recommendation candidate**, but it must run the real classifier before any stage promotion or AI request. Unknown authority keeps consequential paths blocked.

## Workspace starters

| Workspace type | Starter mission | Candidate assets | Suggested review-completeness measures | Hard boundary |
|---|---|---|---|---|
| `enterprise` | Define one ninety-day mission and decision-right map | `WF-01` / `PWR-01` / `TPL-05` | mission owner named; authority source/expiry reviewed; no more than three outcomes; next review dated | No board/executive authority, enterprise commitment or official strategy claim |
| `hospital_facility` | Map one handoff or flow question for a reversible test | `WF-06` / `PWR-06` / `TPL-10` | context defined; operational and clinical owners named; aggregate source approved; stop/rollback rule present | No patient row, throughput/safe-capacity conclusion, schedule or care-priority action |
| `service_line` | Build one access, demand and capacity question brief | `WF-05` / `PWR-05` / `TPL-09` | numerator/denominator/exclusions drafted; measure owners named; equity and balancing questions present | No individual access, eligibility, triage or utilization decision |
| `clinic_practice` | Explore one fictional or user-approved aggregate access constraint | `WF-05` / `PWR-05` / `TPL-09` | service promise marked approved/proposed/unknown; aggregate data path reviewed; one reversible-test candidate | No patient list, appointment action or claim about actual performance without evidence |
| `multi_site_network` | Compare role, decision and handoff boundaries across proposed sites | `WF-08` / `PWR-08` / `TPL-12` | entity/site scope explicit; local versus shared decisions separated; dependencies and unresolved conflicts listed | No consolidation, staffing, closure or standardization decision |
| `independent_small_practice` | Create a protected ninety-day operating compass | `WF-01` / `PWR-01` / `TPL-05` | three priorities or fewer; owner and resource assumptions visible; protected-life boundary and stop rule present | No financial, clinical, employment, contract or regulatory conclusion |
| `academic_public_nonprofit_community` | Prepare an equity, accessibility and community-impact question set | `WF-18` / `PWR-18` / `TPL-23` | affected groups not presumed; engagement owner/route named; accessibility/language questions and evidence gaps visible | No claim to represent a community, determine equity or substitute AI for engagement |
| `critical_access_rural` | Rehearse one synthetic continuity scenario | `WF-19` / `PWR-19` / `TPL-24` | scenario labeled synthetic; essential-function owner/official plan named or Unknown; stop and after-action route present | No real emergency command, activation, staffing adequacy or downtime instruction |
| `fqhc_rhc_safety_net` | Frame one access-and-equity learning question using approved aggregates | `WF-05` / `PWR-05` / `TPL-09` | service/population terms reviewed; small-cell/privacy rule identified; measure limits and human owners visible | No eligibility, benefit, referral, triage, payer or individual access decision |
| `tribal_ihs_sovereign` | Define a sovereignty-respecting community review route before analysis | `WF-18` / `PWR-18` / `TPL-23` | governing authority and data/community review route named or Unknown; prohibited assumptions listed; no analysis before gate | No presumption of authority, ownership, applicability or permission; sovereign policy controls |
| `administrator_learner_consultant` | Build a leadership learning charter and one bounded AI-governance practice goal | `WF-15` / `PWR-15` / `TPL-20`; optional preview of `WF-23` / `PWR-23` / `TPL-28` | learning goal, time boundary, evidence type and reviewer route proposed; protected-life constraint present | Learning/consulting identity grants no organizational, clinical or agent authority |
| `shared_administrator` | Clarify one decision, active hat and cross-role handoff | `WF-02` / `PWR-02` / `TPL-06` | one decision/non-decision boundary; active hat; source/assumptions; named sender/receiver and acknowledgment route | No cross-population join, transferred authority or official decision record |

If the user selects several workspace types, create one isolated starter per approved workspace. Do not duplicate a shared goal automatically. Show a proposed shared relationship and require approval before linking records.

## Situation overlays

An overlay adjusts questions; it never rewrites the base role, changes authority or activates an asset.

| Situation | Add these prompts | Candidate assets | Additional boundary |
|---|---|---|---|
| `steady_state` | What should be sustained, measured, stopped or learned? | Base workspace asset | No assumption that current state is acceptable or known |
| `transition` or `new_role` | What mandate, predecessor decision, stakeholder route, handoff and expiry must be verified? | `WF-01`, `WF-15` | No inferred succession or delegated right |
| `turnaround` | Which fact, cash/resource assumption, capacity constraint and harm signal needs verified human review first? | `WF-02`, `WF-03`, `WF-06` | No solvency, staffing, closure or safety conclusion |
| `merger_integration` | Which entity, policy, data, decision and workforce boundaries must remain distinct? | `WF-03`, `WF-08`, `WF-14` | No combined dataset or operating-model decision without authorization |
| `closure_consolidation` | Which services/people may be affected, which official process owns the decision and which continuity safeguards require review? | `WF-02`, `WF-14`, `WF-19` | No closure recommendation, public message or transition execution |
| `crisis_response` | Is this a real event? If yes, stop and use the official route. If synthetic, define exercise scope and controller. | `WF-19` only for a synthetic exercise | Real incidents and emergencies stay outside STEWARD execution |
| `growth_expansion` | What demand, capacity, workforce, finance, equity and exit assumptions must be tested? | `WF-03`, `WF-08`, `WF-09` | No capital, hiring, site or service commitment |
| `learning_certification` | What capability criterion, authentic evidence and qualified reviewer are appropriate? | `WF-15`, optional `WF-23` | No badge may imply certification or replace a formal program |
| `other_reviewed` | Ask the user to name the situation, affected people, risk and official owner | No candidate until reviewed | Unknown context keeps recommendations and consequential paths blocked |

## Safe starter mission fields

Hermes may populate only:

- user-approved display labels and workspace selection;
- the canonical starter title/questions above;
- `Unknown` for missing authority, entity, baseline, official source, owner or destination;
- the candidate asset IDs above as recommendations only;
- completion measures about required definitions, reviews and safeguards; and
- source/catalog/version/provenance metadata.

Hermes must not seed a performance number, staffing level, budget, service promise, policy requirement, legal/regulatory applicability, community preference, role competence, authorization, clinical fact, organizational result or connector configuration.

## Adopt, clear and restore

### Adopt

Preview exact records and analytics effects. Adoption changes `starter=true` to `starter_origin=true, adopted_at=<time>` and preserves seed/catalog provenance. It does not make a claim true or earn a badge. The user must replace synthetic/Unknown values with permitted evidence and complete the work normally.

### Clear

Remove only unadopted records from the selected workspace after confirmation. Do not delete user-created or adopted records, profile fields, evidence or other workspaces. Record counts and stable seed keys without retaining removed content.

### Restore

Restore only missing current-version starter records by stable seed key. Never overwrite, duplicate, unarchive, reset or relabel an adopted/user-created record. Preview migrations between starter-catalog versions.

## Required tests

For all 12 workspace types and every situation overlay, test deterministic seed output, one Primary workspace, generated unique IDs, no invented authority/facts, canonical asset resolution, Unclassified default, no activation, analytics/badge exclusion, Adopt, scoped Clear, idempotent Restore, multi-workspace isolation, version migration, correction and complete deletion.
