Sentinel

What Sentinel doesCopy Anchor Link

A project's shared foundation keeps moving after launch: package managers change, and code copied into each project becomes published Ciridae packages. Porting every change by hand turns into maintenance debt. Sentinel applies Ciridae-authored updates to your repository and opens them as draft PRs your team reviews and merges.

Current updates move projects from Yarn to pnpm, replace duplicated auth, telemetry, OpenAPI tooling, Temporal Sentry, and Ghost client code with their published Ciridae packages, and adopt direct object storage access.

Sentinel never marks a PR ready or merges it. Your team decides when each change ships.

How an update reaches your projectCopy Anchor Link

1. Eligibility: Sentinel considers projects that enable it in project.yaml and have a live full deployment.
2. Qualification: Sentinel reads the trunk branch and decides whether the update applies. If the pattern it replaces is absent, the run stops without creating a branch.
3. Change: An agent in a temporary workspace makes the change, runs the project's checks, and opens a draft PR. Some updates open an ordered stack of draft PRs, and each PR body states the merge and deployment order.
4. Correction: The agent works through CI failures and high-priority review findings, for up to three rounds.
5. Review: Your team reviews the draft, marks it ready, and merges it.

Turn Sentinel offCopy Anchor Link

Projects created from the Agents template have Sentinel on. To opt out, override the setting in the project's project.yaml on the trunk branch:

updates:
  sentinel:
    enabled: false