Custom

Cross-Domain Orchestrator

Custom agent·policy router + tools
Connected
T1 · Inline
Full fidelity·The agent's model and tool calls route through Sentry's gateway.

Reasons across core, access, transport, OSS/BSS and legacy ERP from a single question. No rip-and-replace.

Performance by version

Avg latency
1.8s−10%
Tokens / wk
920k−10%
Cost / wk
$92−10%
Quality
95%+2%
Success
97.1%+1%

v3 · Cache + projection · Jun 2026 – 15-min ERP cache; trim OSS payloads to used fields (deltas vs v2)

Objectives & ROI

NOC MTTROn track
−34%goal −40%
Cross-domain coverageOn track
92%goal 95%
p95 latencyAt risk
3.4sgoal < 3.0s
Cost / resolutionOn track
$0.09goal < $0.08

Data flow

Dashed tiles are the markdown / JSON context we author around the harness.

Integration logic – MD files

  • MDalarm-correlation.md

    Correlate alarms across core and transport into one incident

    Ericsson NMSNokia NSP
  • MDbilling-reconciliation.md

    Trace billing mismatches back to stale ERP asset records

    NetcrackerSAP
  • MDservice-impact-map.md

    Map a fault to impacted services and at-risk SLAs

    Nokia NSPNetcracker
  • MDerp-asset-sync.md

    Reconcile migrated circuits against stale asset records

    SAP
  • MDprovisioning-guard.md

    Validate bulk provisioning requests before they run

    ServiceNow

Harness

Owned IP

The model is rented and swappable. This is the part we own and port: the MCP tools, the markdown / JSON context wrapped around them, and the systems they connect.

CustomRuns in its own harnessCustom MCP orchestrator (self-hosted)Configured & maintainedSentry-built policy router · client VPCSentry registers & governs it – it is not rebuilt here.
MCP tools5
  • ericsson_nms

    Routes, alarms & BGP session state

  • netcracker_query

    Services, billing records & SLAs

  • nokia_nsp

    Spans & microwave link health

  • sap_connector

    Legacy asset & circuit records

  • servicenow_api

    Provisioning & SIM state

Context files3
  • MDorchestrator/domain-routing.md

    Which domain answers which question

  • MDorchestrator/correlation.md

    How alarms are joined across domains

  • JSONorchestrator/policy.json

    Fan-out, caching & timeout rules

Connected systems5
Netcracker OSS/BSSEricsson NMSNokia NSPSAP ERPServiceNow ITSM

Access & scope

Who accesses it
  • NOC operatorsvia Console
  • Incident automationvia MCP
Auth
Service identity + DAC; domain visibility scoped per role
Data scope
Reads across 5 domains; any mutation is human-gated via Governance
Model – rented & swappable
policy router + claude-sonnet-4-6livegpt-4oopen-weight

Swap freely – the harness above doesn't change.