# Praxis > Praxis by DFG: a method and toolchain for keeping AI-assisted product work connected — four role harnesses (BA, Architect, Developer, Quality) with reviewable handoffs. Language: en. Every page is available as Markdown at its URL plus `.md`; the full text is at https://flagridge.com/llms-full.txt. ## about - [About Flagridge: a method and toolchain for connected work](https://flagridge.com/about.md): What Flagridge is: an open method and toolchain that keeps AI-assisted product work connected through role harnesses, shared Core contracts and named artifacts. ## blog-index - [Blog — Flagridge](https://flagridge.com/blog.md): The Flagridge blog: notes on building software with AI agents with a person on every irreversible decision. ## blog-post - [Code is no longer the bottleneck. Deciding what to build is. — Flagridge](https://flagridge.com/blog/bottleneck-moves-to-requirements.md): Agents can already write code around the clock. To use it, a team needs a steady flow of requirements, which product engineers give; the next bottleneck is quality, which platform engineers widen. - [What Flagridge is: a runtime for Claude Code, Codex and OpenCode — Flagridge](https://flagridge.com/blog/what-flagridge-is.md): Flagridge is not another coding agent. It is the soft harness that gives Claude Code a correct runtime, with Codex and OpenCode coming soon. - [Back to one role: who a product engineer is — Flagridge](https://flagridge.com/blog/who-is-product-engineer.md): The developer role made one more turn of the spiral. Implementation moved to agents, so one person can own a whole product capability again. We call that person a product engineer. ## case-index - [Case studies: product contexts, method and sourced results](https://flagridge.com/cases.md): Read two product contexts, Digital Winery and WatchLink, with the working context, the method used, the result and the source behind every number reported. ## case-detail - [Digital Winery case study: changes traced to requests](https://flagridge.com/cases/digital-winery.md): See how development of a winemaking platform moved onto the method in March 2026, with its context, challenge and how every change traces to a change request. - [WatchLink case study: from a Facebook group to its own apps](https://flagridge.com/cases/watchlink.md): Follow a luxury-watch community from a Facebook group of 4,000+ members to web, iOS and Android apps of its own, with 2,041 accounts registered in month one. ## changelog - [Changelog: role harness and local Runtime changes by release](https://flagridge.com/changelog.md): Follow dated updates to the role harnesses and local Runtime, from the alpha.49 guided workflow back to the source snapshot, with links to the release notes. ## size - [Flagridge for enterprise: one shared delivery process](https://flagridge.com/enterprise.md): Give every delivery team one way to work with AI: shared artifact contract across roles, distinct approvals and a chain from accepted scope to evidence. - [For startups: let a small team change roles with context](https://flagridge.com/startups.md): Let a small team move between product, design and code with the request, technical choices and implementation evidence kept openable as the team grows. ## hub - [Solutions by role: who carries the coordination cost](https://flagridge.com/for.md): See the method from the role you hold, from founder to quality lead, and where each one carries the cost of coordinating AI-assisted work across roles. - [Solutions: find a path by situation, role or quality job](https://flagridge.com/solutions.md): Choose a path by delivery situation, by the role carrying the cost, or by the quality job that needs a shared flow, from code review to security. - [Solutions by situation: start where the work breaks down](https://flagridge.com/solutions/by-stage.md): Pick the moment that repeats in your delivery week, from starting a product to a recent launch to team delivery, and begin with the role harness that fits it. ## role - [For developers: start coding with decisions attached](https://flagridge.com/for/developer.md): Start coding with the decisions attached: a resolved package of requirement, design, contracts and budgets, closed by a record of the checks that actually ran. - [For engineering directors: one delivery process for the team](https://flagridge.com/for/engineering-director.md): For engineering directors: turn individual AI speed into one shared delivery process, with versioned handoffs in git, human gates and evidence per requirement. - [For founders: change roles without losing decisions](https://flagridge.com/for/founder.md): Move from product to architecture to code in a day without rebuilding earlier reasoning: accepted requirements, explicit decisions and evidence in one flow. - [For heads of product: keep a requirement intact at handoff](https://flagridge.com/for/head-of-product.md): Keep a requirement's business rule and acceptance attached as it reaches engineering, with links to affected stories and decisions before a change is built. - [For quality leads: see quality drift before it settles in](https://flagridge.com/for/quality-lead.md): Review one result with the Quality Harness, read the failures and skipped checks, and see where a planned private Platform would track drift across projects. ## home - [Flagridge: role harnesses that keep product work connected](https://flagridge.com/index.md): 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. ## platform-overview - [Flagridge platform: four role harnesses, one method](https://flagridge.com/platform.md): See how four role harnesses, shared Core contracts and local Runtime tools pass named artifacts and reviewable decisions from Business Analyst to Quality. ## platform-component - [Architect harness: from requirements to bounded decisions](https://flagridge.com/platform/architect.md): Turn a work package into decisions, contracts and measurable NFR budgets, and prepare a design package a Developer can build from without guessing intent. - [Business Analyst harness: from request to accepted scope](https://flagridge.com/platform/ba.md): Turn a change request, feature or bug report into typed, traceable requirements and a work package, with scope approved by a person before anything is written. - [Developer harness: from bounded package to verified change](https://flagridge.com/platform/developer.md): Inspect a prepared package, research what the change touches, implement bounded scope and record evidence, including skipped checks, for a reviewer to inspect. ## quality-platform - [Quality Harness: review one work result against evidence](https://flagridge.com/platform/quality.md): Learn what the Quality Harness does for one work result, from checks to a verdict backed by evidence, and where the planned Quality Platform keeps history. ## release-index - [Release notes: what changed in each Flagridge release](https://flagridge.com/releases.md): Read what changed in each published release, how to install or upgrade it and what is still unverified, starting with 0.1.0-alpha.49 of Flagridge. ## release - [Flagridge alpha.49: guided workflow, prototypes, evidence](https://flagridge.com/releases/alpha-49.md): See what alpha.49 adds: a guided workflow with review gates, interactive prototypes, structured requirement and story reviews, Quality verdicts with evidence. ## roadmap - [Roadmap: shipped, in preview and next across the harnesses](https://flagridge.com/roadmap.md): See what the current Flagridge source snapshot contains, the directional next work on setup, packages and evidence, and the private Quality Platform direction. ## situation - [After launch: change a product and keep its decisions](https://flagridge.com/solutions/by-stage/after-launch.md): Trace which requirements, decisions and contracts a change affects before implementation starts, so each request builds on accepted behavior, not chat memory. - [Starting a product: make the requirement buildable first](https://flagridge.com/solutions/by-stage/starting-a-product.md): Settle the business rule, acceptance and scope before code runs ahead: the BA harness clarifies the request and creates the first canonical work package. - [Team delivery: move one work package across every role](https://flagridge.com/solutions/by-stage/team-delivery.md): Turn each role's output into the next role's governed input: one work package moves from BA through Architect and Developer to a Quality review. ## solution - [Code review against intent: check each change beyond syntax](https://flagridge.com/solutions/code-review.md): Check a generated change against its accepted requirement, its design constraint and the checks that actually ran, instead of rebuilding intent from a diff. - [Legacy Upgrade: modernize code without guessing behavior](https://flagridge.com/solutions/legacy-upgrade.md): Modernize legacy code without a rewrite: inspect one seam, confirm uncertain business intent, move one bounded package with test evidence and remaining risks. - [Quality drift review: find debt hidden behind green merges](https://flagridge.com/solutions/quality-drift.md): See why quality drift needs repeated, comparable observations against a default-branch baseline, and how debt that builds up after green merges is measured. - [Security review: keep checks attached to the change itself](https://flagridge.com/solutions/security.md): Start from a specific security constraint, run the configured checks and show the evidence and gaps a reviewer needs, so review stays attached to the change. ## Docs - [Documentation](https://flagridge.com/docs/) - [Sitemap](https://flagridge.com/sitemap-index.xml)