After-Action Cases
The consequences that follow your operations.
What They Are
Field operations rarely end cleanly. Individuals you encounter—faction representatives, intelligence contacts, adversaries you spared, allies you assisted—remember your actions.
After completing missions, these contacts may reach out through the Reticle ansible network with follow-up situations requiring attention.
Urgency Classifications
| Urgency | Response Window | Consequence of Neglect |
|---|---|---|
| Critical | 4 hours | Operational risk, relationship damage |
| Moderate | 24 hours | Important follow-ups |
| Low Priority | 72 hours | Routine matters |
| Background | 168 hours | Non-urgent communications |
Response Processing
Unlike real-time agent communications, After-Action responses operate asynchronously:
- You craft a response
- Message enters pending delivery queue
- Delivery follows urgency-based timing
- Contact's reply follows same timing system
Consequences of Neglect
When you fail to respond within windows:
- Idina intervenes with an automated response, based on the options provided in the mission
- After two interventions, case goes dormant
- Contacts notice automated handling—reputation suffers
- Chronic neglect affects future mission invitations
Strategic Value
Successfully resolving After-Action situations:
- Builds relationships yielding future intelligence
- Are noted by agents interacting with you during live missions
- Demonstrates operational maturity
Learn More
- Intelligence Overview - All intelligence systems
- Agent Communications - Working with contacts