# STEWARD Cards & Templates

These are copyable working forms, not approvals or official records. Every template shows owner; exact role/active hat; entity/site/service; context and partition; allowed/prohibited data; source/version; fact versus interpretation; human decision owner; status; created/updated/expiry; retention; correction; export and deletion. Run CHART; add ALIGN or ORBIT when relevant. Unknown consequential information is labeled and never invented.

## Template 1 — Administrator True North & Protected-Life Promise

**Stable ID:** `TPL-01`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Personally controlled store verified:** `<enter or mark Unknown>`
- **Leadership identity beyond title:** `<enter or mark Unknown>`
- **One-sentence mission:** `<enter or mark Unknown>`
- **Protected-life promise:** `<enter or mark Unknown>`
- **Non-negotiable ethical boundary:** `<enter or mark Unknown>`
- **Ninety-day direction:** `<enter or mark Unknown>`
- **Minimum Mode trigger:** `<enter or mark Unknown>`
- **Review and delete date:** `<enter or mark Unknown>`

**Worked synthetic example:** Fictional administrator Jordan writes: ‘Protect reliable access while keeping one evening each week free for family,’ then sets a 90-day review.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Owner accepts, revises or deletes; employer access and analytics stay Off. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 2 — Administrator Identity, Entity, Site, Hat & Delegated-Authority Card

**Stable ID:** `TPL-02`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Exact job title:** `<enter or mark Unknown>`
- **Active administrative or clinical hat:** `<enter or mark Unknown>`
- **Legal entity and ownership context:** `<enter or mark Unknown>`
- **Operating level and site/network:** `<enter or mark Unknown>`
- **Jurisdiction:** `<enter or mark Unknown>`
- **Delegated authority and source:** `<enter or mark Unknown>`
- **Decision rights and exclusions:** `<enter or mark Unknown>`
- **Committee/board roles:** `<enter or mark Unknown>`
- **Escalation routes and expiry:** `<enter or mark Unknown>`

**Worked synthetic example:** Jordan records the exact title ‘Clinic Operations Administrator,’ one site, a $0 purchasing authority for this exercise, and an escalation to the fictional COO.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Title, credential, committee role and delegated authority stay separate; unknowns block consequential use. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 3 — Source, Requirement, Policy & Freshness Ledger

**Stable ID:** `TPL-03`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Publisher and exact title:** `<enter or mark Unknown>`
- **Canonical URL or approved reference:** `<enter or mark Unknown>`
- **Publication/effective date:** `<enter or mark Unknown>`
- **Version and status:** `<enter or mark Unknown>`
- **Applicability owner:** `<enter or mark Unknown>`
- **Requirement or claim:** `<enter or mark Unknown>`
- **Local policy/override:** `<enter or mark Unknown>`
- **Conflict and exclusions:** `<enter or mark Unknown>`
- **Retrieved/review/expiry dates:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional CMS source is labeled ‘example only’; its applicability remains Unknown until the compliance owner verifies the real current source.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Qualified human verifies applicability; proposed, retired, superseded and conflicting sources remain labeled. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 4 — CHART Authority and Action Gate Receipt

**Stable ID:** `TPL-04`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **C — context, constituency and consequence:** `<enter or mark Unknown>`
- **H — human authority, active hat and accountable owner:** `<enter or mark Unknown>`
- **A — authorization, access, agreements and approved action:** `<enter or mark Unknown>`
- **R — regulation, risk, resources and official records:** `<enter or mark Unknown>`
- **T — trace, test, transition, expiry and termination:** `<enter or mark Unknown>`
- **Gate: pass, question, block or emergency stop and official route:** `<enter or mark Unknown>`
- **Named-human decision and timestamp:** `<enter or mark Unknown>`
- **Official reconciliation receipt:** `<enter or mark Unknown>`

**Worked synthetic example:** A synthetic clinic-dashboard request fails CHART because the approved data source and named release owner are missing.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** All five elements are current and consistent or the action blocks and routes to a human. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 5 — Strategy-on-a-Page & Ninety-Day Alignment Card

