Validation coverage

TCAF 0.4.0 is a public pre-1.0 release. Validation is reported by scenario and transport rather than as a universal guarantee.

Core workflow acceptance

The v0.4.0 semantic BLACK_BOX acceptance evidence covers the following scenarios:

Core scenario	Status	What was exercised
Greenfield bootstrap from ordinary project material	PASS	Source documents were used without expert manual preprocessing and preserved as source evidence.
Existing-project adoption	PASS	Inspection-first adoption preserved the existing project while deriving only needed project state.
Feature planning	PASS	Broader work was decomposed into reviewable, dependency-aware planning without implementation.
Project sync	PASS	Current repository evidence was re-read and bounded reconciliation preserved developer changes and history.
Task Contract generation	PASS	A clean BLACK_BOX path produced the bounded authorization object required before implementation.
No expert chat preprocessing	PASS	Covered runs used the TCAF bundle plus project evidence without an expert manually restructuring the input in chat first.

These results support the covered workflows. They do not prove every model, repository, host, operating system or configuration.

Adapter and host coverage

Adapter validation is a separate question from the semantic core workflow:

Transport	Status	Current boundary
Codex native	Verified	Native Codex usage is part of the validated path.
Cline manual-envelope	Verified with limitations	The bounded manual-envelope procedure is verified.
Native Cline invocation	Not verified	Do not present native runner-to-Cline invocation as equivalent to the verified manual path.
Generic CLI / chat and broader combinations	Validation in progress	Framework support does not imply equal acceptance coverage across hosts and models.

What “verified” means

A verified scenario has executed evidence under documented conditions. It does not mean every possible environment has been tested.

The same evidence rule TCAF applies to software delivery is applied to TCAF itself: unsupported, pending or limited combinations remain visible instead of being turned into stronger claims.

Recommended first trial

1. install TCAF and run tcaf doctor;
2. start with bootstrap or adopt;
3. use plan only when the requested outcome is broader than one task;
4. run one bounded task;
5. verify the result before acceptance;
6. use sync when repository or project state changes outside the current run.

Return to the Quick Start to try TCAF now.