The Sentinel Protocol
How 24/7 monitoring prevents Architecture Decay.
Vigilance is the first pillar of the Vellum Standards. The Sentinel Protocol is our commitment to 24/7 monitoring so that your infrastructure never degrades unnoticed—a state we call Architecture Decay.
What Is Architecture Decay?
Architecture Decay occurs when:
- SSL certificates approach expiry and nobody is alerted
- Security headers are removed or misconfigured in a deploy
- Latency drifts above the Heritage threshold
- DNS or cache TTLs change and break assumptions
Without continuous monitoring, these regressions go unnoticed until they cause an incident. The Sentinel Protocol exists to prevent that.
How the Protocol Works
- Continuous checks — Scribe Sentinel runs checks on a schedule (and on demand) against your configured endpoints.
- Signal evaluation — Each check evaluates SSL, Headers, Latency, TTL and other signals.
- Grading — Results are aggregated into a Heritage Grade (A through F).
- Alerts — When a signal degrades or a grade drops, the Sentinel notifies you so you can correct course before users are affected.
Vigilance in Practice
- Run a Quick Audit — From the homepage or onboarding flow, you can trigger an immediate scan and see your grade.
- Monitor in the Portal — Once you have an organization, use the Scribe Cloud dashboard to view real-time status and history.
- Automate responses — Integrate with your CI/CD or runbooks so that failed Sentinel checks block deploys or trigger remediation.
Related
- Scribe Sentinel — What we monitor and how to interpret grades.
- Edge Standards — Latency and orchestration requirements.
- The Security Vault — Header and policy integrity.