# Roadmap

## Phase 1 — Charter-first public repository

Goal:
- publish AITP as a charter-and-protocol repository rather than a vague kernel.

Deliverables:
- rewritten README,
- charter doc,
- agent model doc,
- context-loading guidance,
- adapter installation docs.

## Phase 2 — Public contract family

Goal:
- define the first stable protocol objects.

Deliverables:
- contract docs,
- JSON schemas,
- public conformance vocabulary,
- promotion and validation object boundaries.

## Phase 3 — Reference adapters

Goal:
- make AITP executable across multiple agent front-ends.

Deliverables:
- OpenClaw adapter assets,
- Codex adapter assets,
- Claude Code adapter assets,
- OpenCode adapter assets,
- unified install and uninstall guidance.

## Phase 4 — Reference runtime boundary

Goal:
- clarify what the public runtime is allowed to do.

Deliverables:
- runtime boundary docs,
- audit surface description,
- explicit line between protocol logic and implementation logic.

## Phase 5 — Worked benchmark cases

Goal:
- show that AITP is not only philosophical prose.

Target cases:
- literature-to-knowledge,
- idea evaluation,
- theory-to-numerics,
- theory-to-formalization,
- closed-loop research record.

## Phase 6 — Decision Points, Traces, and Lightweight Runtime

Goal:
- harden the operator-facing runtime so AITP can ask questions, preserve
  causal traces, and run with a smaller viable shell.

Deliverables:
- decision point protocol plus schema,
- decision trace protocol plus schema,
- session chronicle protocol plus schema,
- clarification loop guidance for vague idea-first starts,
- lightweight runtime conformance profile,
- git-level schema validation for critical runtime artifacts.

## Guiding constraint

The repository should become stricter before it becomes broader.
