---
title: "About — Praxis"
route: "/about"
template: about
intent: "Explain Praxis as a product method before its company story."
primaryCta: { label: "Explore the platform", href: "/platform" }
description: "Praxis is an open method and toolchain for AI-native software delivery — four specialized role harnesses connected by shared artifacts, Core contracts and local Runtime tools."
schemaType: AboutPage
hero:
  eyebrow: "About"
  headline: "Praxis is a method and toolchain for keeping AI-assisted product work connected."
  sub: "Praxis is an open method and toolchain for AI-native software delivery — specialized role harnesses and a handoff you can inspect at each boundary."
  primaryCta: { label: "Explore the platform", href: "/platform" }
  secondaryCta: { label: "Book a demo", href: "/enterprise#contact" }
sections:
  - { id: product, kind: explanation, heading: "What Praxis is" }
  - { id: principles, kind: cards, heading: "Principles" }
  - { id: journey, kind: timeline, heading: "Our journey" }
  - { id: team, kind: explanation, heading: "Team" }
  - { id: contact, kind: cta, heading: "Contact" }
---

## What Praxis is

Praxis is a method and toolchain for keeping AI-assisted product work connected. BA clarifies scope and creates the initial canonical WP; Architect enriches it; Developer implements bounded scope; Quality Harness reviews the result. Core defines shared contracts, and Runtime supplies local tools for supported operations. The private Quality Platform is a separate planned product for history within and across projects.

## Principles

- **Start with one role** — choose the harness that matches the decision you own.
- **Make the next input inspectable** — accepted scope, selected design and evidence have named artifacts.
- **Approve the action in front of you** — canonical writes, Quality application and Git delivery have distinct boundaries.
- **Keep the record** — version the appropriate artifacts explicitly; local journals and cross-machine setup need separate handling.

## Our journey

The method has grown around real questions of intent, design, implementation and review. Current role and Runtime sources show those workflow surfaces; they do not establish a public launch chronology for every offering or a deployed multi-project dashboard.

## Team

Praxis is built by DFG's product and engineering team. The method is used to make product intent, decisions, implementation evidence, and human acceptance visible across delivery work.

## Contact

For a walkthrough, a rollout conversation, or a question about the method, reach out and book time with the team.

### Start here

Explore the platform or book a conversation to see the method against a delivery problem you recognize.