Purpose

These are the standard cross-database workflows that agents should follow when operating across the Tentacles OS Layer. Each template describes the trigger, the step-by-step sequence of database operations, and the expected end state. Agents should reference these templates as patterns — not rigid scripts — and adapt as needed.

For the exact JSON payloads, see the Agent Interface Spec.

Workflow 1: New Client Request → Ticket → Tasks

Trigger: A client or account manager submits a request (via human, email, Slack, or agent detection).

When to use: Any time work needs to happen for a client engagement.

Steps:

1. Create a ticket in 🎫 Tickets
   • Set Project Code to the client's engagement code (e.g., {CLIENT}-{TYPE})
   • Set Title, Description, Priority
   • Set Source (Human, Agent, Email, or Slack)
   • Link Related Client to the client record
   • Link Related Engagement to the active engagement
   • Serialized ID auto-generates (e.g., {CLIENT}-{TYPE}-005)
2. Triage the ticket — update Status from New to Triaged
   • Assign to a team member if known
   • Set Due Date if applicable
3. Spawn tasks in ✅ Tasks for each unit of work
   • Link each task back via Source Ticket relation
   • Link to the same Related Engagement
   • Set Task Type, Priority, Sprint, Effort Estimate
   • Example: A single ticket "Migrate CRM data" might spawn 3 tasks: "Export legacy data", "Transform and normalize", "Load into RAG pipeline"
4. Update ticket status as tasks progress
   • Triaged → In Progress when first task starts
   • Blocked if a dependency stalls
   • Done when all spawned tasks are complete
5. Add a summary comment to the ticket when done
   • What was accomplished, any issues found, links to outputs

End state: Ticket is Done. All spawned tasks are Done. Client engagement has an audit trail of what was requested and what was delivered.

Workflow 2: Initiative Approval → Project + Tickets

Trigger: An initiative in 🚀 Initiatives moves from Approved to In Progress.

When to use: When a strategic initiative gets the green light and needs to be operationalized.

Steps:

1. Update the initiative status to In Progress in 🚀 Initiatives