The proposed operator cycle
This four-step model is the product direction. The production cycle is not available yet.
Discover
The proposed cycle would gather approved signals to identify useful work.
Plan
It would turn those signals into a reviewable plan before execution.
Execute
Approved tasks would run only after the relevant controls pass validation.
Report
The proposed report would show evidence, spend, and pending decisions.
What we're building
A governed operator concept with human review, visible costs, and portability as design goals.
Daily Operator Cycle
A proposed discover, plan, execute, and report loop that is still under reliability testing.
Approval Inbox
A planned review point for financial, publishing, and irreversible actions.
Transparent Cost Ledger
A planned record of token use, external calls, and estimated spend for each cycle.
Portable & Open-Core
Portability and operator ownership remain product goals; export is not available yet.
Specialist Workers
The product direction includes focused workers for research, growth, support, and reporting.
Guardrails & Policies
Approval gates and policy controls are being validated before the operator becomes available.