feat(dowel): carry the site write surface as the lane's landing workflow

coilysiren commented

2026-08-18 16:56:41 +00:00

Owner

The demo's work surface is a guarded MCP over markdown fragments: list, read,
put, no delete. The rule that matters for this lane is that those verbs are the
whole landing workflow, so a successful put is delivered work rather than a
change awaiting promotion. Without saying so, the engineer charter's deferral of
live mutation reads a site put as an operator action and hands off the exact
work the demo exists to show.

Draws the line rather than waiving it: rollback, serving, and nginx stay out of
reach and out of the agent's promises, because no verb reaches them.

Carries the operating discipline the surface actually needs: one file per
concern so a new section is a new file, read-then-put because a put rewrites the
file whole and there is no append verb, minimal flat front matter or none at all
since indentation is the one visible way to break a page, and one put per
section because the audience sees each one within about two seconds.

Names the collision with capability.md rather than leaving it to be guessed. That
file forbids describing work as queued, and the changelog protocol asks for a
queued line. The rule is about work outliving the turn, so a line for a put that
lands before the reply is sent is a record rather than a promise.

Refs coilyco-bridge/deploy#658

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Co-authored-by: Angie coilyco-ops@coilysiren.me
Co-authored-by: Claude noreply@anthropic.com

The demo's work surface is a guarded MCP over markdown fragments: list, read, put, no delete. The rule that matters for this lane is that those verbs are the whole landing workflow, so a successful put is delivered work rather than a change awaiting promotion. Without saying so, the engineer charter's deferral of live mutation reads a site put as an operator action and hands off the exact work the demo exists to show. Draws the line rather than waiving it: rollback, serving, and nginx stay out of reach and out of the agent's promises, because no verb reaches them. Carries the operating discipline the surface actually needs: one file per concern so a new section is a new file, read-then-put because a put rewrites the file whole and there is no append verb, minimal flat front matter or none at all since indentation is the one visible way to break a page, and one put per section because the audience sees each one within about two seconds. Names the collision with capability.md rather than leaving it to be guessed. That file forbids describing work as queued, and the changelog protocol asks for a queued line. The rule is about work outliving the turn, so a line for a put that lands before the reply is sent is a record rather than a promise. Refs coilyco-bridge/deploy#658 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: Angie <coilyco-ops@coilysiren.me> Co-authored-by: Claude <noreply@anthropic.com>

coilysiren added 1 commit

2026-08-18 16:56:41 +00:00

feat(dowel): carry the site write surface as the lane's landing workflow

ci / image-build (pull_request) Successful in 3s

Details

ci / test (pull_request) Successful in 59s

Details

ci / publish-echo-image (pull_request) Has been skipped

Details

ci / publish-observed (pull_request) Has been skipped

Details

755625b0e0

The demo's work surface is a guarded MCP over markdown fragments: list, read,
put, no delete. The rule that matters for this lane is that those verbs are the
whole landing workflow, so a successful put is delivered work rather than a
change awaiting promotion. Without saying so, the engineer charter's deferral of
live mutation reads a site put as an operator action and hands off the exact
work the demo exists to show.

Draws the line rather than waiving it: rollback, serving, and nginx stay out of
reach and out of the agent's promises, because no verb reaches them.

Carries the operating discipline the surface actually needs: one file per
concern so a new section is a new file, read-then-put because a put rewrites the
file whole and there is no append verb, minimal flat front matter or none at all
since indentation is the one visible way to break a page, and one put per
section because the audience sees each one within about two seconds.

Names the collision with capability.md rather than leaving it to be guessed. That
file forbids describing work as queued, and the changelog protocol asks for a
queued line. The rule is about work outliving the turn, so a line for a put that
lands before the reply is sent is a record rather than a promise.

Refs coilyco-bridge/deploy#658

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Angie <coilyco-ops@coilysiren.me>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops referenced this pull request

2026-08-18 19:15:16 +00:00

fix(image): ship the sirens-dowel skill root, which is crashlooping the lane #972

coilyco-ops commented

2026-08-18 19:16:21 +00:00

Member

Closing rather than resolving the conflict. Diffed both files against d887bd8, and the branch carries nothing main lacks.

.agents/skills/sirens-dowel/SKILL.md - byte-identical to main. Empty diff.
.agents/skills/sirens-dowel/references/site-work.md - 82 lines here against main's 96, and older. This version describes a generic "list the pages, read a page, put a page" write surface. Main describes the quire MCP by its real verbs, list_page / get_page / set_page, and points at the quire-pages resource, after 695ea7b matched the prose to the surface that actually shipped. Merging this replaces accurate prose with prose naming tools that do not exist.

The work this PR describes landed through #954 and #956. Against current main the branch is a ~3,500 line revert, predating internal/coalesce, internal/ingest, cmd/sirens-echo-bridge, #947, and #963.

Reopenable if something here was meant to be distinct from what landed.

Closing rather than resolving the conflict. Diffed both files against `d887bd8`, and the branch carries nothing main lacks. * **`.agents/skills/sirens-dowel/SKILL.md`** - byte-identical to main. Empty diff. * **`.agents/skills/sirens-dowel/references/site-work.md`** - 82 lines here against main's 96, and older. This version describes a generic "list the pages, read a page, put a page" write surface. Main describes the quire MCP by its real verbs, `list_page` / `get_page` / `set_page`, and points at the `quire-pages` resource, after 695ea7b matched the prose to the surface that actually shipped. Merging this replaces accurate prose with prose naming tools that do not exist. The work this PR describes landed through #954 and #956. Against current main the branch is a ~3,500 line revert, predating `internal/coalesce`, `internal/ingest`, `cmd/sirens-echo-bridge`, #947, and #963. Reopenable if something here was meant to be distinct from what landed.

coilyco-ops closed this pull request

2026-08-18 19:16:23 +00:00

coilyco-ops referenced this pull request

2026-08-18 19:16:53 +00:00

The skillpack loader discards every skill's description and inlines its body instead #971