# AMQ Bridge documentation map

## Authority order

1. `docs/current/` — executable current contract.
2. Accepted `docs/adr/` — durable architecture decisions.
3. `docs/verification/` and `docs/e2e-test-matrix.md` — acceptance evidence.
4. `docs/postmortems/` and `docs/bug-fix-log.md` — incidents and residual risks.
5. `README.md` — user-facing quickstart.
6. `docs/archive/` — historical material, not implementation guidance.

## Current direction

AMQ Bridge is a harness-neutral core with pluggable harness and transport adapters. Pi + AMQ filesystem is first path. OpenCode/Codex support is planned through adapters, not protocol forks.

## Current Pi stable baseline

- unfinished nested active work survives read, restart, and owner takeover through bounded LIFO stack;
- reply/resolve validate current target identity;
- lifecycle heartbeat/reload health has explicit diagnostics;
- natural acceptance uses isolated roots and exact sender/kind/priority checks;
- stale historical work has explicit resume/abandon/quarantine policy.

## Remaining architecture work

- durable operation journal and idempotent cross-transport reply;
- hard cancellation of an already-running provider turn (urgent stack scheduling now resumes at next available turn);
- runtime `BridgeCore` façade wired to harness adapters;
- OpenCode/Codex adapters, deferred until core architecture and lifecycle semantics mature;
- exact deterministic mailbox/state assertions for all authentic harnesses.

These are post-baseline work items, not reasons to replace notify-pull.