Doctrine: surface freeze during crunch windows, and provenance headers on briefs #1127

New issue

Open

opened 2026-08-18 17:09:59 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-18 17:09:59 +00:00

Member

Two doctrine lines fall out.

Surface freeze during crunch windows

During a declared crunch window (demo prep, incident, deadline), the tooling surface is frozen. A new repository, a new server process, or a new HTTP route is an escalation to Kai with a one-line justification, never something an agent self-serves or asks about in passing. A permission refusal on repo creation during a crunch is the system working, so the fix for hitting one is escalation, not a permission grant. Existing surfaces grow by guardfile grant or skill, which stay inside review.

Provenance headers on briefs

Any brief that names infrastructure carries a one-line provenance header stating whether each named component exists, is owned by another lane, or is to be built. "Infrastructure named here exists or is owned elsewhere, you consume it, never build it" is the default line. A described surface with no provenance reads as a spec, and an agent in goal mode will build it.

Acceptance: both lines land in the doctrine tree where composed roles pick them up, and the crunch-window rule is referenced from the role skills that can create repositories.

Worked example from 2026-08-18: an agent was briefed on a demo write surface described abstractly ("a hot-reloading server"), read the description as a build order, hit the repo-creation 403, asked, and the human created the repo by hand under time pressure. The result was quire, a well-built server the architecture did not want, plus a deploy train (deploy#664, #665, #667) that then read as work orders to other agents. Two doctrine lines fall out. ## Surface freeze during crunch windows During a declared crunch window (demo prep, incident, deadline), the tooling surface is frozen. A new repository, a new server process, or a new HTTP route is an escalation to Kai with a one-line justification, never something an agent self-serves or asks about in passing. A permission refusal on repo creation during a crunch is the system working, so the fix for hitting one is escalation, not a permission grant. Existing surfaces grow by guardfile grant or skill, which stay inside review. ## Provenance headers on briefs Any brief that names infrastructure carries a one-line provenance header stating whether each named component exists, is owned by another lane, or is to be built. "Infrastructure named here exists or is owned elsewhere, you consume it, never build it" is the default line. A described surface with no provenance reads as a spec, and an agent in goal mode will build it. Acceptance: both lines land in the doctrine tree where composed roles pick them up, and the crunch-window rule is referenced from the role skills that can create repositories.

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

coilyco-flight-deck/agentic-os#1127

No description provided.

Rows
Columns