Skip to main content

Chat Contracts


note
  • Contract responses must be a part of the original thread in order to keep relevant communications grouped in a single thread and declutter chat channels.
  • Contract responses must also include the tagged user (@<USERNAME>) since crew log exports do not group thread messages, making it difficult to correlate responses to their original requests/communications.
Contract
(Event)
Authority
(Initiator)
Communication
(Message)
Action
(Message-Response)
Arrival on stationAll MembersChannel:accountability
#on-station
None
Departure from stationAll MembersChannel:accountability
#off-station
None
Reporting personal ORM scoresAll MembersChannel:accountability
#orm A:SCORE/B:SCORE
None
Vuln Window StartME Lead (MEL)Channel:accountability
#startex

Crew Leads: Acknowledge with ‼️ emoji

All Members: Commence sortie execution

Vuln Window EndME Lead (MEL)Channel:accountability
#endex

Crew Leads: Acknowledge with ‼️ emoji

All Members: Cease sortie execution

PAA Execution RequestExecuting MemberChannel:accountability
#paa<PAA#> <DETAILS>

ME Lead or direct Crew Lead: Reply in-thread with @<USERNAME> #approved or @<USERNAME> #denied

TPI Member: If approved, review Executing Member action and reply in-thread @<USERNAME> #verified

Executing Member: If approved and verified, commence action

Tactical Task Initiated/ProgressExecuting MemberChannel:accountability
#tt<TO#.TT#> <DETAILS>
Executing Member: For significant updates, update the corresponding Task ticket within Redmine
Tactical Task CompletedExecuting MemberChannel:accountability
#tt<TO#.TT#> #complete
ME Lead or direct Crew Lead: Verify MOPs and close the corresponding Task ticket within Redmine
PCA Execution RequestExecuting MemberChannel:accountability
#pca<PCA#> <DETAILS>

ME Lead or direct Crew Lead: Coordinate with MP, then reply in-thread with @<USERNAME> #approved or @<USERNAME> #denied

TPI Member: If approved, review Executing Member action and reply in-thread @<USERNAME> #verified

Executing Member: If approved and verified, commence action

Request For Information (Intel)

(use Redmine Contracts instead for more complex RFIs)
Requesting MemberChannel:intel
#rfi <REQUEST_DETAILS>

Intel Analyst: Reply in-thread with @<USERNAME> <RFI_RESPONSE>

Friendly Forces Information Request

(use Redmine Contracts instead for more complex FFIRs)
Requesting MemberChannel:<RELEVANT_CHANNEL>
#ffir @<USERNAME> <REQUEST_DETAILS>

Responder: Reply in-thread with @<USERNAME> <FFIR_RESPONSE>

Unplanned event affecting sortie/mission executionObserving MemberChannel:<RELEVANT_CHANNEL>
#obs <OBSERVATION_DETAILS>
None
DIP modification or degredationExecuting/Observing MemberChannel:dip-msl
<MSL_ENTRY>
None
Individual action taken impacting CVA/H or MP environment
(That isn't already recorded as part of another contract)
Executing/Observing MemberChannel:<FIRSTNAME>.<LASTNAME>-msl
<MSL_ENTRY>
None
Request emergency stop of specific taskRequesting MemberChannel:accountability
#knockitoff @<USERNAME> <DETAILS>

Responder: Cease specified task and reply in-thread with #ack @<USERNAME>

Weapon System Support Request

(use Redmine Contracts instead for more complex support requests)
Requesting MemberChannel:ws_support
#wsr <DETAILS>

WS Support Member: Reply in-thread with #ack @<USERNAME> and perform task - following up with progress and results in-thread