**Stable ID:** `TPL-05`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Approved mission and mandate:** `<enter or mark Unknown>`
- **Community and ownership context:** `<enter or mark Unknown>`
- **Three strategic outcomes:** `<enter or mark Unknown>`
- **Measures and owners:** `<enter or mark Unknown>`
- **Non-negotiables:** `<enter or mark Unknown>`
- **Assumptions and constraints:** `<enter or mark Unknown>`
- **Stakeholder commitments:** `<enter or mark Unknown>`
- **Ninety-day choices:** `<enter or mark Unknown>`
- **Review body and date:** `<enter or mark Unknown>`

**Worked synthetic example:** Northstar Community Clinic, a fictional organization, connects three outcomes to named owners and labels two board-direction questions unresolved.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Board/owner/executive sponsor approves any material direction. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 6 — ALIGN Executive Decision, Options & Assumptions Brief

**Stable ID:** `TPL-06`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **A — aim, decision boundary and affected people:** `<enter or mark Unknown>`
- **L — leadership and decision accountability:** `<enter or mark Unknown>`
- **I — inputs, interdependencies and official systems:** `<enter or mark Unknown>`
- **G — gates, governance, contingencies and communication:** `<enter or mark Unknown>`
- **N — next state, named receiver, closed loop and expiry:** `<enter or mark Unknown>`
- **Status quo and genuine alternatives:** `<enter or mark Unknown>`
- **Pre-mortem and leading indicators:** `<enter or mark Unknown>`
- **Human decision status:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional extended-hours choice compares status quo, pilot and full rollout; assumptions and a human decision box remain visible.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Named owner—not AI—records accept, revise, defer or reject. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 7 — Portfolio, Dependency, Capacity & Benefit Gate

**Stable ID:** `TPL-07`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Initiative ID and sponsor:** `<enter or mark Unknown>`
- **Charter and strategic link:** `<enter or mark Unknown>`
- **Lifecycle state:** `<enter or mark Unknown>`
- **Milestones:** `<enter or mark Unknown>`
- **Resource demand:** `<enter or mark Unknown>`
- **Dependencies:** `<enter or mark Unknown>`
- **Benefit definition/evidence:** `<enter or mark Unknown>`
- **Risks and equity/burden:** `<enter or mark Unknown>`
- **Continue/revise/pause/stop gate:** `<enter or mark Unknown>`

**Worked synthetic example:** A synthetic portfolio shows two projects competing for the same trainer; the portfolio council receives pause/resequence options.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Portfolio council or sponsor owns priority and funding; no hidden score. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 8 — Board or Committee Brief, Conflict Prompts & Action Register

**Stable ID:** `TPL-08`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Body, charter and authority:** `<enter or mark Unknown>`
- **Meeting type/date:** `<enter or mark Unknown>`
- **Agenda classification:** `<enter or mark Unknown>`
- **Materials and confidentiality:** `<enter or mark Unknown>`
- **Quorum/conflict prompts:** `<enter or mark Unknown>`
- **Decision owner:** `<enter or mark Unknown>`
- **Unofficial decision/action fields:** `<enter or mark Unknown>`
- **Acknowledgment and due date:** `<enter or mark Unknown>`
- **Official record reference:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional committee pre-read marks one decision, two discussion items and an unverified conflict prompt; no official minutes are created.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Chair/secretary/counsel verifies official notice, vote, minutes and conflicts. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 9 — Access, Demand, Capacity & Equity Brief

**Stable ID:** `TPL-09`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Service and period:** `<enter or mark Unknown>`
- **Approved aggregate source:** `<enter or mark Unknown>`
- **Metric definitions:** `<enter or mark Unknown>`
- **Demand/capacity distinctions:** `<enter or mark Unknown>`
- **Numerator/denominator/exclusions:** `<enter or mark Unknown>`
- **Small-cell rule:** `<enter or mark Unknown>`
- **Equity segments:** `<enter or mark Unknown>`
- **Data-quality limits:** `<enter or mark Unknown>`
- **Hypotheses and sponsor questions:** `<enter or mark Unknown>`

