> ## 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.

# Technical Account Success Business Context: Entities and Events

> The core business entities, relationships, events, and evidence types powering Technical Account Success context assembly within Spine Fabric.

The Technical Account Success business context defines the semantic layer that Spine Fabric uses to assemble technical meaning from raw source data. These entities and relationships form the basis for health scoring, workflow triggers, and AI reasoning.

## Entities

| Entity | Key Attributes | Identity Source |
| - | - | - |
| TechnicalAccount | environment, tier, region, deployment\_type | Salesforce |
| SystemArchitecture | diagram, decisions, stack, standards\_compliance | Documentation, Jira |
| Integration | system, version, config, health\_status, last\_sync | API gateways, Datadog |
| Implementation | milestones, status, owner, target\_date, completion\_criteria | Jira, Salesforce |
| TechnicalIssue | severity, category, status, engineering\_assignment | Zendesk, Jira |
| HealthScore | score, components, trend, computed\_at | Spine Fabric computed |
| APIUsage | requests, errors, latency, quota, endpoints | API gateway logs |
| TechnicalDebt | description, severity, remediation\_effort, age | GitHub, Jira, docs |

## Relationships

* A **TechnicalAccount** has one **SystemArchitecture** and may have many **Integrations**
* An **Implementation** belongs to one **TechnicalAccount** and tracks progress via milestones
* A **TechnicalIssue** may reference a **TechnicalAccount**, **Integration**, or **Implementation**
* **APIUsage** is associated with a **TechnicalAccount** and may indicate **Integration** health
* **TechnicalDebt** is linked to a **TechnicalAccount** and may block **Implementation** completion

## Key Events

| Event | Source | Trigger |
| - | - | - |
| HealthScoreChanged | Spine Fabric | Integration error rate or API latency crosses threshold |
| IntegrationFailure | Datadog/API gateway | Health check fails or error rate exceeds limit |
| MilestoneReached | Jira | Implementation milestone criteria satisfied |
| TechnicalEscalationCreated | Zendesk/Jira | Issue priority raised to high or urgent |
| ArchitectureReviewDue | Documentation/Jira | Scheduled review date within 30 days |
| APIQuotaThreshold | API gateway | Usage exceeds 80% of allocated quota |

## Evidence Types

* **Monitoring:** Uptime metrics, error rates, latency distributions from Datadog and APM tools
* **Code:** Repository status, deployment history, configuration changes from GitHub
* **Ticketing:** Support interactions, bug reports, engineering assignments from Zendesk and Jira
* **Documentation:** Architecture decisions, runbooks, and technical debt registers
* **API Telemetry:** Request volumes, response codes, and quota consumption from gateways

## Related

* [Technical Account Success Index](/internal-docs/domains/technical-account-success/index)
* [Domain Views](/internal-docs/domains/technical-account-success/domain-views)
* [Spine Fabric](/internal-docs/domains/technical-account-success/spine-fabric)
* [Agents](/internal-docs/domains/technical-account-success/agents)
* [Events and Continuity](/how-it-works/continuity)


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