Bound the task
Turn a request into an explicit Task Contract before consequential implementation begins.

TCAF 0.4.0 · Public preview
Turn a request into an explicit Task Contract before consequential implementation begins.
The AI works with existing architecture, behavior and local patterns instead of expanding scope or rewriting opportunistically.
Executed checks, pending verification and limitations stay visible before the developer accepts the work.
Where TCAF fits
TCAF brings them together in one practical delivery workflow while developers retain authority over architecture, code and acceptance.
Specifications and repository evidence define what should be built.
Runtime, adapters, context and rules make AI execution repeatable across tools.
Planning, Task Contracts, sync, verification and approval keep consequential decisions developer-owned.
Inside one task
Developer defines the intended outcome.
TCAF makes scope, preservation and acceptance explicit.
The AI can execute the approved work inside that boundary.
Evidence is reported before developer acceptance.
The v0.4.0 workflow
tcaf bootstrapStart from ordinary project material and establish the minimum useful project state.
→tcaf adoptInspect the repository and adopt it without changing application code or history.
→tcaf planTurn a feature or outcome into a reviewable dependency-aware plan before implementation.
→tcaf taskPrepare one Task Contract, approve it, then execute and verify the requested delta.
→tcaf syncRe-read repository evidence and reconcile the smallest approved state update.
→Need the reasoning behind the workflow?
See how TCAF works →