--- title: 'Flagridge: role harnesses that keep product work connected' description: 'Give each role a harness for its part of the work, and pass shared requirements, work packages and reviewable evidence to the next person in Flagridge.' url: 'https://flagridge.com/' type: 'page' template: 'home' language: 'en' --- # AI made everyone faster. Keeping the work together still falls on you. > Each role gets a harness for its part of the work. Shared requirements, work packages, and reviewable evidence help the next person continue without reconstructing the decisions from chat. Primary action: [Explore the harnesses](https://flagridge.com/platform) ## What Praxis is - **A harness for your role** — BA, Architect, Developer and Quality Harness guide distinct responsibilities. Choose the one that serves your current work. - **A connected contract** — accepted scope, a prepared package and evidence let the next person inspect the decision. - **A reviewable transition** — proposed canonical writes, Quality application and Git delivery each have their own approval boundary. - **A durable record** — versionable artifacts can live in your repository; local Runtime journals and cross-machine setup need their own handling. ## AI put an agent on every desk. It did not put them on the same team. AI makes a person faster at the task in front of them. The coordination cost remains when a requirement is accepted in one session, designed in another, and implemented against a ticket that omits the decision. Praxis gives each role an artifact the next owner can open. Review or rework can still send the package back; the method keeps that decision visible. ## Four role harnesses, one connected method. The delivered role chain is **Business Analyst → Architect → Developer → Quality Harness**. BA clarifies and accepts scope and creates the initial canonical work package. Architect enriches that same package with relevant technical decisions. Developer inspects the prepared input, implements a bounded change and records checks, failures and skips. Quality Harness reviews that particular result. Applying its findings and publishing through Git require their own approvals; a published PR or MR still awaits human review and merge. A separate private **Quality Platform** is planned to keep quality history within each project and provide oversight across multiple projects. That future history is not a claim that every current review creates a live trend. ## Install one role, or run the whole flow. - **Business Analyst** — make a raw request and its acceptance reviewable. [Read the BA guide](https://flagridge.com/docs/plugins/ba). - **Architect** — enrich accepted scope with the technical choices the selected change needs. [Read the Architect guide](https://flagridge.com/docs/plugins/architect). - **Developer** — check the package and repository context, implement, and return evidence. [Start in Claude Code CLI](https://flagridge.com/docs/getting-started/cli). - **Quality Harness** — inspect an individual result and preview any application. [Read the Quality guide](https://flagridge.com/docs/plugins/quality). Each package has its own distribution and prerequisites. Current workflows include Claude Code CLI and Claude Desktop/local Runtime paths; the [setup guide](https://flagridge.com/docs/) separates them. ## Developers become product engineers. A developer needs accepted intent and relevant design to own the resulting feature. The prepared package brings those links together, but its referenced files must be accessible in the code workspace. In a team setup, BA and Architect can share a product repository while Developer works in a code repository; transferring the prepared package is an explicit step. Runtime does not automatically sync a sibling checkout. ## Craft shifted to AI. Accountability didn't. Use the harness to expose what a person is deciding: proposed scope, technical tradeoffs, implementation evidence and Quality findings. A verdict reports a particular operation, including skipped checks where relevant. It does not imply that every build, test, lint or security check ran. Keep the working record available for the next role and explicitly stage the versionable parts you choose to publish. ## Your canon stays inspectable. The BA, Architect and Developer paths and a delivered Quality Harness have distinct package surfaces. The filesystem canon can be versioned in your Git repository; `.project` is its configuration file. The private Quality Platform is a separate product direction with access discussed in conversation. ## Built with the lifecycle, running in production. These cases describe product contexts, the method used there, and a result with the source of its number. They do not imply today's Runtime or private Platform was used historically. - **[Winery OS](https://flagridge.com/cases/digital-winery)** — Winery OS moved development to Praxis in March 2026. The group's VP of Engineering reports the team went from 18 people to 10 on the same volume of work. - **[WatchLink](https://flagridge.com/cases/watchlink)** — A luxury-watch community moved from a Facebook group of 4,000+ members to web, iOS, and Android apps of its own. Product analytics counted 2,041 registered accounts in the first month. ## Start growing products. Choose the responsibility you hold today. Begin with one accepted scope or prepared package, then bring the next role in when the work needs it. --- HTML: https://flagridge.com/ Markdown: https://flagridge.com/index.md