Project Phoenix

Domain Analysis Interface Framework

Built on tau-bench (MIT License, Sierra Research)

Purpose

Project Phoenix explains how deterministic expert systems are built, validated, and deployed across production domains. It is an expert system framework, not a language model runtime.

Tagline: Domain Analysis Interface Framework built on Tau-Bench.

Lineage

Tau-Bench (MIT, Sierra Research) -> open-source agent evaluation framework -> SOP -> Tools -> Tasks architecture -> Project Phoenix -> production interface framework -> CLI, GUI, Agentic Cockpit -> Foundation + Four Operational Phases -> Phoenix Principles (including HITL Gate)

Key Stats

16 Domains

Production implementations across finance, sports, fitness, education, healthcare, and manufacturing.

710 Tools

Deterministic tool registry spanning all domain systems.

Six Phoenix Principles

From Write-Then-Verify to the Human-in-the-Loop gate for controlled progression.

Quick Navigation

Home

Return to the overview page and key framing of Project Phoenix.

Open Home

Philosophy

Why Phoenix is an expert system framework, not an LLM runtime.

Open Philosophy

Four Phases

Foundation stage plus four operational phases for execution control.

Open Four Phases

Principles

Six Phoenix principles, including HITL as a binding gate after V4.

Open Principles

Tau-Bench

Research grounding and challenge-to-solution mapping for Phoenix.

Open Tau-Bench

Domains

Production domain coverage and links to implementation areas.

Open Domains

Architecture

Project structure, execution modes, and deterministic runtime layout.

Open Architecture

White Paper

Canonical PDF describing framework rationale, design, and validation.

Open White Paper

Purpose

Jump directly to the purpose statement for quick context.

Go to Purpose