**Worked synthetic example:** A synthetic access brief defines third-next-available appointment using fictional aggregate counts and suppresses cells under the local threshold.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Operational/clinical owners validate; no patient action or safe-capacity conclusion. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 10 — Flow, Bottleneck, Handoff & PDSA Map

**Stable ID:** `TPL-10`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Approved process scope:** `<enter or mark Unknown>`
- **Sponsor and QI/research determination:** `<enter or mark Unknown>`
- **Start/end and current state:** `<enter or mark Unknown>`
- **Work/wait/rework/failure demand:** `<enter or mark Unknown>`
- **Bottleneck hypotheses:** `<enter or mark Unknown>`
- **Handoff/dependency map:** `<enter or mark Unknown>`
- **Outcome/process/balancing measures:** `<enter or mark Unknown>`
- **Smallest reversible test:** `<enter or mark Unknown>`
- **Owner and stop rule:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional referral process shows two wait states and one handoff hypothesis; the sponsor—not AI—authorizes a small test.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Sponsor authorizes, executes and monitors any test in official workflows. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 11 — Daily Huddle, Seven Signals & Escalation Board

**Stable ID:** `TPL-11`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Huddle tier and time:** `<enter or mark Unknown>`
- **Seven signals maximum:** `<enter or mark Unknown>`
- **Source/freshness/threshold:** `<enter or mark Unknown>`
- **Fact versus interpretation:** `<enter or mark Unknown>`
- **Human owner:** `<enter or mark Unknown>`
- **Decision or escalation needed:** `<enter or mark Unknown>`
- **Due and acknowledgment:** `<enter or mark Unknown>`
- **Official reconciliation:** `<enter or mark Unknown>`
- **Close/escalate/expire status:** `<enter or mark Unknown>`

**Worked synthetic example:** A synthetic morning huddle displays six aggregate signals, two decisions and one expired item; it sends no messages.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Huddle leader verifies; AI sends nothing and never acts as real-time command. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 12 — Hospital, Clinic, Service or Multi-Site Operating-Model Canvas

**Stable ID:** `TPL-12`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Entity/site/service and operating level:** `<enter or mark Unknown>`
- **Approved service promise:** `<enter or mark Unknown>`
- **Governance and accountabilities:** `<enter or mark Unknown>`
- **Decision rights:** `<enter or mark Unknown>`
- **Enterprise standards:** `<enter or mark Unknown>`
- **Local variations/exceptions:** `<enter or mark Unknown>`
- **Interfaces and handoffs:** `<enter or mark Unknown>`
- **Measures and review cadence:** `<enter or mark Unknown>`
- **Approval owners:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional three-site clinic network separates enterprise standards from two proposed local variations requiring approval.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Authorized governance and functional owners approve; canvas does not enact structure or policy. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 13 — Budget, Forecast, Variance & Sensitivity Scenario

**Stable ID:** `TPL-13`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Budget version, period, currency and units:** `<enter or mark Unknown>`
- **Approved sources:** `<enter or mark Unknown>`
- **Actual/budget/forecast labels:** `<enter or mark Unknown>`
- **Assumptions:** `<enter or mark Unknown>`
- **Variance bridge:** `<enter or mark Unknown>`
- **Base/upside/downside cases:** `<enter or mark Unknown>`
- **Sensitivity drivers:** `<enter or mark Unknown>`
- **Mission/quality/equity effects:** `<enter or mark Unknown>`
- **Finance reviewer and decision:** `<enter or mark Unknown>`

**Worked synthetic example:** A synthetic budget uses $1.0M base expense, ±5% sensitivity and an explicit note that finance has not validated accounting treatment.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Finance validates; template is not an accounting record or transaction. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 14 — Aggregate Revenue-Cycle, Denial & Contract-Question Brief

