# Product ## Platform web ## Users Software teams planning changes in GitHub repositories. ## Product Purpose Chopin gives a team one shared planning space: an MDX document, a visible conversation, and a repository-aware agent. Success is a durable, collectively owned plan that can guide implementation. ## Positioning The agent can inspect the selected repository while the team writes and retains the decisions in the same collaborative plan; it informs decisions without owning them. ## Operating Context Teams sign in with GitHub, select an authorized repository, create planning channels, and collaborate in real time while preparing work against an existing codebase. ## Capabilities and Constraints - GitHub App authentication and repository-scoped authorization are product boundaries. - Multiple people can edit one MDX plan with presence and cursors. - The agent acts only when explicitly addressed and has repository-scoped read access. - Plans and their supporting decision state are durable. ## Brand Commitments The product is named Chopin. Its existing interface is light-only, precise, and restrained; product decisions and collaboration should remain legible and attributable. ## Evidence on Hand The repository contains a runnable web application, its collaborative editor, UI source, and technical documentation. No external customer evidence, testimonials, or marketing claims are on hand. ## Product Principles - Keep the team in control of decisions. - Ground planning in the real repository. - Make shared work visible, attributable, and durable. - Treat repository access and document validity as non-negotiable boundaries.