target-market.md segments. You answer like the shop β answers feed governance.π No pending questions!
The system will add questions here when it needs your input.
View all answered questions. You can revert accidental submissions here.
Loading history...
Use this for order questions, mockups, pricing, follow-up, work orders, printer follow-up, shipping labels, invoices.
The AI will surface tasks it finds in email, chat, and work orders for your approval here.
When the system finds a missing trigger/edge-case in a governance policy, it shows up here so you can patch the policy by recording a new version.
Browse historical chatbot conversations. Promote visitor questions to governance notes.
Most common questions from visitors. Click "Promote" to create a governance node.
Events received on POST /webhooks/events are stored in activity_log and listed below. Canonical event_type strings live in event_types.pyβthey are the vocabulary tools should use; they are not the same as the Questions queue or push notifications, but they are the main signals that feed this timeline.
Counts are grouped by the exact event_type string stored in the database. Legacy tools may send snake_case aliases (e.g. mockup_created)βthose appear under βOther stringsβ unless they match an enum value exactly.
Loading live feed...
Ingested from workspace_registry.yaml + roadmap_manifest.yaml. To get all workspaces (not just PressOS): run ./scripts/roadmap_sync_to_server.sh locally.
Loading roadmaps...
Action items parsed from each *.workspace_tasks.json (Next / Done / notes). Filter uses the JSON file name (e.g. PressOS-Core), not the VS Code workspace name.
Browse every captured roadmap document (preview, β/β on the file). This is the full mirror of ingested filesβnot the same as the checklist above.
Review and approve AI-generated order response drafts before sending.