Skip to content

/edikt:capture ​

Mid-session sweep — surfaces uncaptured ADRs, invariants, and documentation gaps in the current conversation before they're lost to compaction. Read-only: it surfaces candidates, it doesn't create anything.

Usage ​

bash
/edikt:capture

What it does ​

Scans the conversation for three signal types:

SignalSurfaced asRoutes to
Product architecture choice (a new boundary, a contract, a data store, a cross-context dependency, an external provider in the product's call path) with a real rejected alternativeADR candidate/edikt:adr:new
Hard constraint where violation causes real harmInvariant candidate/edikt:invariant:new
Design rationale or decisions missing from project docsDocumentation gap/edikt:docs:review

Every candidate runs through the GL-001 capture gates before being surfaced — burden of proof is on capture, not silence, and a candidate with no real rejected alternative isn't proposed at all. It never surfaces an ADR candidate for implementation inside existing boundaries (algorithms, data structures, refactors), tooling used to build the product that does not ship in it (linters, test runners, local tracing stacks, editor and agent config), local dev setup, or experiments and measurements. Then it reports what it found:

text
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 CAPTURE SWEEP
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

ADR Candidates (1 found)

  1. Use Redis for session storage
     Decision: Redis over in-memory sessions
     Alternatives considered: in-memory store (doesn't survive restarts)
     Rationale: sessions must persist across deploys
     → Suggestion only — /edikt:adr:new if you want it recorded (its intake gates may still refuse it)

Invariant Candidates (1 found)

  1. Sessions must expire within 24h
     Consequence of violation: stale sessions accumulate, memory grows unbounded
     → Run /edikt:invariant:new to capture this

Documentation Gaps (0 found)

  None found — no uncaptured decisions in this category.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✅ Capture sweep complete

Next: nothing above is required — a healthy session produces zero ADRs. Use /edikt:adr:new or /edikt:invariant:new only for an item you choose to record.

Nothing gets created automatically — every finding is a suggestion you may decline, not an automated write. A missing ADR never blocks a build or a review.

When to use ​

Run at the end of a conversation where multiple governance-worthy things happened. Instead of remembering to run four different commands, run one.

The Stop hook suggests (never requires) specific capture commands during conversations. /edikt:capture is the catch-all when you want to sweep the whole conversation at once.

Natural language triggers ​

  • "capture everything from this conversation"
  • "let's save what we decided"
  • "wrap up this conversation"

What's next ​

Released under the Elastic License 2.0. Free to use, not for resale.