coilyco-flight-deck/agent-compose

Watch

Register housecast and house-cast on PyPI now, ahead of the repository #347

New issue

Open

opened 2026-08-25 18:52:26 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-25 18:52:26 +00:00

Member

Outcome

Claim housecast and house-cast on PyPI before anything else in #329 scope A
starts. This is a name-squatting race, not a packaging task, and it is separable
from every other step.

Why this is urgent rather than ordinary

The name landed in #330. The naming search that produced it turned up a finding
that outlives the naming question:

The naming register this product occupies is being actively consumed by other
AI-agent projects right now. Seven independent projects, all created during
2026, took names that were on the shortlist:

dokimasia - deevus/dokimasia, Pytest-first acceptance testing for agent
capabilities, created 2026-05-15
euthyna - Euthyna/Euthyna, local audit gateway for AI coding agents,
created 2026-07-22
chartulary - Cavinee/Chartulary, multi-agent repository analysis, created
2026-08-21
inspeximus - on PyPI, 114 releases, last shipped 2026-08-14, agent memory
vidimus - on PyPI, verifiable custody of agent-produced records
charter - meta-llm-charter, 249 stars, updated 2026-08-25
investiture - erikaflowers/investiture, Claude Code doctrine scaffold,
created 2026-01-31

Four of those cleared PyPI and died only on the GitHub check. One landed four
days before the search ran. PyPI distribution names are first-come and there is
no reservation mechanism short of uploading a distribution, so the gap between
choosing a name and holding it is pure exposure.

What to do

Upload a placeholder distribution for housecast claiming the name.
Do the same for house-cast, because PEP 503 normalizes house-cast and
house_cast to one name and housecast is a separate name. Holding both
removes the hyphen decision from the critical path and prevents a
near-miss squat.
Both names verified free 2026-08-25T18:50:55Z, 404 on both the JSON API and
the simple index, against a control string that also returned 404.

Boundaries

This is not the packaging slice. It claims names and stops. #329 scope A still
owns growing evalkit into the published compositor.
Do not treat a placeholder upload as a release. No version number that implies
working software, and the description should say the name is reserved.
The house-cast hyphen remains an open styling call, informed by the note in
#330 that housecast also parses as house plus forecast and that three of the
four existing GitHub repositories under that string are housing-price
forecasters.

#330 - the naming brief and the full search record, including the lock.
#329 - the parent design. The repository this name is for blocks its packaging
slice.

Ownership

Filed from the Developer Advocate seat, which owned the naming recommendation and
does not own packaging plumbing. Handing the action to the Developer Platform
Engineer.

## Outcome Claim `housecast` and `house-cast` on PyPI before anything else in #329 scope A starts. This is a name-squatting race, not a packaging task, and it is separable from every other step. ## Why this is urgent rather than ordinary The name landed in #330. The naming search that produced it turned up a finding that outlives the naming question: **The naming register this product occupies is being actively consumed by other AI-agent projects right now.** Seven independent projects, all created during 2026, took names that were on the shortlist: * `dokimasia` - `deevus/dokimasia`, Pytest-first acceptance testing for agent capabilities, created 2026-05-15 * `euthyna` - `Euthyna/Euthyna`, local audit gateway for AI coding agents, created 2026-07-22 * `chartulary` - `Cavinee/Chartulary`, multi-agent repository analysis, created 2026-08-21 * `inspeximus` - on PyPI, 114 releases, last shipped 2026-08-14, agent memory * `vidimus` - on PyPI, verifiable custody of agent-produced records * `charter` - `meta-llm-charter`, 249 stars, updated 2026-08-25 * `investiture` - `erikaflowers/investiture`, Claude Code doctrine scaffold, created 2026-01-31 Four of those cleared PyPI and died only on the GitHub check. One landed four days before the search ran. PyPI distribution names are first-come and there is no reservation mechanism short of uploading a distribution, so the gap between choosing a name and holding it is pure exposure. ## What to do * Upload a placeholder distribution for `housecast` claiming the name. * Do the same for `house-cast`, because PEP 503 normalizes `house-cast` and `house_cast` to one name and `housecast` is a separate name. Holding both removes the hyphen decision from the critical path and prevents a near-miss squat. * Both names verified free 2026-08-25T18:50:55Z, 404 on both the JSON API and the simple index, against a control string that also returned 404. ## Boundaries * This is not the packaging slice. It claims names and stops. #329 scope A still owns growing evalkit into the published compositor. * Do not treat a placeholder upload as a release. No version number that implies working software, and the description should say the name is reserved. * The `house-cast` hyphen remains an open styling call, informed by the note in #330 that `housecast` also parses as house plus forecast and that three of the four existing GitHub repositories under that string are housing-price forecasters. ## Related * #330 - the naming brief and the full search record, including the lock. * #329 - the parent design. The repository this name is for blocks its packaging slice. ## Ownership Filed from the Developer Advocate seat, which owned the naming recommendation and does not own packaging plumbing. Handing the action to the Developer Platform Engineer.

