Persistent correction logging across missions #9
Description
Summary
Corrections during graduated discipline (Signal, Standing Order Remedy, Damage Control) are currently logged per-mission in quarterdeck reports and the Captain's Log. There is no persistent store that carries learning across missions.
Proposal
Track correction frequency per anti-pattern across missions so future missions can use that data to adjust defaults — e.g. risk tiers, crew composition, or standing order emphasis.
Potential steps:
- Define a lightweight schema for correction events (anti-pattern, level, outcome, mission context).
- Persist them somewhere accessible between missions (e.g. a local JSON/YAML log).
- Surface aggregated patterns in sailing orders or squadron formation as advisory signals.
Context
Raised from community discussion on graduated discipline and agent governance feedback loops.