EP-021-detail-battle-rhythm-collection

[DETAIL - ENGAGEMENT REF] - Detail Battle Rhythm Map

EP-021 Detail Battle Rhythm - execution workspace for a running protective detail. Central topic = the detail on this engagement. Branches = the recurring cadence the Team Leader (RF) commands the detail against: daily cycle, shift handover, weekly cycle, per-engagement events, decision authority, and admin. Tick each occurrence as it happens; clone the serial blocks per shift, per leg, per week. → executes EP-021 in full; consumes ART-daily-brief and EP-019 PIR set; feeds EP-016 (daily brief) and EP-023 (movement execution).

00 * Process Plan - Gates & Triggers

Stand-up conditions, ownership, and the deviation rule that governs every branch below. → EP-021 SS1 Purpose and Authority.

Ownership (fixed for this engagement)

• Field: [Team Leader (initials) - owns rhythm, approves changes]
• Field: [Shift Lead (initials, per shift) - executes daily cycle]
• Field: [Operations Manager (initials) - owns logistics/admin slots]
• Field: [Detail Intelligence Officer (initials) - owns intel pull and PIR feed]

Stand-up trigger

• ART-engagement-order activated (reference: [ ])
• Rhythm stood up within 24 hours of activation
• This document instantiated with detail-specific times (M-hour, TZ, shift structure)
• First full daily cycle scheduled for day one

Anchor products confirmed live

• ART-daily-brief feed reachable and populating
• EP-019 standing PIR set current and loaded
• EP-016 daily brief slot and distribution list confirmed

Deviation rule (governs every branch)

• Decision: [ ] Principal activity always outranks the rhythm
• Displaced event rescheduled or consciously skipped by the Shift Lead
• Every skip logged (→ 99 skipped-event log); it never silently disappears

00b * Battle Rhythm & Triggers

The standing cadence itself - daily, weekly, and per-engagement layers. This is the dominant spine for EP-021 (continuous detail). → EP-021 SS2 Daily Cycle, SS4 Weekly Cycle, SS5 Per-Engagement Events.

Daily cycle (today’s instance)

Reproduce times as offsets from M-hour, not fixed clock times; reset at evening sync.

• Field: [M-hour today - HH:MM local, TZ: [ ]]
• M-2:00 Intelligence pull and overnight review complete (Detail Intelligence Officer) - ART-daily-brief + overnight logs in
• M-1:30 Daily detail brief delivered per EP-016 to all oncoming personnel
• M-1:00 Vehicle and kit checks complete (SYS-009/SYS-010); deficiencies reported to Shift Lead
• M-0:30 Comms check on all nets complete per EP-011; failures worked before movement
• M-hour First principal movement executed per EP-023
• Midday SITREP delivered to Team Leader (routine); immediate reports event-driven per EP-011
• Shift change handover complete (→ 01 Shift Start / Handover serial)
• E+0:30 Evening sync held (Shift Lead, DIO, Ops Manager): next-day itinerary confirmed, M-hour set, PIR review per EP-019, logistics needs to Ops Manager
• E+1:00 Daily log closed (occurrences, deviations, reports filed)

Weekly cycle serial

Clone per week of the engagement. → EP-021 SS4.

• [week of - e.g. YYYY-MM-DD]
  • MON - PIR set review (retire/revise/re-task) per EP-019 SS8 - owner: Detail Intelligence Officer + Team Leader
  • TUE - Kit and medical audit, rotating third of inventory - owner: Operations Manager
  • WED - Route and venue refresh vs. EP-003 - owner: Advance Lead / drivers
  • THU - Rehearsal block: one immediate-action drill from EP-012 - owner: Shift Lead
  • FRI - Weekly rollup to client / family office - owner: Team Leader
  • SAT/SUN - Reduced rhythm: daily cycle only
  • Notes / deviations this week: [ ]
