How it works
How YOC keeps recurring AI work maintainable
A Package defines a business scenario. Tasks divide it into independently queued, observed, and recoverable units.
Responsibility boundary
One Task, three clear responsibilities
- 01 Prepare Validate and deduplicate
- 02 AI Understand, judge, and generate
- 03 Complete Verify, save, and deliver
YOC is designed for defined recurring processes, not unconstrained autonomous exploration.
Lifecycle
From trigger to retained Run
A trigger creates a queued request. Admission creates a Run. The completed or failed Run keeps its result and Workspace for later diagnosis.
-
Schedule
Manual, one-time, recurring, CLI, and upstream triggers enter an explicit Queue.
-
Trace
Each Run retains inputs, events, logs, results, and its Workspace.
-
Recover
A failed Task can be diagnosed and rerun without overwriting earlier successful Runs.
Visible state
Waiting and running are different facts
Public Help