**Stable ID:** `TPL-14`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Aggregate scope and period:** `<enter or mark Unknown>`
- **Metric definitions/denominators:** `<enter or mark Unknown>`
- **Category map:** `<enter or mark Unknown>`
- **Data-quality questions:** `<enter or mark Unknown>`
- **Workflow/training hypotheses:** `<enter or mark Unknown>`
- **Contract/policy sources:** `<enter or mark Unknown>`
- **Unresolved legal/coding/coverage questions:** `<enter or mark Unknown>`
- **Human owners:** `<enter or mark Unknown>`
- **Next review:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional denial analysis uses aggregate categories only and routes contract-language questions to legal and payer relations.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Authorized specialists decide; no claim, code, coverage, appeal or payer action. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 15 — Procurement, Vendor, Business Case & Exit-Risk Matrix

**Stable ID:** `TPL-15`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Approved need and owner:** `<enter or mark Unknown>`
- **Must-have requirements:** `<enter or mark Unknown>`
- **Alternatives including no purchase:** `<enter or mark Unknown>`
- **Vendor claims versus evidence:** `<enter or mark Unknown>`
- **Lifecycle cost/benefit ranges:** `<enter or mark Unknown>`
- **Security/privacy/interoperability/accessibility:** `<enter or mark Unknown>`
- **Implementation and workforce burden:** `<enter or mark Unknown>`
- **Sustainability/continuity/exit:** `<enter or mark Unknown>`
- **Formal reviewers and gate:** `<enter or mark Unknown>`

**Worked synthetic example:** A synthetic vendor matrix distinguishes claims from evidence and includes data export, implementation burden and termination assistance.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Formal procurement reviews remain required; AI neither selects nor commits. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 16 — Asset, Space, Supply & Sustainability Stewardship Map

**Stable ID:** `TPL-16`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Asset/space/supply category:** `<enter or mark Unknown>`
- **Current approved inventory source:** `<enter or mark Unknown>`
- **Demand and utilization definitions:** `<enter or mark Unknown>`
- **Lifecycle/maintenance owner:** `<enter or mark Unknown>`
- **Continuity and backup:** `<enter or mark Unknown>`
- **Accessibility and safety questions:** `<enter or mark Unknown>`
- **Waste/carbon/resource hypotheses:** `<enter or mark Unknown>`
- **Investment/disposal options:** `<enter or mark Unknown>`
- **Decision and official-system route:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional supply map tests reusable-versus-disposable assumptions without asserting clinical equivalence or making a purchase.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Authorized facilities, supply, clinical engineering, finance and safety owners verify and decide. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 17 — Workforce Capacity, Workload & Skill-Mix Evidence Brief

**Stable ID:** `TPL-17`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Role group and period:** `<enter or mark Unknown>`
- **Aggregation and small-cell rules:** `<enter or mark Unknown>`
- **Headcount/FTE/productive-hour definitions:** `<enter or mark Unknown>`
- **Demand and workload measures:** `<enter or mark Unknown>`
- **Vacancy/turnover/overtime ranges:** `<enter or mark Unknown>`
- **Skill/competency categories:** `<enter or mark Unknown>`
- **Equity/burden/safety questions:** `<enter or mark Unknown>`
- **Scenario assumptions:** `<enter or mark Unknown>`
- **HR/operational governance route:** `<enter or mark Unknown>`

**Worked synthetic example:** A synthetic role-group scenario compares FTE ranges and demand assumptions without displaying or scoring any employee.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** No employee-level decisions, assignment or adequacy claims. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 18 — Psychological Safety, Listening Themes & Response Commitments

**Stable ID:** `TPL-18`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Purpose and visibility statement:** `<enter or mark Unknown>`
- **Voluntary/aggregate source:** `<enter or mark Unknown>`
- **Suppression and confidentiality rules:** `<enter or mark Unknown>`
- **Source words versus themes:** `<enter or mark Unknown>`
- **Interpretations and uncertainty:** `<enter or mark Unknown>`
- **Missing or dissenting voices:** `<enter or mark Unknown>`
- **Immediate official routes:** `<enter or mark Unknown>`
- **Response commitments and owners:** `<enter or mark Unknown>`
- **Feedback-back date:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional listening synthesis reports three themes, one dissenting view and uncertainty; groups below the threshold are suppressed.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Authorized humans handle reports and employment action; no surveillance or retaliation scoring. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 19 — Change Impact, Communication, Learning & Adoption Plan

