Implemented in v2.8.22
Tactical Friction
"Roadmap/release pages were mixing promises and shipped history. Hard to trust planning."
Feedback
Command center for bugs and field requests
Direct Line to the Founder: Help Us Sharpen the Scanner.
We audit cloud waste by day and ship fixes by night. Found a bug, a missing protocol, or rollout friction? Send it here. Every submission is reviewed and routed into execution planning.
Best signal
One issue per dispatch
Tight reports move from investigation to fix much faster.
Useful detail
Version, provider, region
Those three fields are usually enough for reproducible triage.
Visibility
Feedback is tied to roadmap rhythm
You can verify what moves into next sprint on Tactical Roadmap.
Submit Feedback
Issue Dispatch
Use this form like a command channel: what broke, where it broke, and what would count as done.
Voice of the Field
Recent operator notes and status.
Public snippets from real feedback cycles so new users can see execution transparency.
Under Investigation
Direct Hit
"Admin trend panels occasionally desync after date-range switch under proxy-heavy traffic."
Queued Next Sprint
Surface Noise
"Add stronger founder-facing acknowledgements after feedback submit so users know where to track progress."
Next Stop
Need delivery context instead of a form?
The roadmap page shows what is active now, what is queued next, and what shipped recently. The release ledger keeps the longer record.