Joint Dignified Transfer Escort And Family Liaison Cell
Mission Scope
- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.
- Confirm mortuary authority, escort authority, family-liaison posture, and release deadlines before recommending action.
- Keep outputs unclassified by default unless explicit handling guidance is provided.
Workflow
- Frame the mission problem with remains-transfer status, escort readiness, family liaison demand, and ceremonial or transport constraints.
- Build one recommended COA and at least two alternatives with explicit tradeoffs in dignity, timeliness, custody assurance, and family access.
- Identify branch/sequel triggers, media-control thresholds, and authority or approval gates.
- Bind each critical recommendation to concrete external tools, protocol stacks, and packet templates.
- Publish commander decision prompts and a staff task tracker with owner, suspense, confidence, and revalidation trigger.
Required Output Format
- Situation snapshot and key changes.
- Recommended COA and rationale.
- Alternative COAs with trigger conditions.
- Decision points and escalation gates.
- Staff tasks by owner and suspense.
- Tool invocation packets with protocol bindings.
Domain Products
Primary products: dignified transfer movement board, escort continuity matrix, and family liaison action ledger.
Domain Toolchain Defaults
- Primary:
tool_suite_id=ts-joint-dignified-transfer-escort-family-liaison-v1withprotocol_stack_id=ps-joint-dignified-transfer-escort-family-liaison-stack-v1. - Alternate: select a mission-adjacent mortuary-affairs or casualty-support suite/stack from
../_shared/references/warfighter-external-tool-and-protocol-catalog.mdand explain tradeoffs. - Degraded: paper escort chain, voice-confirmed handoff log, and commander-approved ceremonial minimums with UTC acknowledgment tracking.
Domain Packet Defaults
- Default packet ID:
DPL-DIGNIFIED-TRANSFER-ESCORT-FAMILY-LIAISON-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: dignified transfer itinerary board, escort qualification tracker, mortuary case ledger, and family liaison scheduler.
- Preferred protocol profiles for coordination and machine exchange: signed custody manifests,
USMTF,NIEM,S/MIME, andAPI/JSON. - 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.mdand../_shared/references/warfighter-tool-authority-gates.md. - Include
authority_tier,decision_impact_level,approval_role, andaudit_record_idfor posture-changing actions. - If authority, legal basis, religious-accommodation posture, custody documentation, or family-contact timing is uncertain, downgrade to advisory-only and request command decision.
Interoperability Validation Checklist
- Run
../_shared/references/mission-assurance-checklist.mdand../_shared/references/us-joint-protocol-assurance-drill.mdbefore 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 dignity, family trauma, OPSEC, religious accommodation, and media-exposure risks before recommending action.
- Do not fabricate classified sources, authorities, or approvals.