**Stable ID:** `TPL-19`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Change scope/sponsor/status:** `<enter or mark Unknown>`
- **Affected groups and impact:** `<enter or mark Unknown>`
- **Decided/proposed/unknown labels:** `<enter or mark Unknown>`
- **Co-design and consultation:** `<enter or mark Unknown>`
- **Accessible/language-aware messages:** `<enter or mark Unknown>`
- **Human-voice/anti-slop check: source, owner, action and date retained; filler/clichés/fake warmth removed:** `<enter or mark Unknown>`
- **Learning/support plan:** `<enter or mark Unknown>`
- **Feedback channels:** `<enter or mark Unknown>`
- **Adoption/burden measures:** `<enter or mark Unknown>`
- **Pause/revise/rollback triggers:** `<enter or mark Unknown>`

**Worked synthetic example:** A synthetic scheduling-policy change labels what is approved versus proposed and adds accessible formats, training and rollback triggers.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Sponsors and authorized reviewers approve; no send, publication or launch. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 20 — Leadership, Delegation, Succession & Growth Map

**Stable ID:** `TPL-20`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Leadership purpose:** `<enter or mark Unknown>`
- **Active hat and boundaries:** `<enter or mark Unknown>`
- **Decisions to retain/delegate/consult/escalate:** `<enter or mark Unknown>`
- **Development and sponsorship:** `<enter or mark Unknown>`
- **Succession questions:** `<enter or mark Unknown>`
- **Truthful evidence:** `<enter or mark Unknown>`
- **Capacity/protected-life limits:** `<enter or mark Unknown>`
- **Ninety-day experiment:** `<enter or mark Unknown>`
- **Human review date:** `<enter or mark Unknown>`

**Worked synthetic example:** Jordan delegates meeting preparation but retains final decision communication and protects a weekly recovery block in a personal store.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Governance/HR owns appointments and employment decisions; private data remains owner-only. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 21 — Quality, Safety, Accreditation & Regulatory Readiness Crosswalk

**Stable ID:** `TPL-21`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Entity/site/service:** `<enter or mark Unknown>`
- **Authority and exact source/version:** `<enter or mark Unknown>`
- **Applicability owner:** `<enter or mark Unknown>`
- **Requirement:** `<enter or mark Unknown>`
- **Local policy/control:** `<enter or mark Unknown>`
- **Evidence reference/status:** `<enter or mark Unknown>`
- **Gap and risk question:** `<enter or mark Unknown>`
- **Remediation owner/date:** `<enter or mark Unknown>`
- **Attestation/survey authority:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional readiness crosswalk marks evidence as present, stale or missing; the compliance owner decides sufficiency.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Qualified humans determine applicability and sufficiency; no certification or invented evidence. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 22 — Policy, Control, Audit Evidence & Exception Matrix

**Stable ID:** `TPL-22`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Requirement/source:** `<enter or mark Unknown>`
- **Interpretation labeled:** `<enter or mark Unknown>`
- **Policy/procedure/practice comparison:** `<enter or mark Unknown>`
- **Control objective/activity/frequency:** `<enter or mark Unknown>`
- **Owner and evidence:** `<enter or mark Unknown>`
- **Test and result owner:** `<enter or mark Unknown>`
- **Exception and approval:** `<enter or mark Unknown>`
- **Redline rationale:** `<enter or mark Unknown>`
- **Publication/retention/training route:** `<enter or mark Unknown>`

**Worked synthetic example:** A synthetic policy crosswalk separates source requirement, interpretation, proposed wording and current practice.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Authorized owners approve and publish; no legal or audit opinion. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 23 — Equity, Accessibility, Patient/Family & Community Impact Review

