Say what this repository is now #65

Merged
PerishFire merged 1 commit from agents-current into main 2026-08-02 08:53:49 +00:00
Owner

AGENTS.md described four delivery planes, a pnpm web application with its component
territory, and runseal :guard spanning all of them. None of that has been true for a
while: the web plane was deferred to a placeholder, the generic wrappers and hooks are
gone, and guard calls its checkers directly. It also said cold start law was held
outside the repository while it settled, which stopped being true when the law moved in
as skills/ensign.

The layout now names what a reader will actually find, including deploy and skills,
and says why apps/web still holds a seat rather than leaving the next reader to guess
whether it was forgotten.

Two laws are added rather than corrected:

  • A landed seat is retired immediately. A rebase-landed worktree stops being provably
    landed once main moves again, and one left overnight blocked every branch in this
    repository that needed Cargo.lock.
  • Releases run through Plumb with guard_contexts declared. That declaration is what
    keeps a release reading the evidence recorded against its commit instead of
    recomputing it against a registry that moves faster than a promotion takes.

Every claim was checked against the tree rather than written from memory — the api
binary is still named api and only ships as ensign-api, which is the sort of detail
that made the previous version wrong.

AGENTS.md described four delivery planes, a pnpm web application with its component territory, and `runseal :guard` spanning all of them. None of that has been true for a while: the web plane was deferred to a placeholder, the generic wrappers and hooks are gone, and guard calls its checkers directly. It also said cold start law was held outside the repository while it settled, which stopped being true when the law moved in as `skills/ensign`. The layout now names what a reader will actually find, including `deploy` and `skills`, and says why `apps/web` still holds a seat rather than leaving the next reader to guess whether it was forgotten. Two laws are added rather than corrected: - A landed seat is retired immediately. A rebase-landed worktree stops being provably landed once `main` moves again, and one left overnight blocked every branch in this repository that needed `Cargo.lock`. - Releases run through Plumb with `guard_contexts` declared. That declaration is what keeps a release reading the evidence recorded against its commit instead of recomputing it against a registry that moves faster than a promotion takes. Every claim was checked against the tree rather than written from memory — the api binary is still named `api` and only ships as `ensign-api`, which is the sort of detail that made the previous version wrong.
Say what this repository is now
All checks were successful
guard / guard (pull_request) Successful in 3m43s
guard / guard (push) Successful in 3m40s
4a9a942206
AGENTS.md described four delivery planes, a pnpm web application with its
component territory, and `runseal :guard` spanning all of them. None of that
has been true for a while: the web plane was deferred to a placeholder, the
generic wrappers and hooks are gone, and guard calls its checkers directly.
It also said cold start law was held outside the repository while it settled,
which stopped being true when the law moved in as skills/ensign.

The layout now names what a reader will actually find, including `deploy` and
`skills`, and says why `apps/web` still holds a seat rather than leaving the
next reader to guess whether it was forgotten.

Two laws are added rather than corrected. A landed seat is retired
immediately, because a rebase-landed worktree stops being provably landed once
main moves again — that cost a blocked repository this week. And releases run
through Plumb with `guard_contexts` declared, because that declaration is what
keeps a release reading the evidence recorded against its commit instead of
recomputing it against a registry that moves faster than a promotion takes.
PerishFire deleted branch agents-current 2026-08-02 08:53:49 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PerishLab/ensign!65
No description provided.