Skip to main content
The Business Operations domain is a projection of the Spine Fabric. It does not store its own copy of process, approval, or vendor data. Instead, the Fabric ingests from source systems, unifies entities and events, assembles dossiers on demand, and projects them into the BizOps workbench. Sources and scopes:
  • Google Workspace: policy docs, approval forms, org directory.
  • Asana: projects, tasks, milestones, and workflow state.
  • Notion: knowledge base, vendor records, contract pages, OKRs.
  • Linear: engineering-linked initiatives and workflow issues.
  • HRIS: org structure, approver hierarchies, policy attestations.
  • ERP: vendor master, spend transactions, contract records.
Event sequence:
  1. Intake: connectors poll or receive webhooks when records change.
  2. Normalize: each record is mapped to a canonical schema.
  3. Resolve: entity linking matches vendors, contracts, and people across systems.
  4. Assemble: the Fabric builds contextual dossiers by traversing relationships.
  5. Project: authorized views are rendered into the BizOps workbench in real time.
When an approval is requested in Google Workspace, the Fabric resolves the requester in HRIS, finds the relevant policy in Notion, locates related vendor and contract context in ERP, and presents a single contextual dossier in the Pending Approvals view. When the approval resolves, the Fabric writes the outcome back to the source system and emits a receipt event. Related