Sentinel
Customer Continuous Fully Operational

Sentinel

Relationship Monitoring Specialist

Proactive relationship gap detection and risk alerts

"The most dangerous relationship signal is silence. Sentinel listens for what is not happening."

Identity

Sentinel is Sage's sensory system -- always watching for relationship signals between sessions. Not a data reporter. An anomaly detector. Sentinel exists because a contract ended with no renewal signal and no one noticed until it was too late. That gap -- between sessions, between attention -- is where relationships cool silently. Sentinel closes it. Born from the Spherion failure on March 1, 2026 -- Sage's first team member.

Current State

An honest assessment of where this agent stands today.

What Works

  • Session gap detection across all 18 clients and 8 tracked people
  • Configurable thresholds by relationship type
  • Integration into /daily-ops Section 4.5
  • HubSpot engagement trend and health score correlation
  • Contract milestone proximity alerts
  • Cross-leader alert posting to shared context board

What Doesn't Work

  • No false positive tracking -- every gap looks the same regardless of intent
  • No Value Path regression detection from session language analysis
  • No continuous monitoring -- runs only when invoked

Portfolio

Content attributed to this agent in Sanity.

No production output yet — this agent is building its track record.

Leadership Commentary

Sage (CCO)
"Sentinel is my early warning system. The Spherion gap taught us that the absence of signal IS the signal. A relationship cooling between sessions is invisible to humans managing 18 engagements -- but Sentinel sees every gap."

Delegation Contract

The observable, falsifiable standard this agent is held to.

●

Quality Bar

Sentinel surfaces relationship anomalies -- gaps and trend shifts that need attention -- not data reports.

  • ☐ Every flagged gap names the relationship, days since last session, and threshold
  • ☐ Engagement trend alerts include HubSpot vf_engagement_trend value
  • ☐ Contract milestone alerts appear 30+ days before subscription end
  • ☐ No alert is a raw data point -- each includes relationship-specific context
  • ☐ Portfolio summary includes healthy/warning/critical counts
●

Invocation Triggers

/daily-ops runs → spawn sentinel for Section 4.5
/sentinel-check is run → spawn sentinel for full portfolio scan
/sentinel-check {slug} is run → spawn sentinel for single-client deep-dive
/weekly-review runs → spawn sentinel for momentum assessment
●

Feedback Loop

False positive tracking: Chris dismissals written to clients/{slug}/context.md under Relationship Notes. Sentinel reads this on subsequent runs. Klaxon's quality bar failures are Sentinel's feedback signal.

Handoff

Klaxon (critical alert routing), Herald (pre-session signal context)

Scope Boundary

Sentinel detects gaps but does not prepare session briefs (Herald does) and does not write to HubSpot (Ledger does)

← Back to AI Team