01
Understand
Sense reads the current project state, surrounding context, and relevant constraints before it suggests any action.
How It Works
How C turns intent into trusted change.
Sense understands the work in context, proposes a bounded move, keeps preview and approval in the loop, and updates history after every approved action.
Understand Preview Apply with trust
01
Understand
02
Scope
03
Preview
04
Apply
Trust Loop
A six-step contract keeps the workflow intelligible.
Trust breaks when any of these steps disappear.
02
Scope
The system proposes a bounded plan, not an unstructured wish. Intent and limits stay visible.
03
Preview
Teams inspect the likely result before the project changes, so quality stays reviewable.
04
Apply
Only approved change executes. The apply path is governed instead of improvised by the model.
05
Undo
Rollback remains fast and explicit, so experimentation does not destroy continuity.
06
Update context
After approved work lands, project truth and provenance update so the next action starts from reality.
Cross-surface handoff
The contract stays consistent as work moves across products.
StageGraph can turn a script into portable story context before the timeline is touched.
Studio can use that context to preview and apply semantic edits with the same review and rollback posture.
VPS can carry approved prompt and policy context into generative workflows without restarting from raw prompt text.
Why handoff matters
If context breaks between surfaces, you do not have a system. You have a stack of demos.
Why it stays trusted
The risky parts stay visible.
These controls are what separate useful automation from hidden state drift.
The user sees the proposed change before state mutates.
C does not ask teams to trust hidden edits after the fact.
The human stays inside the decision loop at the right point.
That is what keeps the workflow fast without surrendering accountability.
Recovery remains part of the normal workflow, not an exception.
The system is safer because rejection and reversal are cheap.
History explains what happened and why the work changed.
Trust compounds when evidence survives the action itself.
Walkthrough
See the contract in motion.
Open the public proof routes or request a guided walkthrough of how understand, scope, preview, apply, undo, and provenance show up in product.