Operations Architecture: Domain Projection and Contracts

The Operations domain is not a separate application. It is a projection of Spine Fabric assembled on demand from shared entities, events, and evidence. The architecture is defined by contracts that specify which data the domain consumes, how it is shaped, and what capabilities it exposes.

Domain Contract

domain: operations
version: 1.2
owner: operations-team@integratewise.ai
entities:
  - name: Request
    sourceOfTruth: ServiceNow
    fields: [id, category, priority, status, submitterId, createdAt, slaDeadline]
  - name: Ticket
    sourceOfTruth: ServiceNow
    fields: [id, requestId, assigneeId, status, resolutionCategory, closedAt]
  - name: Asset
    sourceOfTruth: ServiceNow
    supplemental: [Google Workspace]
    fields: [id, type, serialNumber, assignedTo, location, refreshDate, status]
  - name: Vendor
    sourceOfTruth: ServiceNow
    supplemental: [Notion]
    fields: [id, name, riskTier, contractEndDate, primaryContact, status]
  - name: Policy
    sourceOfTruth: Notion
    fields: [id, title, scope, effectiveDate, reviewDate, ownerId]
  - name: Approval
    sourceOfTruth: ServiceNow
    fields: [id, requestId, approverId, decision, decidedAt, scope]
  - name: KPI
    sourceOfTruth: computed
    inputs: [ServiceNow, Jira]
    fields: [id, name, target, currentValue, frequency, alertThreshold]
events:
  - RequestCreated
  - TicketAssigned
  - AssetAssigned
  - VendorOnboarded
  - PolicyPublished
  - ApprovalDecided
  - KPIThresholdCrossed
views:
  - RequestQueue
  - AssetInventory
  - VendorPortfolio
  - ApprovalDashboard
  - KPISnapshot
capabilities:
  read: [ops.request.read, ops.asset.read, ops.vendor.read, ops.policy.read, ops.kpi.read]
  write: [ops.ticket.update, ops.asset.update, ops.vendor.update, ops.approval.submit, ops.approval.decide]
  communication: [ops.ticket.comment, ops.vendor.message, ops.broadcast.policy]
  workflow: [ops.workflow.requestFulfillment, ops.workflow.vendorOnboarding, ops.workflow.assetProvisioning, ops.workflow.approvalRouting, ops.workflow.kpiReview]

Architecture References

Domain Projection Architecture — how Spine Fabric projects shared entities into domain-specific views
Context Assembly Architecture — how entity graphs are built on demand from multiple sources
Agent Architecture — how Twin and domain agents observe, reason, and act within domain scope
Capability Architecture — how capabilities are defined, resolved, and audited across domains
Workflow Architecture — how multi-step workflows coordinate human and agent actions with receipts
Integration Architecture — how connectors ingest and write to source systems
Event Architecture — how events are normalized, routed, and replayed for consistency

The domain contract is versioned. Changes to entity schemas or capability lists must be reviewed by the domain owner and approved by the platform team.

Domains Overview

Account Success

Technical Account Success

Business Operations

Finance & RevOps

Sales

Marketing

Content

Service

Product Engineering

Personal

Human Resources

Legal

Support

Founder Ops

Operations

Operations Architecture: Domain Projection and Contracts

Domain Contract

Architecture References

​Domain Contract

​Architecture References

​Related

Domain Contract

Architecture References

Related