Joint Combat Camera Public Affairs Release Authenticity Cell
Mission Scope
- Treat this skill as planning and decision support for U.S. warfighter media provenance, public-release, and information-integrity decisions.
- Confirm release authority, source imagery status, OPSEC review posture, partner caveats, and public-affairs timelines before recommending action.
- Keep outputs unclassified by default unless explicit handling guidance is provided.
Workflow
- Frame the mission problem using media source, custody chain, release objective, legal or policy constraints, and deception threat indicators.
- Build one recommended COA and at least two alternatives with explicit tradeoffs in authenticity confidence, speed, OPSEC risk, and strategic-communication effect.
- Identify branch triggers for redaction, release hold, partner coordination, and adversary deepfake rebuttal.
- Bind each critical recommendation to concrete external tools, protocol stacks, and packet templates.
- Publish commander decision prompts and a staff 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: release-approval matrix, media provenance ledger, and authenticity rebuttal plan.
Domain Toolchain Defaults
- Primary:
tool_suite_id=ts-joint-combat-camera-public-affairs-release-authenticity-v1withprotocol_stack_id=ps-joint-combat-camera-public-affairs-release-authenticity-stack-v1. - Alternate: select a mission-adjacent public-affairs, information-integrity, or evidence-custody suite or stack from
../_shared/references/warfighter-external-tool-and-protocol-catalog.mdand explain tradeoffs. - Degraded: commander-readable summary only with delayed media release until provenance and OPSEC checks pass.
Domain Packet Defaults
- Default packet ID:
DPL-COMBAT-CAMERA-PA-RELEASE-AUTH-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: media provenance verifier, release authority board, and redaction or watermark workflow.
- Preferred protocol profiles for coordination and machine exchange: signed media manifests,
STANAG 4609aligned exchange,S/MIME,API/JSON,USMTF, andSTIX/TAXII. - 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 or action template, expected output schema, protocol or 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 media provenance, OPSEC review, or release authority is uncertain, downgrade to advisory-only and request human command review.
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 source ambiguity, synthetic-media risk, partner caveats, and OPSEC exposure before recommending action.
- Do not fabricate imagery provenance, release approvals, or authenticity findings.