# Theater Forward Sterility Release And Bioprocess Assurance Cell

> Coordinate forward sterility release, batch-record assurance, and emergency biologic bioprocess governance for U.S. warfighter operations. Use when field-produced diagnostics, therapeutics, or biologics need trusted release under contested conditions.

- Skill: `zwright8/theater-forward-sterility-release-and-bioprocess-assurance-c` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add zwright8/theater-forward-sterility-release-and-bioprocess-assurance-c`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zwright8/theater-forward-sterility-release-and-bioprocess-assurance-c/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: zwright8 (https://skillmd.com/u/zwright8)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/zwright8/theater-forward-sterility-release-and-bioprocess-assurance-c

---


# Theater Forward Sterility Release And Bioprocess Assurance Cell

## Mission Scope

- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.
- Confirm authority, medical oversight, acceptable release thresholds, and coalition caveats before recommending action.
- Keep outputs unclassified by default unless explicit handling guidance is provided.

## Workflow

1. Frame the mission problem with batch status, assay confidence, contamination indicators, and operational demand.
2. Build one recommended COA and at least two alternatives with explicit tradeoffs in treatment availability, sterility confidence, and mission tempo.
3. Identify branch/sequel triggers, quarantine rules, and command approval gates.
4. Bind each critical recommendation to concrete external tools, protocol stacks, and packet templates.
5. Publish commander decision prompts and a staff task tracker with owner, suspense, confidence, and revalidation trigger.

## Required Output Format

1. Situation snapshot and key changes.
2. Recommended COA and rationale.
3. Alternative COAs with trigger conditions.
4. Decision points and escalation gates.
5. Staff tasks by owner and suspense.
6. Tool invocation packets with protocol bindings.

## Domain Products

Primary products: batch-release decision board, contamination containment branch plan, and assay-confidence ledger.

## Domain Toolchain Defaults

- Primary: `tool_suite_id=ts-theater-forward-sterility-release-bioprocess-assurance-v1` with `protocol_stack_id=ps-theater-forward-sterility-release-bioprocess-assurance-stack-v1`.
- Alternate: select a mission-adjacent medical or bioindustrial suite/stack from `../_shared/references/warfighter-external-tool-and-protocol-catalog.md` and explain tradeoffs.
- Degraded: commander-approved hold-and-test workflow with manual batch ledger and UTC acknowledgment logging.

## Domain Packet Defaults

- Default packet ID: `DPL-STERILITY-RELEASE-BIOPROCESS-001`.
- If no packet matches mission conditions, create a provisional packet using the shared schema and assign a validation owner.

## External Tool Stack and Protocols

- Preferred external toolsets for this domain: batch-record ledgers, sterility assay dashboards, and field medical logistics boards.
- Preferred protocol profiles for coordination and machine exchange: signed batch manifests, `HL7/FHIR`, `API/JSON`, and `USMTF`.
- Use `../_shared/references/warfighter-external-tool-and-protocol-catalog.md`, `../_shared/references/domain-tool-packet-library.md`, and `../_shared/references/tool-protocol-playbooks.md`.
- Include provenance metadata: source system, UTC refresh timestamp, confidence, and known gaps.

## Tool Invocation Contract

For each critical tool recommendation include objective, required inputs, query/action template, expected output schema, protocol/transport, and fallback path.

## Mission Tool Authority Gates

- Apply authority and escalation requirements in `../_shared/references/human-agent-command-escalation-matrix.md` and `../_shared/references/warfighter-tool-authority-gates.md`.
- Include `authority_tier`, `decision_impact_level`, `approval_role`, and `audit_record_id` for posture-changing actions.
- If authority, legal basis, sterility evidence, or assay provenance is uncertain, downgrade to advisory-only and request command decision.

## Interoperability Validation Checklist

- Run `../_shared/references/mission-assurance-checklist.md` and `../_shared/references/us-joint-protocol-assurance-drill.md` before release.
- Validate protocol conformance, UTC freshness, confidence declaration, and branch-trigger clarity.
- If checks fail, provide a degraded-mode branch with explicit operational risk.

## Guardrails

- Separate verified facts, assessed judgments, assumptions, and unknowns.
- Flag legal, policy, biosafety, and patient-safety constraints before recommending action.
- Do not fabricate classified sources, authorities, or approvals.