Write the four prose sections on the housecast project page #139

New issue

Open

opened 2026-08-28 21:08:45 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-28 21:08:45 +00:00

Collaborator

The page shell is live at /projects/housecast/, noindex until the prose lands. Everything mechanical is already filled. What is left is the four sections #133 assigns to the Developer Advocate seat, and this issue is the handoff so it is not a conversation that ended.

What is already decided, so it is not re-litigated

The claim is the repository description verbatim, per coilysiren/inbox#397: "A YAML driven roster framework for agent context." Never re-invented for this page.
Status is Preview, because housecast has no tagged release. #133 is explicit that a page says what is true rather than implying parity with umbra and agent-compose.
No showcase tile yet. projects.js describes the homepage tile as the strongest content on the page, and a tile leading to TK copy spends that attention badly. It goes up when the prose does.
No stack chain section, and that is a separate decision rather than an omission. The chain is now umbra, mcp-beaver, agent-compose since sirens-echo was deprovisioned in 42ca404, and whether housecast takes the vacated fourth slot is open.

The four sections, with the brief already in the file

Each carries TK. stubs naming what it is for. The order is #133's buyer-framing order and is not negotiable.

problem - the problem as the reader already has it, plus what it costs to leave alone. #133 calls this the section that decides whether the page reaches buyers or practitioners.
how-it-works - the mechanism at one level of depth.
roster - one real artifact, shown then explained. #133 notes these projects are unusually strong here, because the roster and policy files are short and readable.
not-a-framework - honest non-goals. Converts better than more features do.

The hero also carries three TK fields: hook, caption, and the code sample.

Source material, because this is extraction rather than invention

Repository: coilyco-flight-deck/housecast, README 3.8 KB.
docs/FEATURES.md, the only page its docs directory holds. It already names the composition engine, the roster language and the roster projection, in the shape sections 2 and 3 want.
housecast/data/roster.yaml is the obvious candidate for the roster section's artifact, since it is the thing a reader would understand immediately.
Context on why it exists: coilyco-flight-deck/agent-compose#329, #333 and #337.

The rule that binds every section

A project page never restates a fact with a canonical home. The claim comes from the repository description, the status from the release, and anything hand-written must be content that exists nowhere else, which is exactly these four sections. If the page and the repository disagree about what housecast is, the repository wins and the page is the bug.

Done means

The four sections and the three hero fields carry no TK.
robots flips from noindex, follow to follow, index, which also puts the page in the sitemap, since the sitemap already filters on exactly that
A showcase entry in src/data/projects.js, which needs a banner and a mark that do not exist yet (coilysiren/inbox#406 owns marks)
A decision recorded on whether housecast joins the stack chain

The last two are not the writer's to make alone and are listed so they are not discovered after the prose is done.

The page shell is live at `/projects/housecast/`, `noindex` until the prose lands. Everything mechanical is already filled. What is left is the four sections #133 assigns to the Developer Advocate seat, and this issue is the handoff so it is not a conversation that ended. ## What is already decided, so it is not re-litigated * **The claim is the repository description verbatim**, per `coilysiren/inbox#397`: *"A YAML driven roster framework for agent context."* Never re-invented for this page. * **Status is Preview**, because housecast has no tagged release. #133 is explicit that a page says what is true rather than implying parity with umbra and agent-compose. * **No showcase tile yet.** `projects.js` describes the homepage tile as the strongest content on the page, and a tile leading to TK copy spends that attention badly. It goes up when the prose does. * **No stack chain section**, and that is a separate decision rather than an omission. The chain is now umbra, mcp-beaver, agent-compose since sirens-echo was deprovisioned in `42ca404`, and whether housecast takes the vacated fourth slot is open. ## The four sections, with the brief already in the file Each carries `TK.` stubs naming what it is for. The order is #133's buyer-framing order and is not negotiable. * `problem` - the problem as the reader already has it, plus what it costs to leave alone. #133 calls this the section that decides whether the page reaches buyers or practitioners. * `how-it-works` - the mechanism at one level of depth. * `roster` - one real artifact, shown then explained. #133 notes these projects are unusually strong here, because the roster and policy files are short and readable. * `not-a-framework` - honest non-goals. Converts better than more features do. The hero also carries three TK fields: `hook`, `caption`, and the code `sample`. ## Source material, because this is extraction rather than invention * Repository: `coilyco-flight-deck/housecast`, README 3.8 KB. * `docs/FEATURES.md`, the only page its docs directory holds. It already names the composition engine, the roster language and the roster projection, in the shape sections 2 and 3 want. * `housecast/data/roster.yaml` is the obvious candidate for the `roster` section's artifact, since it is the thing a reader would understand immediately. * Context on why it exists: `coilyco-flight-deck/agent-compose#329`, `#333` and `#337`. ## The rule that binds every section A project page never restates a fact with a canonical home. The claim comes from the repository description, the status from the release, and anything hand-written must be content that exists nowhere else, which is exactly these four sections. If the page and the repository disagree about what housecast is, the repository wins and the page is the bug. ## Done means - [ ] The four sections and the three hero fields carry no `TK.` - [ ] `robots` flips from `noindex, follow` to `follow, index`, which also puts the page in the sitemap, since the sitemap already filters on exactly that - [ ] A showcase entry in `src/data/projects.js`, which needs a banner and a mark that do not exist yet (`coilysiren/inbox#406` owns marks) - [ ] A decision recorded on whether housecast joins the stack chain The last two are not the writer's to make alone and are listed so they are not discovered after the prose is done.

coilyco-ops added the

labels

2026-08-28 21:08:45 +00:00