> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spineworkspace.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Account Success Execution Flow: From Intent to Source Write

> The complete Execution Path for Account Success actions from intent through capability resolution to source system write-back and continuity.

The Account Success Execution Flow describes how intentions become governed actions that update source systems and produce receipts. This is the Execution Path applied to customer lifecycle operations.

<Steps>
  <Step title="Intent">
    A CSM or agent identifies a need: update a renewal opportunity, escalate an at-risk account, or schedule a QBR. Intent is expressed through the UI or inferred by Twin from signals.
  </Step>

  <Step title="Context">
    Spine Fabric assembles the full context for the target account: entities, relationships, recent events, and authorization scope. Context validation prevents actions on unassigned accounts.
  </Step>

  <Step title="Decision">
    Twin or the CSM selects the action from available capabilities. The system validates that the actor has the required authorization for the target entity and capability.
  </Step>

  <Step title="Proposal">
    For complex actions, Twin generates a proposal with expected changes, affected systems, and side effects. The CSM reviews before confirmation.
  </Step>

  <Step title="Capability Resolution">
    The action maps to a governed capability: `salesforce.opportunity.update`, `zendesk.ticket.create`, or `workflow.escalation.trigger`. Scope is enforced at resolution time.
  </Step>

  <Step title="Handoff">
    If the action spans multiple systems or teams, Twin coordinates the handoff. Escalations notify managers. Renewals involve sales. QBRs schedule with calendars.
  </Step>

  <Step title="Tool Selection">
    Spine Fabric selects the appropriate connector: Salesforce REST API, Zendesk API, HubSpot API, or email/calendar integrations.
  </Step>

  <Step title="MCP/Connector">
    The connector translates the capability into a native API call with proper authentication, field mapping, and error handling.
  </Step>

  <Step title="Authorization">
    Final authorization check validates the connector token, user permissions, and entity scope before the API call executes.
  </Step>

  <Step title="Human Approval">
    High-impact actions require explicit approval: pricing changes, contract amendments, health score overrides. Approval requests route to defined approvers.
  </Step>

  <Step title="Workflow Execution">
    The API call executes. For workflow capabilities, multiple steps may run in sequence with intermediate validation.
  </Step>

  <Step title="Source-System Write">
    The target system records the change. Salesforce updates the opportunity. Zendesk creates the ticket. The source system returns a confirmation.
  </Step>

  <Step title="Receipt">
    Spine Fabric records a receipt: actor, capability, target, timestamp, outcome, and source-system reference. Receipts are visible in the account timeline.
  </Step>

  <Step title="Event">
    A domain event is emitted: OpportunityUpdated, TicketCreated, or EscalationInitiated. Other agents and views react to the event.
  </Step>

  <Step title="Continuation">
    Session state updates with the completed action and any pending follow-ups. Continuity ensures the next session or handoff resumes seamlessly.
  </Step>
</Steps>

## Related

* [Account Success Index](/internal-docs/domains/account-success/index)
* [Workflows](/internal-docs/domains/account-success/workflows)
* [Capabilities](/internal-docs/domains/account-success/capabilities)
* [System Flow](/internal-docs/domains/account-success/system-flow)
* [Governed Actions](/how-it-works/governed-actions)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.