**Stable ID:** `TPL-23`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Decision/initiative:** `<enter or mark Unknown>`
- **Affected groups:** `<enter or mark Unknown>`
- **Approved data and denominators:** `<enter or mark Unknown>`
- **Missing voices:** `<enter or mark Unknown>`
- **Accessibility/accommodation:** `<enter or mark Unknown>`
- **Language access:** `<enter or mark Unknown>`
- **Distributional effects:** `<enter or mark Unknown>`
- **Engagement plan:** `<enter or mark Unknown>`
- **Mitigations/owners/feedback:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional digital-intake initiative identifies language access and screen-reader testing plus a community review before pilot.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Civil-rights/accessibility/community experts review; no protected-class inference or claim of equity. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 24 — Synthetic Emergency, Continuity & Downtime Exercise Plan

**Stable ID:** `TPL-24`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **CLEARLY SYNTHETIC EXERCISE banner:** `<enter or mark Unknown>`
- **Current approved plan/source:** `<enter or mark Unknown>`
- **Objectives and stop phrase:** `<enter or mark Unknown>`
- **Command roles:** `<enter or mark Unknown>`
- **Essential functions/dependencies:** `<enter or mark Unknown>`
- **Injects and expected decisions:** `<enter or mark Unknown>`
- **Manual workarounds/accessibility:** `<enter or mark Unknown>`
- **Recovery/reconciliation:** `<enter or mark Unknown>`
- **After-action observations and owners:** `<enter or mark Unknown>`

**Worked synthetic example:** A clearly labeled exercise rehearses a two-hour scheduling-system outage and stops immediately if a real event is declared.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Real events immediately transfer to official command and procedures. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 25 — Privacy, Cybersecurity, Data-Flow & Third-Party Risk Intake

**Stable ID:** `TPL-25`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **System/use case and owners:** `<enter or mark Unknown>`
- **Data classes and minimization:** `<enter or mark Unknown>`
- **Data-flow/trust boundaries:** `<enter or mark Unknown>`
- **Vendor/hosting/subprocessors:** `<enter or mark Unknown>`
- **Identity/access/logging/encryption:** `<enter or mark Unknown>`
- **Integrations/retention/deletion:** `<enter or mark Unknown>`
- **Continuity/incident/exit:** `<enter or mark Unknown>`
- **Evidence gaps/compensating controls:** `<enter or mark Unknown>`
- **Formal review decision:** `<enter or mark Unknown>`

**Worked synthetic example:** A synthetic vendor intake maps public data only, no production connection, and routes encryption and retention evidence to security/privacy.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Qualified privacy/security/legal owners authorize; intake is not an ATO or HIPAA determination. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 26 — Incident, Issue, Corrective-Action & Official-System Boundary Card

**Stable ID:** `TPL-26`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Synthetic or approved official context:** `<enter or mark Unknown>`
- **Immediate safety/reporting route:** `<enter or mark Unknown>`
- **Known facts versus interpretation:** `<enter or mark Unknown>`
- **Timeline/process questions:** `<enter or mark Unknown>`
- **Human cause/reportability owners:** `<enter or mark Unknown>`
- **Corrective-action proposal:** `<enter or mark Unknown>`
- **Measure/stop rule:** `<enter or mark Unknown>`
- **Verification and closure evidence:** `<enter or mark Unknown>`
- **Privilege/retention boundary:** `<enter or mark Unknown>`

**Worked synthetic example:** A synthetic issue card keeps cause Unknown and lists questions for the authorized review body plus one reversible action proposal.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Authorized humans decide cause, blame, reporting, discipline and closure. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 27 — Digital & AI Use-Case Intake, Stage Gate & Retirement Plan

**Stable ID:** `TPL-27`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Problem/sponsor/owner:** `<enter or mark Unknown>`
- **Users and affected people:** `<enter or mark Unknown>`
- **Non-AI alternatives:** `<enter or mark Unknown>`
- **Data/model/vendor/integrations:** `<enter or mark Unknown>`
- **Decision and rights impact:** `<enter or mark Unknown>`
- **Value/harm hypotheses and baseline:** `<enter or mark Unknown>`
- **Evidence/control gates:** `<enter or mark Unknown>`
- **Monitoring/material-change/incident:** `<enter or mark Unknown>`
- **Renewal/exit/retirement:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional AI meeting-summary use case compares a non-AI template alternative and remains at ‘Proposed—Not Approved.’

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Cross-functional governance approves each stage; no shadow AI or self-approval. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 28 — ORBIT Agent Charter, Permission & Human-Handoff Envelope

