States and outcomes

TCAF uses separate vocabularies for documentation completeness, workflow maturity, implementation state and final outcome. They must not be collapsed into one badge or interpreted as equivalent.

Documentation content status

• complete — the bilingual page contains the intended editorial explanation for the current release.
• draft — useful content exists but still requires editorial or technical completion.
• placeholder — the route exists, but the full page is still in preparation.

A complete page can describe an unverified or planned workflow. Editorial completeness is not implementation maturity.

Workflow status

• verified — exercised with recorded evidence in the current framework work.
• verified-with-limitations — exercised successfully, with host, coverage or transport limitations that remain material.
• framework-aligned — defined consistently with TCAF rules but not yet exercised across the documented scenario.
• documentation-in-progress — workflow evidence exists while its public explanation is still being prepared.
• planned — intended capability or integration not yet available as a verified workflow.
• not-supported — TCAF intentionally does not perform the operation automatically or without separate authorization.
• no workflow status — informational page rather than an executable workflow.

Implementation state

A task report can use:

• IMPLEMENTED — the contracted change is present, but verification may still be pending;
• VERIFICATION_PENDING — required developer, manual or CI checks remain;
• VERIFIED — required declared checks have completed successfully.

These states do not imply developer acceptance or commit.

Outcome labels

• PASS — contracted result is present and every required check already run has passed.
• READY FOR CHECK — implementation is present and a declared developer or manual verification remains.
• PARTIAL — only part of the contract is satisfied; completed and remaining work must be identified.
• BLOCKED — a contradiction, missing decision or unavailable requirement prevents safe continuation.
• FAIL — a required check failed; preserve the bounded state for review.

Never report PASS while a mandatory check is pending.

Active-task classifications

New information during implementation is classified as:

• clarification;
• correction;
• local adaptation;
• amendment required;
• separate task;
• blocker.

The classification determines whether work may continue, requires reporting, or must stop for developer approval.