Roadmap

Knocker’s current shape is intentionally narrow:

• verified webhook ingress
• durable Delivery and Event rows on SQLite
• operator reads and event actions over the shared SQLite contract
• explicit pruning plus small retention automation/helpers over the shared core primitive
• bindings for Bun, Elixir, Go, Node, Python, and Ruby
• SQLite-shaped runtime-confidence tests plus representative local performance evidence

Still intentionally deferred

• hosted packages for every binding runtime
• richer retention policy beyond the current automation
• hosted control plane or built-in admin API
• HTML admin UI
• framework-specific adapters

Release focus

The current release work is about clarity and proof, not new semantics:

• ship-worthy docs
• representative performance evidence
• explicit compatibility and publish criteria

That proof is intentionally modest:

• a real subprocess-kill crash test
• a fresh-process reopen path
• a small local benchmark harness plus loose CI performance floors
• binding smoke tests over the shared SQLite contract

If Knocker grows later, it should do so by staying library-shaped: small durable semantics in the core, thin binding-owned ergonomics on top.