• [week 2]
  • MON PIR review
  • TUE kit/medical audit
  • WED route/venue refresh
  • THU rehearsal drill
  • FRI weekly rollup
  • SAT/SUN reduced rhythm
  • Notes: [ ]

Per-engagement event triggers

Non-calendar events keyed to engagement phase. → EP-021 SS5.

• Engagement start: rhythm stood up, first daily cycle run (→ 00 stand-up trigger)
• New AO or venue identified → EP-020 advance planning cycle spurred off the rhythm; milestones enter daily brief until Gate 5
• Decision: [ ] Threat posture change to Elevated or above (L x I >= 11) → daily brief moves to twice daily; PIR review becomes daily until posture drops
• Engagement end / stand-down declared → after-action report per EP-017 due within [5] days; rhythm formally closed; logs archived per CLASSIFICATION.md

01 * Shift Start / Handover

The mandatory six-item handover briefed post by post; most detail failures cluster here. → EP-021 SS3 Shift Change Standard.

Shift handover serial

Clone per shift change, per post.

• [handover - e.g. Day shift → Night shift, Post 2]
  • Principal status and location briefed; party members in play confirmed
  • Active threat picture briefed: changes since last brief, open EP-019 PIR answers, surveillance indicators logged
  • Posture and posts briefed: current formation, post assignments, patrol/dwell state per EP-009
  • Equipment briefed: radios, medical kits, vehicle states, discrepancies per SYS-009/SYS-010
  • Pending actions briefed: expected visitors/vendors (PIR-9 check), deliveries, itinerary changes, open logistics requests
  • Comms briefed: active nets, call signs, duress word confirmed per EP-011
  • Decision: [ ] Oncoming Shift Lead accepts shift by name over command net
  • Acceptance logged - time: [ ]
• [handover 2 - Night shift → Day shift, Post 2]
  • Principal status / party
  • Threat picture / PIR answers
  • Posture and posts
  • Equipment
  • Pending actions
  • Comms
  • Decision: [ ] Shift accepted by name
  • Acceptance logged - time: [ ]

02 * Static / RON Posture

Formation, post rotation, and remain-overnight posture between movements, and the duty-limit envelope that bounds it. → EP-021 SS7 (posture adjustments within approved formation set) and SS8 Fatigue and Sustainment.

Current posture

• Field: [Formation in effect - approved set reference: [ ]]
• Field: [Post assignments - reference EP-009 posture standard]
• Static/RON location confirmed secure for current posture tier
• Decision: [ ] Posture adjustment within approved formation set - Shift Lead authority, no escalation required

Duty-limit compliance (this shift)

• No operator exceeds [12] hours on post without relief
• Minimum [8] hours rest between shifts confirmed for oncoming personnel
• Decision: [ ] Scheduled coverage cannot meet duty limits for more than [48] hours → Team Leader requests vendor surge via Operations Manager (ART-vendor-roster)
• Notes / exceptions: [ ]

03 * Movement Serials

The rhythm schedules the movement window; execution detail (routes, formations, actions-on) is EP-023. Tick the scheduling handoff here, not the movement itself. → EP-021 SS2 (M-hour movement) and SS5 (new-AO spur).

Movement window serial

Clone per scheduled movement this day.

• [movement - e.g. M-hour - Lodging to Site]
  • Movement window confirmed in daily cycle (→ 00b daily cycle)
  • Execution handed off to EP-023 movement-serial process
  • Route status confirmed current per EP-003 (refreshed weekly, → 00b WED)
  • Completion / arrival confirmed back to Shift Lead
  • Notes / deviation from schedule: [ ]
• [movement 2 - Midday - Site to Venue]
  • Window confirmed
  • Handed off to EP-023
  • Route current
  • Arrival confirmed
  • Notes: [ ]

New-AO spur trigger

• Decision: [ ] New venue or AO identified → spur EP-020 advance planning cycle
• Spur milestones added to daily brief until Gate 5 closure

04 * Arrival / Departure sequences

