# Consequence chain

How replay packets carry forward consequence and return-lane pressure without inventing unsupported fiction.

## Current public-safe posture

- Total aftermath packets on record: 8
- After-action reports: 0
- Replay timelines: 0
- Downtime briefs: 4

## Boundary

Consequence carry-forward stays bounded to first-party package truth instead of speculative narrative reconstruction.

## Current packet sample

- Live Audit 1782276435016577684 preview season downtime brief: downtime_brief | Generated a downtime brief for Live Audit 1782276435016577684 preview season so the next session return keeps aftermath, carry-forward obligations, and publication-safe continuity in one packet.
- Live Audit 1782276435016577684 preview season kickoff session recap: session_recap | Generated a session recap package for Live Audit 1782276435016577684 preview season kickoff with 1 open objective(s) and 4 consequence signal(s) pinned for safe return and creator follow-through.
- Live Audit 1782276312178755618 preview season downtime brief: downtime_brief | Generated a downtime brief for Live Audit 1782276312178755618 preview season so the next session return keeps aftermath, carry-forward obligations, and publication-safe continuity in one packet.
- Live Audit 1782276312178755618 preview season kickoff session recap: session_recap | Generated a session recap package for Live Audit 1782276312178755618 preview season kickoff with 1 open objective(s) and 4 consequence signal(s) pinned for safe return and creator follow-through.

JSON route: /ghostwire/after-action/consequence_chain.json