**Stable ID:** `TPL-28`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **O — objective, owner, beneficiary and non-goals:** `<enter or mark Unknown>`
- **R — risk tier, rights impact and prohibited decisions:** `<enter or mark Unknown>`
- **B — boundaries for data, sources, tools, destinations, time/cost and expiry:** `<enter or mark Unknown>`
- **I — independent normal/failure/injection/bias/security/recovery tests:** `<enter or mark Unknown>`
- **T — transfer to human or terminate; kill/rollback/purge/retire:** `<enter or mark Unknown>`
- **Install state PERM-P0:** `<enter or mark Unknown>`
- **Proposed maximum permission:** `<enter or mark Unknown>`
- **Manual fallback and incident route:** `<enter or mark Unknown>`

**Worked synthetic example:** A synthetic source-verifier charter allows public URLs only, no tools or writes, PERM-P0 install state and a one-run test proposal.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Named human approves one bounded run after passing evidence. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 29 — Agent Test, Run, Human Decision, Incident & Retirement Receipt

**Stable ID:** `TPL-29`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Agent/charter/version/run ID:** `<enter or mark Unknown>`
- **Owner/permission/expiry:** `<enter or mark Unknown>`
- **Accepted and rejected inputs:** `<enter or mark Unknown>`
- **Tests and evidence:** `<enter or mark Unknown>`
- **Sources/output/uncertainty:** `<enter or mark Unknown>`
- **Human edits and accept/reject:** `<enter or mark Unknown>`
- **Tools/actions/destinations/cost:** `<enter or mark Unknown>`
- **Incident/kill/containment:** `<enter or mark Unknown>`
- **Rollback/purge/retirement proof:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional run fails a provenance test; the receipt records Kill, no release, rollback verification and purge confirmation.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** No release without named-human receipt; failure ends safely with no hidden retry. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.

## Template 30 — Seven-Day Launch & Ninety-Day STEWARD Development Plan

**Stable ID:** `TPL-30`  
**Use when:** a user has passed the appropriate privacy/authority preflight and needs this exact administrative artifact.  
**Common header:** owner; exact title; active hat; legal entity; operating level; site/service; delegated authority source; decision threshold; context/partition; source/version; human owner; created/updated/expiry; retention; correction; export; deletion.

**Purpose-specific fields:**

- **Days 1–7 actions and owners:** `<enter or mark Unknown>`
- **Power previews and exact states:** `<enter or mark Unknown>`
- **Agents retained PERM-P0 or separately approved:** `<enter or mark Unknown>`
- **Benefit, burden and failure observations:** `<enter or mark Unknown>`
- **Day-7 retain/revise/pause/remove:** `<enter or mark Unknown>`
- **Days 8–30 maximum-three-power plan:** `<enter or mark Unknown>`
- **Days 31–90 one bounded track:** `<enter or mark Unknown>`
- **Material-change/expiry review:** `<enter or mark Unknown>`
- **Uninstall test:** `<enter or mark Unknown>`

**Worked synthetic example:** A fictional seven-day launch previews two powers, activates none, records low burden and schedules a 30-day retain/remove review.

**Validation rules:** required fields cannot be inferred; approved versus proposed, fact versus interpretation and actual versus estimate stay distinct; sources and human owners must be current; prohibited partitions never join; expired artifacts block action.  
**Human gate and safe exit:** Every milestone has a receipt; zero activated powers remains acceptable. The named human may accept, revise, reject or delete. If the gate fails, save only a minimal blocker receipt with no sensitive detail and route to the official process.  
**Boundary:** This template is not a patient record, clinical direction, employee file, assignment, performance decision, accounting entry, claim, contract, procurement commitment, legal/compliance conclusion, incident report, security authorization, board record, policy publication or external communication.
