Documentation

This documentation explains how to use TCAF as an operating framework for real software development—not as a replacement for engineering work and not as supervised vibe coding.

The developer or development team remains free to inspect, design, write, refactor, debug and modify the code directly. TCAF constrains what the AI may do autonomously inside a task; it does not constrain the developer’s authority over the software.

Start from your current goal

• Understand what TCAF is if you are evaluating the framework for the first time.
• See how TCAF works for the complete operating path from a request to reviewed evidence.
• Choose your path if you already know whether you are starting a project, adopting one or running a task.
• Install TCAF when you are ready to use the runtime locally.
• Read the workflow status guide before interpreting verified, framework-aligned or planned procedures.

What the documentation covers

The navigation follows the real lifecycle of AI-assisted software work:

1. install and verify the runtime;
2. understand Task Contracts and operating principles;
3. bootstrap a new project or adopt an existing one;
4. run bounded development tasks;
5. classify changes that appear during a task;
6. use a tool adapter without changing core TCAF behavior;
7. verify outcomes, reconcile project state and commit accepted work;
8. consult examples, references and troubleshooting guidance.

Two independent status dimensions

Every operational page distinguishes between:

• content status, which indicates whether the bilingual explanation is complete, draft or still represented by a placeholder;
• workflow status, which indicates how far the underlying procedure has been implemented and verified.

A complete page may document a workflow that is still framework-aligned or planned. Conversely, a verified workflow can temporarily have incomplete editorial coverage. These states are intentionally separate so the site never presents documentation completeness as proof of operational validation.

Version and naming conventions

The current documentation targets TCAF 0.3.3, a pre-1.0 draft.

The framework name is always written TCAF in prose. The lowercase form tcaf is reserved for the executable command, for example:

tcaf doctor
tcaf adopt --target <project-path>

No silent language fallback

English and Italian are maintained as explicit pairs. When a page has not yet received full editorial content, the requested language displays a declared placeholder rather than silently substituting the other language.

This makes missing work visible and keeps the documentation trustworthy while coverage expands section by section.