coilyco-ops added the

autonomy

headless

priority

labels

2026-08-25 18:52:26 +00:00

coilyco-ops referenced this issue

2026-08-25 20:29:41 +00:00

Create the compositor repository, package it, and publish it #337

coilyco-ops added

and removed

labels

2026-08-25 20:29:47 +00:00

coilyco-ops referenced this issue

2026-08-25 20:29:56 +00:00

Invert the stack: data, compositor, bundle, then Go. Drop KDL, move composition out of the engine, mount the roster #329

coilyco-ops commented

2026-08-25 20:30:10 +00:00

Author

Member

Correction: this is not headless, and I filed it as though it were

I filed this with autonomy/headless and wording that told the platform seat to
go claim the names. That was wrong, and #337 already said so before I wrote it.

#337 carries a standing HITL note: "Creating a public repository and claiming a
PyPI distribution name are externally visible and effectively irreversible, so
both need Kai's explicit go-ahead at the moment of creation rather than standing
authorization." Claiming housecast on PyPI is exactly that action. I had not
read #337 when I filed this, which is the actual mistake, since it was already on
the tracker and directly governs this.

Corrected:

Label moved from autonomy/headless to autonomy/async-consult, matching
#337.
The "What to do" section stands as the recommended action and not as
authorization. Nobody uploads anything until Kai says go, at the moment of
going.
Priority stays P2. The urgency argument is unaffected by who authorizes it.

The substance of this issue is unchanged. PyPI has no reservation mechanism short
of uploading, the register is being consumed at speed, and the gap between
choosing a name and holding it is exposure. That remains true and it remains
worth doing soon. It just needs Kai in the room when it happens.

## Correction: this is not headless, and I filed it as though it were I filed this with `autonomy/headless` and wording that told the platform seat to go claim the names. That was wrong, and #337 already said so before I wrote it. #337 carries a standing HITL note: "Creating a public repository and claiming a PyPI distribution name are externally visible and effectively irreversible, so both need Kai's explicit go-ahead at the moment of creation rather than standing authorization." Claiming `housecast` on PyPI is exactly that action. I had not read #337 when I filed this, which is the actual mistake, since it was already on the tracker and directly governs this. Corrected: * Label moved from `autonomy/headless` to `autonomy/async-consult`, matching #337. * The "What to do" section stands as the recommended action and **not** as authorization. Nobody uploads anything until Kai says go, at the moment of going. * Priority stays P2. The urgency argument is unaffected by who authorizes it. The substance of this issue is unchanged. PyPI has no reservation mechanism short of uploading, the register is being consumed at speed, and the gap between choosing a name and holding it is exposure. That remains true and it remains worth doing soon. It just needs Kai in the room when it happens.

coilyco-ops referenced this issue

2026-08-26 02:45:37 +00:00

Eval prep: the measured gap on the seven-seat board, and every eval, prose, and content ticket folded into one ordering #357

coilyco-ops referenced this issue

2026-08-27 09:36:08 +00:00

Create the compositor repository, package it, and publish it #337

coilyco-ops referenced this issue from a commit

2026-08-27 11:12:46 +00:00

feat!: hand composition to housecast and consume it from Forgejo (#337)

coilyco-ops referenced this issue

2026-08-27 11:16:08 +00:00

Create the compositor repository, package it, and publish it #337