The recurring checkpoints inside the daily cycle that bracket each movement and shift boundary. → EP-021 SS2 Daily Cycle (full timeline).

Daily checkpoint serial

Clone per checkpoint occurrence today; reproduces the SS2 timeline as tick-off gates.

• [checkpoint - e.g. M-1:30 Daily detail brief]
  • Time held at correct offset from M-hour
  • Participants present (all oncoming personnel)
  • Output captured: threat changes, PIR status, itinerary, comms settings, weather/route status
• [checkpoint - M-1:00 Vehicle and kit checks]
  • Time held
  • SYS-009/SYS-010 checklists run
  • Deficiencies reported to Shift Lead
• [checkpoint - E+0:30 Evening sync]
  • Time held
  • Next-day itinerary confirmed
  • Next M-hour set
  • PIR review per EP-019 logged

05 * Principal Interface Standard

How the detail interfaces with the principal’s schedule and how the rhythm yields to it. → EP-021 SS1 deviation rule and SS7 client-consultation decisions.

Interface checks

• Principal’s planned day reviewed against rhythm anchor (M-hour set from principal’s schedule, not clock time)
• Decision: [ ] Principal activity conflicts with a scheduled rhythm event → event rescheduled or skipped by Shift Lead, logged (→ 99)
• Activity-cancellation recommendation required → routed to client consultation (→ 06 client-consultation decision)

Client-facing product touchpoints

• Weekly rollup content reviewed before Team Leader delivery (→ 00b FRI)
• Any protective-coverage change communicated to client per SS7 client-consultation route

06 * Running Decision Points

The rhythm pre-decides who decides; immediate threats never wait for a scheduled slot. → EP-021 SS7 Decision and Escalation Cadence.

Decision-point serial

Clone per decision event as it occurs.

• [decision event - e.g. route deviation requested]
  • Decision: [ ] Immediate (any time) - any operator declares emergency, initiates EP-012 actions, net to flash traffic per EP-011
  • Decision: [ ] Shift Lead decides without reference - posture adjustment / post rotation / minor itinerary timing shift
  • Decision: [ ] Team Leader decides - route change off approved EP-003 set / venue addition (spurs EP-020) / posture change crossing threat band / staffing change / no-go call
  • Decision: [ ] Client consultation required - activity cancellation / protective-coverage change / budget-affecting surge staffing (via Operations Manager, ART-vendor-roster)
  • Decision logged with authority level and rationale
• [decision event 2]
  • Decision: [ ] Immediate / Shift Lead / Team Leader / Client (select one)
  • Decision logged

99 * Execution Admin

Running product register, deviation and skip log, and the change-control record for this rhythm instance. → EP-021 SS6 Reporting and Product Cadence, SS8 Fatigue and Sustainment, SS9 Rhythm Discipline and Change Control.

Product register (this cycle)

• Daily detail brief (EP-016) delivered on schedule - M-1:30 daily
• SITREP delivered - midday + event-driven
• PIR status (EP-019) updated - daily at evening sync; weekly deep review MON
• Daily log closed - E+1:00 daily
• Weekly client rollup delivered - FRI
• After-action report (EP-017) filed - per engagement / per serious incident

Skipped-event log (running)

Every skipped or displaced event with reason; reviewed weekly per SS9.

• [event skipped - e.g. evening sync - date]
  • Reason: [ ]
  • Rescheduled to / consciously dropped: [ ]
  • Logged by: [ ]
• [event skipped 2]
  • Reason: [ ]
  • Disposition: [ ]

Change control

• Rhythm change proposed - description: [ ]
• Decision: [ ] Team Leader approves change
• Change takes effect at next daily brief (never mid-shift, except emergency posture changes)
• Current version published to all detail personnel with EP-010 OPORD annexes

Corrective actions from EP-017 findings

• [finding - e.g. missed handover item, stale PIR, fatigue event] → corrective action opened against this document → version incremented

Open actions / RFIs

• [open item]
• [open item]