ambacti
Explore workflows

ASSISTANT GUIDELINE REVIEW · Workflow idea

Adapt an assistant’s working guidelines without losing oversight.

Collect clear requests for how an assistant should respond in future conversations and present them as proposed working guidelines. Keep the current and proposed wording visible together, check each request for conflicts and unintended effects, and require an authorized owner to approve exact changes before they are adopted.

Make it yours See how it works ↓
A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
A request to change future behavior is made
Produces
A proposed guideline with its requester, purpose, current wording, review notes, and approval status.
Category
Reviews & approvals

01 / The starting point

A clear request.
A useful direction.

A suggestion from an authorized user about how an assistant should handle a defined type of request

“Prepare proposed assistant guidelines for review and require human approval before a lasting change is applied.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps teams capture and review behavior preferences so an assistant can better fit a defined task and audience.

  1. Capture the requested behavior

    Record what the requester wants to change, when the preference should apply, and the problem it is meant to solve.

  2. Prepare clear proposed wording

    Turn the request into a specific guideline that can be understood and reviewed without broadening its intended scope.

  3. Check for conflicts and unintended effects

    Compare the proposal with existing guidance, safety boundaries, privacy expectations, and the needs of other users.

  4. Review the proposed change with its owner

    Show the current and proposed guidance together and explain who or what future interactions could be affected.

  5. Approve before changing future behavior

    Require an authorized owner to approve the exact wording, purpose, and scope before a guideline is adopted or removed.

03 / The result

Something useful.
Something to build on.

A proposed guideline with its requester, purpose, current wording, review notes, and approval status.

AmbactiWorkflow folio · 5 steps

Review assistant guideline changes

Reviews & approvals · Example outcome

The handoff

A proposed guideline with its requester, purpose, current wording, review notes, and approval status.

Keep in mind

A user request may conflict with policy, create unsafe behavior, or affect future users beyond its original context. Keep changes limited to approved purposes, check for conflicts and sensitive information, and do not let a suggestion take effect by itself. An authorized owner must approve the exact guideline and its scope before it changes future responses.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Define who may suggest changes

Choose eligible requesters and describe which kinds of task preferences may be proposed.

Set guideline boundaries

Document policies and safety rules that a preference cannot override, along with how conflicting requests are handled.

Keep proposals and decisions traceable

Record the requester, reason, exact proposed wording, reviewer, and approval status with appropriate access limits.

Assign a guideline owner

Name who reviews scope and conflicts and approves each exact change before it affects future responses.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