[Adopter] Sentinel

[montfort]

Adopter registration — Sentinel

Closing a formality that's been true in practice for a long time: Sentinel is a StrayMark adopter. (Belatedly — the adopters template here already cites Sentinel as the reference adopter, so consider this the paperwork catching up to reality.)

Project name & repository
Sentinel — https://github.com/StrangeDaysTech/sentinel

Organization / responsible maintainer
Strange Days Tech / @montfort

Stack & domain
Go 1.25 modular-monolith backend — huma (HTTP+OpenAPI), watermill (event bus, GCP Pub/Sub), SQLC, Wire compile-time DI, goose migrations, Cloud SQL Postgres with per-tenant Row-Level Security, Firebase operator auth. Domain: a multi-tenant AIOps / incident-response platform — a SentinelAgent observes signals and takes guarded remediation actions (LLM propose→validate→execute via Vertex, with human-approval gates), alongside a comms hub, an MCP tool server, a policy engine, an audit trail, and a status center.

Versions adopted
fw-4.26.0 / cli-3.25.0 (current). Adoption predates this post — Sentinel has governed every Etapa with StrayMark since its early Charters.

Adoption path
Path A — StrayMark from day one (governance applied from Etapa 1 / CHARTER-01 onward).

Feedback committed

• Charter telemetry (.straymark/charters/CHARTER-NN.telemetry.yaml at close)
• External audit results (Sentinel routinely runs multi-CLI / multi-model calibration audits at Charter close — the external_audit arrays)
• Pattern candidates
• Format friction
• CLI bugs and documentation gaps

N-context — validating an existing pattern?
Sentinel is more often the N=1 origin of patterns than an N=2 validator — e.g. the Polish-Charter debt-detection pattern, Charter-chain evolution, and the atomic Charter-closure (format v4) pattern all originated here. Most recent dogfooding round surfaced Loom + architecture-model DX findings (issues #262 dangling-reference noise, #263 i18n robustness, #273 architecture-model DX + the has debt overlay), several already remediated upstream (e.g. #275). Domain for crystallization purposes: Go backend / AIOps.

Expected feedback cadence
Per Charter / Etapa close (~1–2 weeks), plus ad-hoc upstream Issues for tooling findings.

How findings cross-link
Actionable findings are filed as Issues that reference this discussion. Recent examples: #262, #263, #273 (Loom / architecture DX), with the fix landing in #275.

Acknowledgements

• Read the Adoption Guide and the Adopter Feedback guide.
• Telemetry stays in-repo by default; sharing is manual, and anything sensitive is anonymized before posting upstream.

Posted on behalf of the Sentinel maintainers to close the registration formality.