🗂PMOS

The vision

PMOS is a product-management OS for teams who actually run their day inside messaging apps — WhatsApp, Discord, Slack — instead of inside a project-management dashboard. Tickets, status changes, assignments, and asset attachments all flow through whichever surface the team is already using to coordinate, with a structured Notion store underneath as the system of record.

The core insight: most PM tooling assumes the team will come to a dashboard. PMOS assumes the dashboard comes to the team. The result is a CRM-shaped layer that lives where the work already happens, without forcing operators to context-switch into yet another tool.

How it works

• Notion as the source of truth — tickets, projects, people, and assignments live in a structured database that any team member can read directly.
• Messaging bridges as the input/output surface — WhatsApp, Discord, and Slack all hook into the same backend, so the team can update status from whichever channel they're in.
• Assistant layer — an LLM-driven agent answers questions about the current state (read-only) and writes structured updates back to Notion (audited, reversible).
• Audit trail and undo — every write the assistant performs is journaled and reversible from the same chat surface that triggered it.

Forks and adaptations

PMOS is built to be forked. The core ticket / messaging / assistant primitives stay the same; the domain layer (what tickets mean, what statuses are valid, what assets attach) gets reshaped per use case.

spoonbot — the Spoonerism music-label fork — was the first downstream adaptation. PMOS's generic project canvas was replaced with a Launch Board for releases, and the messaging surface narrowed to WhatsApp because that's where the label coordinates. Healthcare-CRO and clinical-trial coordination forks are next on the roadmap.