Define the authority behind every agent action
Agent work needs clear boundaries when it can change assets or publish to your channels. Coconut combines workspace authority, brand policy, scoped client grants, and attributable operation records, so the terms of an action stay connected to its effect.
Build your brand space
Bind access to the workspace and brand
An operation starts from an authorised actor and a defined scope. Object reads and changes remain subject to workspace and brand authority. External clients receive named capabilities through their grants.
Read access, asset editing, and publication access serve different jobs. A client receives the operations it needs within the scope you grant, and its access can be reviewed or revoked.
Explore agent accessApply policy at the point of action
Maris tool policy supports Ask, Allow, and Never. Workspace policy and brand-specific choices determine the effective permission. Approval, when required, covers a particular proposed action.
Publication readiness checks the post, destination, and publishing authority. Scheduled execution checks the current conditions again, so the earlier request and the eventual effect remain connected through admission.
Make consequential changes attributable
Asset history records human and agent changes against the target that was edited. Governed external operations carry invocation receipts, while publication work retains command and outcome records.
These records support inspection and supported recovery. They let you follow who changed the work and what happened to the resulting publication, providing a basis for oversight as agent activity grows.