---
title: "Praxis by role"
route: "/for"
description: "See Praxis from the role carrying the coordination cost in AI-assisted product delivery."
template: hub
intent: "Help a role owner recognize their delivery coordination problem."
primaryCta: { label: "Explore the platform", href: "/platform" }
schemaType: CollectionPage
hero:
  eyebrow: "By role"
  headline: "See Praxis from the role carrying the coordination cost."
  sub: "Each role can use one harness. The shared method matters when its output must become somebody else's reliable input."
  primaryCta: { label: "Explore the platform", href: "/platform" }
sections:
  - { id: founder, kind: cards, heading: "Founder / solo" }
  - { id: product, kind: cards, heading: "Head of Product" }
  - { id: engineering, kind: cards, heading: "Engineering Director" }
  - { id: developer, kind: cards, heading: "Developer" }
  - { id: quality, kind: cards, heading: "Quality Lead" }
---

## Founder / solo

You change roles in the same day. Keep the accepted output of one role openable by the next. [See the founder path](/for/founder)

## Head of Product

You need a requirement to arrive in engineering with its business rule and acceptance still attached. [See the product path](/for/head-of-product)

## Engineering Director

You need individual AI gains to become one delivery standard the team can follow. [See the engineering path](/for/engineering-director)

## Developer

You need a bounded package with decisions before you begin implementation. [See the developer path](/for/developer)

## Quality Lead

You need a Quality Harness review of a particular result, plus a separate planned private Platform for history within and across projects. [See the quality path](/for/quality-lead).