Sentinel

Product core: Sentinel is a verified code-review product that turns pull requests into merge-ready verdicts.

First wedge: CLI review on exact HEAD → SHIP / DO NOT SHIP verdict with cited evidence → GitHub App. No code yet — strategy docs only.

The differentiating contract

AI review comments are cheap; merge confidence is not. Existing reviewers comment probabilistically: they can review a stale HEAD, re-report fixed findings, and approve what they never verified.

Sentinel’s contract: a verdict is only issued against the exact commit it verified, and a stale base invalidates the verdict automatically. That is the same evidence discipline this Knowledge Plane runs on.

Strategy docs (13, pinned)

Doc	What it decides
Market Research	Who bleeds from bad merges, cost
Competitor Analysis	Governance-first comparison, moat
Go-to-Market	CLI (free) → GitHub App → hosted tier
Brand Identity	Naming, voice
Personas	CTO, staff engineer, solo maintainer, compliance
Jobs to be Done	The 6 jobs Sentinel is hired for
Validation Plan	Desk research + prototype validation
UI Flows	CLI output, PR comment, verdict card
Data Model v0	Review, Verdict, EvidenceRef, RulePack
Risks	What kills this product
CLI v0 Design	CLI architecture
CLI v0 Features	Feature set
Decisions	Locked decisions

Honest maturity: strategy docs, prototype-first, no code yet. Nothing here upgrades Sentinel’s maturity.

Was this page helpful?