Enough context to understand.
Read access can be wider than the scope of changes the agent may propose.
Latchboard / Operator console & reference interface
Review AI-proposed changes
before they reach your app’s records.
Let AI see enough to be useful, keep its proposals inside temporary scope, and make the boundary visible to the operator.
Knowledge does not
create permission.
The portable interaction model makes what an agent can see, propose, and execute explicit. The enterprise control core stays separate from the interface.
Only the delegated work.
Temporary scope has an identity and lifetime. A proposal stays tied to the state the agent actually saw.
Turn a suggestion into authority.
A plausible proposal does not commit itself. Stale or revoked work needs review before it can move forward.
Understand / Explore
The workflow
- Propose. AI prepares changes within the work the user has delegated.
- Review. The user inspects each proposed edit and decides what to accept.
- Check freshness. If the underlying record has changed, the old proposal needs a fresh review.
- End delegation. Stop accepting proposals under that delegation.
Inspect what the demonstration establishes
A working review-workflow demonstration using example task records handles stale proposals, ended delegation, and repeated review attempts within that task-state workflow.
It does not establish authenticated approvals, production security, control over external actions, or DVS production readiness. Its enterprise role is the operator console/reference interface. The generalized control-plane core, release checks, and enterprise adapters remain separate architectural components.
Portable principles for the enterprise interface
- Give access and proposal scope separate boundaries.
- Make delegation temporary, explicit, and revocable.
- Bind each proposal to the state that informed it.
- Do not recycle an earlier delegation’s authority into a new one.
- Apply a review decision only once on its controlled path.
- Reject a conflicting update instead of silently overwriting newer work.
These describe the intended interaction contract. Coverage in an enterprise system depends on its actual integration and observed results.
Inspect the reference evidenceVerify / Inspect
Reviewing a proposal and controlling its effect are different jobs.
Explore release authority with DVS ↗Build with unFragged
Bring one workflow. Build the evidence together.
Establish the strongest competent baseline. Integrate where a residual control gap remains. Measure the delta. Keep a clean negative result if the existing stack already solves it.
Partner with unFragged