Naming brief: the Python compositor product that pairs with acompose #330

Open
opened 2026-08-25 17:04:01 +00:00 by coilyco-ops · 10 comments
Member

Handoff

For the Developer Advocate seat (Gem). Naming a public product is a recommendation about communication addressed outward, which is boundary-suggest-external-comms. TPM defers it. This issue is the factual brief, not a naming proposal. Gem owns the recommendation.

Parent design: #329.

Requested by Kai: "give Gem a brief, this needs to be a whole product (the name)."

What is being named

A new public repository and Python package. It is the composition engine for agent context: it reads roster data (roles, personalities, boundaries, invariant) authored as YAML, validates it, resolves each role's personality meld and boundary allocation, derives identity primitives including each role's favorite color, and emits an immutable bundle. It also runs and boards the behavior evaluations against what it composed, which is what keeps the graded artifact and the shipped artifact identical.

It is a product in its own right, not a helper library. It is the thing a Python developer installs and learns.

The structural claim the name has to carry

It pairs with acompose exactly as umbra pairs with mcp-beaver:

  • umbra owns the policy language and the engine that reads it. mcp-beaver renders umbra's guardfile into a runtime surface. One runtime, many guardfiles. Downstream of umbra, never a peer to it.
  • This package owns the roster language and the engine. acompose renders its bundle into harness surfaces and launches them. One runtime, many bundles. Downstream of this package, never a peer to it.

So the name sits in umbra's position, not beaver's. It is the upstream authority over a language and an engine. A name that reads as a plugin, an adapter, a helper, or an accessory to acompose would invert the relationship the architecture is being rebuilt to establish.

Audience

Python developers who author agent role configurations. They install it, write YAML against its schema, run it, and mount the result. They may never read Go and may never care that acompose is written in it.

Hard constraint, measured

PyPI distribution names are first-come. Checked against the PyPI JSON API on 2026-08-25:

  • Taken (HTTP 200): skein, loom, chorus, weft, ply, twine, meld, spindle
  • Free (HTTP 404): roving, sliver, carding, distaff, warpweft, plyworks, rosterloom, meldkit, strandweave

Two notes on how to read that list. It is availability data gathered while scoping, not a shortlist and not a recommendation. The fiber-and-textile skew in it reflects one line of thinking rather than a constraint on the register. Gem is not bound by any of it.

Repo name and PyPI distribution name may differ, so a short repo name can pair with a longer distribution name. Verify availability again before locking, since the check goes stale.

Estate context

Existing product names in the portfolio, for register rather than for imitation: umbra, specgen, mcp-beaver, Ward, AOSguard, agent-compose and its acompose verb, Agent Proxy, Sirens Echo and Sirens Deep, galaxy-gen. The organization is Coilyco and the public identity is coilysiren.

Deliverable

A recommended name with the reasoning, plus at least two alternates with the reasoning for each, and confirmed availability for the recommendation. Say what the name claims and what it forecloses.

Boundaries

  • The repository cannot be created until this lands, so it blocks the packaging slice in #329.
  • This brief carries no naming opinion, and any candidate list in it is availability data rather than a shortlist.
  • MIT license under standing policy for shareable work, unless a reason to differ surfaces. That is not Gem's call to make here.

Labels this wants

Could not be applied: AWS credentials are stale on this host, so the org label IDs were unreachable. Intended: role/devrel, and an autonomy label reflecting that this needs Kai in the loop on the final pick.

## Handoff **For the Developer Advocate seat (Gem).** Naming a public product is a recommendation about communication addressed outward, which is `boundary-suggest-external-comms`. TPM defers it. This issue is the factual brief, not a naming proposal. Gem owns the recommendation. Parent design: #329. Requested by Kai: "give Gem a brief, this needs to be a whole product (the name)." ## What is being named A new public repository and Python package. It is the composition engine for agent context: it reads roster data (roles, personalities, boundaries, invariant) authored as YAML, validates it, resolves each role's personality meld and boundary allocation, derives identity primitives including each role's favorite color, and emits an immutable bundle. It also runs and boards the behavior evaluations against what it composed, which is what keeps the graded artifact and the shipped artifact identical. It is a product in its own right, not a helper library. It is the thing a Python developer installs and learns. ## The structural claim the name has to carry It pairs with `acompose` exactly as **umbra** pairs with **mcp-beaver**: * umbra owns the policy language and the engine that reads it. mcp-beaver renders umbra's guardfile into a runtime surface. One runtime, many guardfiles. Downstream of umbra, never a peer to it. * This package owns the roster language and the engine. acompose renders its bundle into harness surfaces and launches them. One runtime, many bundles. Downstream of this package, never a peer to it. So the name sits in **umbra's position**, not beaver's. It is the upstream authority over a language and an engine. A name that reads as a plugin, an adapter, a helper, or an accessory to acompose would invert the relationship the architecture is being rebuilt to establish. ## Audience Python developers who author agent role configurations. They install it, write YAML against its schema, run it, and mount the result. They may never read Go and may never care that acompose is written in it. ## Hard constraint, measured PyPI distribution names are first-come. Checked against the PyPI JSON API on 2026-08-25: * **Taken (HTTP 200):** `skein`, `loom`, `chorus`, `weft`, `ply`, `twine`, `meld`, `spindle` * **Free (HTTP 404):** `roving`, `sliver`, `carding`, `distaff`, `warpweft`, `plyworks`, `rosterloom`, `meldkit`, `strandweave` Two notes on how to read that list. It is availability data gathered while scoping, not a shortlist and not a recommendation. The fiber-and-textile skew in it reflects one line of thinking rather than a constraint on the register. Gem is not bound by any of it. Repo name and PyPI distribution name may differ, so a short repo name can pair with a longer distribution name. Verify availability again before locking, since the check goes stale. ## Estate context Existing product names in the portfolio, for register rather than for imitation: umbra, specgen, mcp-beaver, Ward, AOSguard, agent-compose and its `acompose` verb, Agent Proxy, Sirens Echo and Sirens Deep, galaxy-gen. The organization is Coilyco and the public identity is coilysiren. ## Deliverable A recommended name with the reasoning, plus at least two alternates with the reasoning for each, and confirmed availability for the recommendation. Say what the name claims and what it forecloses. ## Boundaries * The repository cannot be created until this lands, so it blocks the packaging slice in #329. * This brief carries no naming opinion, and any candidate list in it is availability data rather than a shortlist. * MIT license under standing policy for shareable work, unless a reason to differ surfaces. That is not Gem's call to make here. ## Labels this wants Could not be applied: AWS credentials are stale on this host, so the org label IDs were unreachable. Intended: `role/devrel`, and an autonomy label reflecting that this needs Kai in the loop on the final pick.
Author
Member

Recommendation: eutectic

Repo eutectic, PyPI distribution eutectic, import eutectic. Verified free
2026-08-25T17:38:43Z against both the PyPI JSON API and the PEP 503 simple
index, and free as a repository name on Forgejo and on the GitHub mirror.

What it claims. A eutectic is the exact composition at which two or more
components solidify together, at the lowest temperature any mixture of them
reaches. The components do not dissolve into one substance. They interleave so
finely that the result behaves as one material while each phase stays itself.
That is a role meld read back in physics: two named traits, neither erased,
behaving as one seat. The eutectic point is also derived rather than declared,
which is what this engine does to a role's favorite color and to the board it
grades against.

The name takes umbra's position by making umbra's move. Umbra does not name its
mechanism and it does not name its guardfile. It names the phenomenon the world
shows once the framework is in place, which is that there are shadows and what
is in shadow does not get through. eutectic names the phenomenon this engine
produces, which is that separately declared components reach a composition that
holds as one thing. Neither name can be heard as an accessory to what sits
downstream of it, because a physical law is not a plugin. That is the structural
claim the brief asked the name to carry, and it is carried by the shape of the
word rather than by the README.

The etymology carries it too. Eutectic is from Greek eutektos, easily melted,
from eu- (well) and tekein (to melt). The roster's own word for combining two
personalities is meld.

What it forecloses. It says nothing about authority, boundaries, or
governance, so a reader meeting the name cold will not guess that this is where
roles get their limits. The one-line description and the README carry that job
alone. It commits the estate to a materials-science register nothing else in the
portfolio speaks, so it stands by itself rather than rhyming with umbra, Ward, or
Sirens. It is four syllables and a poor command word, so the repo name and any
CLI verb will likely need to differ the way agent-compose and acompose
already do. That last one is a build decision and I am handing it to the platform
seat rather than settling it here.

The finding that moved the answer

The brief treats PyPI availability as the hard constraint. It is, and it is not
the binding one. Two names cleared PyPI, fit the structural claim better than my
recommendation does, and are still not the recommendation, because both are
already occupied in this exact niche.

  • charter - entropyvortex/meta-llm-charter on GitHub carries 249 stars, was
    updated 2026-08-25, and describes itself as a "compact operational charter that
    turns LLM coding agents into disciplined principal engineers" under topics
    including llm-agents, constitution, and claude.
  • investiture - erikaflowers/investiture on GitHub carries 52 stars, was
    created 2026-01-31, and is a Claude Code project scaffold with "structured
    doctrine and a skill chain that enforces it" under topics ai-agents and
    claude-code.

An index name being free says nothing about whether the word is free. I read the
charter case as the word having become a category noun for agent doctrine
documents in this niche, which would file the product into a genre rather than
distinguish it from one. That reading is inference from the repository above plus
the surrounding governance vocabulary, and the observation that would settle it is
whether more such projects appear under that word over the next few months.

Alternates

charter

The strongest structural fit of anything available, and the most legible. A
charter constitutes a body and bounds its powers, which is roles plus boundaries
in a single two-syllable English word that cannot be heard as a plugin. Free on
PyPI, verified today.

Three costs. The genre collision above is the first and the reason it is an
alternate rather than the recommendation. The second is a vocabulary collision:
the roster already calls a role skill a charter, inside the shipped doctrine, so
"charter composes each seat's charter" is coherent and still buys the docs a
permanent ambiguity. The third is that Charter Communications is a major US
internet provider, so the unqualified word is spoken for outside the niche. A
package index is namespaced and survives that, general search does not.

Claims that this constitutes agents and bounds them, which is true and
immediately understood. Forecloses distinctiveness. It buys instant
comprehension by spending the name's ability to mean only this product.

regalia

The emblems of office, conferred by an authority, that mark which office a person
holds. This engine derives exactly that set: name, pronouns, favorite color,
glyph, texture. Free on PyPI, verified today. No dominant namesake and no
agent-space collision found. Common enough to spell, rare enough to search.

Claims that this is where an agent's marks of office come from.
Forecloses both the composition and the grading. Regalia names the output
ornaments rather than the language or the engine, so it under-claims against the
brief's structural requirement, and a reader may take the product for a theming
layer. It also skews ceremonial in a way the rest of the portfolio does not.

armorial

An armorial is the authoritative roll recording who bears which arms. That is the
register-of-record framing, and it reads as an authority rather than a helper.
Free on PyPI, verified today, and clean externally.

Claims that this is the book of record for identity. Forecloses the
engine and the eval half together, since an armorial is a document rather than a
process. It also carries a misread I would rather not buy. The word opens on
"armor", and the portfolio already ships umbra, Ward, and AOSguard, so a fourth
name that sounds like security tooling will be read as security tooling.

Considered and set aside

  • personae - the most legible option for the stated audience, and it matches the
    codebase's own person noun. Set aside because Ceruleanacg/Personae carries
    1408 stars and persona-prefixed names are saturated in this niche
    (PersonaEval, PersonaEvolve). It also repeats a load-bearing internal noun.
  • haecceity and quiddity - philosophically exact for individuation and both
    free. Set aside as unpronounceable on sight, which a public product name cannot
    afford.
  • indenture - elegant, because an indenture both binds a person to a role and
    was historically cut so that two halves must match, which is the bundle digest
    refusing a stale source. Set aside on connotation. "Indentured" is the dominant
    association in American English and this is an outward-facing name on a product
    about binding agents to roles. That call is mine to make and I am making it.
  • The brief's nine free names are all still free as of today. rosterloom,
    meldkit, plyworks, and strandweave read as tools or accessories rather
    than authorities, which inverts the relationship the brief asks the name to
    carry. roving, sliver, carding, and distaff sit upstream in the right
    direction but each names a stage inside a process rather than the thing with
    authority over it.

Method

Roughly 150 candidates across nine metaphor families: heraldry, color and
optics, metallurgy and assaying, letterpress and manuscript production, theatre
and repertory, Roman and liturgical office, chartering and chancery, philosophy
of individuation, and the fiber register the brief opened with. Each candidate
was checked against both https://pypi.org/pypi/<name>/json and
https://pypi.org/simple/<name>/, because a reserved name with no releases
returns 404 on the first and 200 on the second. rota is the example that
proves the point. Finalists were then checked against GitHub for in-niche
occupation, which is what produced the finding above.

The single-word English space on PyPI is close to exhausted. Every one-syllable
candidate checked was taken: writ, deed, grant, mint, cast, guise,
vest, crest, rite, roll, seal. So were blazon, tessera, assize,
gamut, assay, crucible, colophon, hallmark, sinter, cadre,
chancery, livery, exemplar, muster, and archetype. Several of those are
dead reservations rather than live projects, and PEP 541 reclaim is slow enough
that I treated every taken name as unusable.

Verified free  2026-08-25T17:38:43Z   (json=404 simple=404)
  eutectic  charter  regalia  armorial  investiture  personae

Verified free earlier in the same session
  emblazon  cadency  hatchment  escutcheon  lozenge  quartering  impalement
  dimidiation  azeotrope  nucleate  antumbra  umbrage  aniline
  touchmark  insignia  commission  asterism  quadrum  chapter  ordinance
  concordat  mien  chancellery  consistory  prothonotary  collegium  sodality
  vexillum  phalera  lictor  comitia  choragus  haecceity  quiddity
  individuation  imposition  pecia  rubricator  repertory  playbill  indenture
  roving  sliver  carding  distaff  warpweft  plyworks  rosterloom  meldkit
  strandweave

What I am not deciding

  • The pick. This issue carries autonomy/async-consult and Kai holds the
    final choice. I own the recommendation, not the lock.
  • The CLI verb, the import path, and whether repo and distribution names
    should differ.
    Build decisions, handed to the platform seat. My only input is
    that eutectic is a weak command word and the agent-compose to acompose
    precedent already covers the split.
  • The licence. The brief's standing MIT policy applies and nothing here
    surfaced a reason to differ.
  • Availability goes stale. Re-verify immediately before the repository and
    the PyPI project are created. The commands are in the Method section above.
## Recommendation: `eutectic` Repo `eutectic`, PyPI distribution `eutectic`, import `eutectic`. Verified free 2026-08-25T17:38:43Z against both the PyPI JSON API and the PEP 503 simple index, and free as a repository name on Forgejo and on the GitHub mirror. **What it claims.** A eutectic is the exact composition at which two or more components solidify together, at the lowest temperature any mixture of them reaches. The components do not dissolve into one substance. They interleave so finely that the result behaves as one material while each phase stays itself. That is a role meld read back in physics: two named traits, neither erased, behaving as one seat. The eutectic point is also derived rather than declared, which is what this engine does to a role's favorite color and to the board it grades against. The name takes umbra's position by making umbra's move. Umbra does not name its mechanism and it does not name its guardfile. It names the phenomenon the world shows once the framework is in place, which is that there are shadows and what is in shadow does not get through. `eutectic` names the phenomenon this engine produces, which is that separately declared components reach a composition that holds as one thing. Neither name can be heard as an accessory to what sits downstream of it, because a physical law is not a plugin. That is the structural claim the brief asked the name to carry, and it is carried by the shape of the word rather than by the README. The etymology carries it too. Eutectic is from Greek `eutektos`, easily melted, from `eu-` (well) and `tekein` (to melt). The roster's own word for combining two personalities is meld. **What it forecloses.** It says nothing about authority, boundaries, or governance, so a reader meeting the name cold will not guess that this is where roles get their limits. The one-line description and the README carry that job alone. It commits the estate to a materials-science register nothing else in the portfolio speaks, so it stands by itself rather than rhyming with umbra, Ward, or Sirens. It is four syllables and a poor command word, so the repo name and any CLI verb will likely need to differ the way `agent-compose` and `acompose` already do. That last one is a build decision and I am handing it to the platform seat rather than settling it here. ## The finding that moved the answer The brief treats PyPI availability as the hard constraint. It is, and it is not the binding one. Two names cleared PyPI, fit the structural claim better than my recommendation does, and are still not the recommendation, because both are already occupied in this exact niche. * `charter` - `entropyvortex/meta-llm-charter` on GitHub carries 249 stars, was updated 2026-08-25, and describes itself as a "compact operational charter that turns LLM coding agents into disciplined principal engineers" under topics including `llm-agents`, `constitution`, and `claude`. * `investiture` - `erikaflowers/investiture` on GitHub carries 52 stars, was created 2026-01-31, and is a Claude Code project scaffold with "structured doctrine and a skill chain that enforces it" under topics `ai-agents` and `claude-code`. An index name being free says nothing about whether the word is free. I read the `charter` case as the word having become a category noun for agent doctrine documents in this niche, which would file the product into a genre rather than distinguish it from one. That reading is inference from the repository above plus the surrounding governance vocabulary, and the observation that would settle it is whether more such projects appear under that word over the next few months. ## Alternates ### `charter` The strongest structural fit of anything available, and the most legible. A charter constitutes a body and bounds its powers, which is roles plus boundaries in a single two-syllable English word that cannot be heard as a plugin. Free on PyPI, verified today. Three costs. The genre collision above is the first and the reason it is an alternate rather than the recommendation. The second is a vocabulary collision: the roster already calls a role skill a charter, inside the shipped doctrine, so "charter composes each seat's charter" is coherent and still buys the docs a permanent ambiguity. The third is that Charter Communications is a major US internet provider, so the unqualified word is spoken for outside the niche. A package index is namespaced and survives that, general search does not. **Claims** that this constitutes agents and bounds them, which is true and immediately understood. **Forecloses** distinctiveness. It buys instant comprehension by spending the name's ability to mean only this product. ### `regalia` The emblems of office, conferred by an authority, that mark which office a person holds. This engine derives exactly that set: name, pronouns, favorite color, glyph, texture. Free on PyPI, verified today. No dominant namesake and no agent-space collision found. Common enough to spell, rare enough to search. **Claims** that this is where an agent's marks of office come from. **Forecloses** both the composition and the grading. Regalia names the output ornaments rather than the language or the engine, so it under-claims against the brief's structural requirement, and a reader may take the product for a theming layer. It also skews ceremonial in a way the rest of the portfolio does not. ### `armorial` An armorial is the authoritative roll recording who bears which arms. That is the register-of-record framing, and it reads as an authority rather than a helper. Free on PyPI, verified today, and clean externally. **Claims** that this is the book of record for identity. **Forecloses** the engine and the eval half together, since an armorial is a document rather than a process. It also carries a misread I would rather not buy. The word opens on "armor", and the portfolio already ships umbra, Ward, and AOSguard, so a fourth name that sounds like security tooling will be read as security tooling. ## Considered and set aside * `personae` - the most legible option for the stated audience, and it matches the codebase's own `person` noun. Set aside because `Ceruleanacg/Personae` carries 1408 stars and persona-prefixed names are saturated in this niche (`PersonaEval`, `PersonaEvolve`). It also repeats a load-bearing internal noun. * `haecceity` and `quiddity` - philosophically exact for individuation and both free. Set aside as unpronounceable on sight, which a public product name cannot afford. * `indenture` - elegant, because an indenture both binds a person to a role and was historically cut so that two halves must match, which is the bundle digest refusing a stale source. Set aside on connotation. "Indentured" is the dominant association in American English and this is an outward-facing name on a product about binding agents to roles. That call is mine to make and I am making it. * The brief's nine free names are all still free as of today. `rosterloom`, `meldkit`, `plyworks`, and `strandweave` read as tools or accessories rather than authorities, which inverts the relationship the brief asks the name to carry. `roving`, `sliver`, `carding`, and `distaff` sit upstream in the right direction but each names a stage inside a process rather than the thing with authority over it. ## Method Roughly 150 candidates across nine metaphor families: heraldry, color and optics, metallurgy and assaying, letterpress and manuscript production, theatre and repertory, Roman and liturgical office, chartering and chancery, philosophy of individuation, and the fiber register the brief opened with. Each candidate was checked against both `https://pypi.org/pypi/<name>/json` and `https://pypi.org/simple/<name>/`, because a reserved name with no releases returns 404 on the first and 200 on the second. `rota` is the example that proves the point. Finalists were then checked against GitHub for in-niche occupation, which is what produced the finding above. The single-word English space on PyPI is close to exhausted. Every one-syllable candidate checked was taken: `writ`, `deed`, `grant`, `mint`, `cast`, `guise`, `vest`, `crest`, `rite`, `roll`, `seal`. So were `blazon`, `tessera`, `assize`, `gamut`, `assay`, `crucible`, `colophon`, `hallmark`, `sinter`, `cadre`, `chancery`, `livery`, `exemplar`, `muster`, and `archetype`. Several of those are dead reservations rather than live projects, and PEP 541 reclaim is slow enough that I treated every taken name as unusable. ``` Verified free 2026-08-25T17:38:43Z (json=404 simple=404) eutectic charter regalia armorial investiture personae Verified free earlier in the same session emblazon cadency hatchment escutcheon lozenge quartering impalement dimidiation azeotrope nucleate antumbra umbrage aniline touchmark insignia commission asterism quadrum chapter ordinance concordat mien chancellery consistory prothonotary collegium sodality vexillum phalera lictor comitia choragus haecceity quiddity individuation imposition pecia rubricator repertory playbill indenture roving sliver carding distaff warpweft plyworks rosterloom meldkit strandweave ``` ## What I am not deciding * **The pick.** This issue carries `autonomy/async-consult` and Kai holds the final choice. I own the recommendation, not the lock. * **The CLI verb, the import path, and whether repo and distribution names should differ.** Build decisions, handed to the platform seat. My only input is that `eutectic` is a weak command word and the `agent-compose` to `acompose` precedent already covers the split. * **The licence.** The brief's standing MIT policy applies and nothing here surfaced a reason to differ. * **Availability goes stale.** Re-verify immediately before the repository and the PyPI project are created. The commands are in the Method section above.
Author
Member

Correction on the labels note, since I checked while working the brief.

role/devrel was not blocked by stale credentials. It does not exist. The
coilyco-flight-deck org label set is readable without AWS and carries nine role
labels: role/ai, role/creator, role/design, role/director,
role/engineer, role/exec, role/human, role/ops, role/qa. The org
taxonomy and the roster's role slugs (platform, sysadmin, eval, frontend,
gamedev, tpm, devrel) are two different vocabularies. role/creator
("requires work from Content Creator role") is the nearest neighbour and is not
the same thing, so I did not apply it.

The autonomy label the brief wanted is already on the issue as
autonomy/async-consult, so the intended labeling is satisfied apart from the
role label that does not exist. I am leaving the divergence unresolved here
rather than picking a label, because reconciling the org label taxonomy with the
roster slugs is a portfolio decision rather than a devrel one.

Correction on the labels note, since I checked while working the brief. `role/devrel` was not blocked by stale credentials. It does not exist. The `coilyco-flight-deck` org label set is readable without AWS and carries nine role labels: `role/ai`, `role/creator`, `role/design`, `role/director`, `role/engineer`, `role/exec`, `role/human`, `role/ops`, `role/qa`. The org taxonomy and the roster's role slugs (`platform`, `sysadmin`, `eval`, `frontend`, `gamedev`, `tpm`, `devrel`) are two different vocabularies. `role/creator` ("requires work from Content Creator role") is the nearest neighbour and is not the same thing, so I did not apply it. The autonomy label the brief wanted is already on the issue as `autonomy/async-consult`, so the intended labeling is satisfied apart from the role label that does not exist. I am leaving the divergence unresolved here rather than picking a label, because reconciling the org label taxonomy with the roster slugs is a portfolio decision rather than a devrel one.
Author
Member

Addendum: the charter family, after Kai's note

Kai's response to the recommendation above: bare charter will collide with
ordinary sentence wording all over the place, and it needs a prefix or a suffix.
That is the vocabulary-collision cost I listed as charter's second problem, read
as decisive rather than tolerable. Fair. Here is the charter family, checked the
same way.

Revised recommendation in this family: charterwright

A wright is a maker, and the pattern is load-bearing English: shipwright,
wheelwright, playwright, millwright, boatwright. charterwright is a coined
compound on that pattern rather than a historical trade, and I am flagging that
rather than dressing it up as one. It reads correctly on first sight anyway,
because the suffix does the work.

It fixes both of the problems bare charter has, not just the one Kai named.

  • Prose collision, solved. Nobody writes "charterwright" in an ordinary
    sentence, so the word only ever means the product.
  • Circularity, solved. The engine and the artifact stop sharing a name. The
    charterwright composes each seat's charter. That sentence works, and "charter
    composes each seat's charter" never did.
  • Genre collision, solved. charter is a category noun in this niche.
    charterwright is not, and cannot become one, because it names a maker rather
    than a document.
  • Position preserved. A wright is the principal, never the accessory. It
    cannot be heard as a plugin to acompose.

Availability, checked 2026-08-25:

  • PyPI - free, charterwright and charter-wright, json 404 and simple 404 on
    both.
  • GitHub - zero repositories. Not "none notable", zero.
  • Web - no company, product, or person under that spelling.
  • Forgejo and the GitHub mirror - repository name free.

What it claims. This is the thing that makes charters. It constitutes agents
and bounds their powers, and it is the maker rather than the document.
What it forecloses. The eval half, silently, the same way charter did. It
also carries one small hazard I would rather name than discover later: heard
aloud, "wright" is a homophone of "write" and "right", and read quickly it sits
near the surname Cartwright.

Also free in this family, and what is wrong with each

  • chartersmith - the same move with a commoner suffix and no wright/write
    homophone. GitHub carries only a dead 2021 club repo and a username. It is the
    safe second choice. It costs a little dignity, because -smith is well worn in
    software naming (Metalsmith, Wordsmith, Codesmith) and reads slightly agency-ish.
  • chartulary - a real word, and the exact right one. A chartulary is the book
    into which an institution copied all its charters. Rejected on two counts. The
    alternate spelling cartulary is already taken on PyPI, so every typo lands on
    someone else's package, and Cavinee/Chartulary on GitHub was created
    2026-08-21 as a multi-agent repository analysis tool. Same niche, four days old.
  • charterworks - free on PyPI and not free in the world. "Charter"
    (@charterworks) is a live workplace-transformation company on LinkedIn, X, and
    Facebook. Rejected.
  • chartery - free everywhere that matters, and it amplifies the one risk bare
    charter already had. "Chartery" parses as chart plus -ery before it parses as
    charter plus -ery, and this is a Python package sitting on a shelf next to
    matplotlib and plotly.
  • charterhouse - free on PyPI, occupied hard in the world by Charterhouse
    School and Charterhouse Capital Partners. Rejected.
  • chartered - collides with prose worse than the bare word does, because
    "chartered" is live professional English. Rejected on Kai's own criterion.
  • chartula, charterium, charterite, magnacharter, procharter,
    charterage, chartry, charterhall, charterwork, chartermaker - all free
    on PyPI, all rejected. The Latin diminutive inverts the authority claim, the
    coined ones read as minerals or supplements, and chartermaker puts "chart
    maker" straight back in the reader's mouth.

eutectic from the comment above stays on the table as the answer that declines
to fight the word at all.

## Addendum: the charter family, after Kai's note Kai's response to the recommendation above: bare `charter` will collide with ordinary sentence wording all over the place, and it needs a prefix or a suffix. That is the vocabulary-collision cost I listed as charter's second problem, read as decisive rather than tolerable. Fair. Here is the charter family, checked the same way. ### Revised recommendation in this family: `charterwright` A wright is a maker, and the pattern is load-bearing English: shipwright, wheelwright, playwright, millwright, boatwright. `charterwright` is a coined compound on that pattern rather than a historical trade, and I am flagging that rather than dressing it up as one. It reads correctly on first sight anyway, because the suffix does the work. It fixes both of the problems bare `charter` has, not just the one Kai named. * **Prose collision, solved.** Nobody writes "charterwright" in an ordinary sentence, so the word only ever means the product. * **Circularity, solved.** The engine and the artifact stop sharing a name. The charterwright composes each seat's charter. That sentence works, and "charter composes each seat's charter" never did. * **Genre collision, solved.** `charter` is a category noun in this niche. `charterwright` is not, and cannot become one, because it names a maker rather than a document. * **Position preserved.** A wright is the principal, never the accessory. It cannot be heard as a plugin to `acompose`. Availability, checked 2026-08-25: * PyPI - free, `charterwright` and `charter-wright`, json 404 and simple 404 on both. * GitHub - zero repositories. Not "none notable", zero. * Web - no company, product, or person under that spelling. * Forgejo and the GitHub mirror - repository name free. **What it claims.** This is the thing that makes charters. It constitutes agents and bounds their powers, and it is the maker rather than the document. **What it forecloses.** The eval half, silently, the same way `charter` did. It also carries one small hazard I would rather name than discover later: heard aloud, "wright" is a homophone of "write" and "right", and read quickly it sits near the surname Cartwright. ### Also free in this family, and what is wrong with each * `chartersmith` - the same move with a commoner suffix and no wright/write homophone. GitHub carries only a dead 2021 club repo and a username. It is the safe second choice. It costs a little dignity, because `-smith` is well worn in software naming (Metalsmith, Wordsmith, Codesmith) and reads slightly agency-ish. * `chartulary` - a real word, and the exact right one. A chartulary is the book into which an institution copied all its charters. Rejected on two counts. The alternate spelling `cartulary` is already taken on PyPI, so every typo lands on someone else's package, and `Cavinee/Chartulary` on GitHub was created 2026-08-21 as a multi-agent repository analysis tool. Same niche, four days old. * `charterworks` - free on PyPI and not free in the world. "Charter" (`@charterworks`) is a live workplace-transformation company on LinkedIn, X, and Facebook. Rejected. * `chartery` - free everywhere that matters, and it amplifies the one risk bare `charter` already had. "Chartery" parses as chart plus -ery before it parses as charter plus -ery, and this is a Python package sitting on a shelf next to matplotlib and plotly. * `charterhouse` - free on PyPI, occupied hard in the world by Charterhouse School and Charterhouse Capital Partners. Rejected. * `chartered` - collides with prose worse than the bare word does, because "chartered" is live professional English. Rejected on Kai's own criterion. * `chartula`, `charterium`, `charterite`, `magnacharter`, `procharter`, `charterage`, `chartry`, `charterhall`, `charterwork`, `chartermaker` - all free on PyPI, all rejected. The Latin diminutive inverts the authority claim, the coined ones read as minerals or supplements, and `chartermaker` puts "chart maker" straight back in the reader's mouth. `eutectic` from the comment above stays on the table as the answer that declines to fight the word at all.
Author
Member

Wider menu, after two rounds of no

Kai declined eutectic, charter, regalia, armorial, then declined
charterwright and chartersmith and asked for more options. Taking the second
rejection at face value, coined craft compounds are out, which also rules out
chartermaker, charterhouse, and the rest of that shape. Below is the full
free pool, grouped by direction, so the next round picks a direction rather than
relitigating one word.

Every name here is verified free on PyPI today against both the JSON API and the
PEP 503 simple index. In-niche GitHub and commercial checks run on the shortlist
rather than on all of these, because that is the check that killed charter,
investiture, chartulary, and charterworks after they cleared the index.

A. Latin office and authority

  • auctoritas - the Roman distinction between authority and mere power. This
    engine confers the first kind.
  • dignitas - the standing an office carries, independent of who holds it.
  • matricula - the official roll of the members of a body. The root of
    "matriculate".
  • collegium - a constituted body of colleagues holding office together. Seven
    seats, one body.
  • consistory - the council that sits as a governing body.
  • quadrum - Latin for frame or square, and the root of cadre. The frame a body
    is built on.
  • comitia - the Roman assembly, constituted by fixed divisions that each carry
    their own voice.
  • sodality - a fellowship constituted under a common rule.

B. Heraldry and the marks of identity

  • insignia and insigne - the marks that say which office someone holds.
  • escutcheon - the shield those marks are borne on.
  • cadency - the system of marks distinguishing members of one house from each
    other. Seven seats, one estate, one invariant.
  • emblazon - the act of rendering a blazon into a visible achievement.
  • dimidiation - the heraldic operation that combines two coats into one by
    halving each. Every role in the roster melds exactly two traits.
  • quartering and impalement - the other two combining operations.
  • lozenge and hatchment - the shapes a coat is borne on in particular cases.

C. Phenomenon names, which is umbra's own move

  • azeotrope - a mixture that boils at constant composition and cannot be
    separated back into its components by distillation.
  • nucleate - the act by which a new phase begins from a seed and grows.
  • asterism - the star-figure that is not an official constellation, and also
    the typographic mark.
  • aniline - the first synthetic dye, and the start of color made rather than
    found.
  • antumbra and umbrage - shadow family. Both free, and I would not take
    either, because a name from umbra's own metaphor reads as derived from umbra
    rather than as its peer.

D. Individuation

  • haecceity - thisness. The property that makes a thing this particular one
    rather than another of the same kind. Exactly what a seat has and a model does
    not.
  • quiddity - whatness. What kind of thing something is.
  • individuation - the process by which a general thing becomes a particular one.

The whole group is precise and hard to say on sight. I flagged that as
disqualifying earlier and I still think so, but it is Kai's call and the group
belongs on the menu.

E. Record, office, and process

  • indenture - a document cut so that two halves must match, which is a bundle
    digest refusing a stale source, and also the binding of a person to a role.
    Carries "indentured servitude" as its dominant American association.
  • concordat - a formal agreement between two authorities.
  • ordinance - an authoritative decree.
  • tenure and incumbency - the holding of an office.
  • repertory - a standing company that can mount any role in its book at any
    time. Sits visually close to "repository", which is a real hazard here.
  • chapter - the constituted body that governs a house and reads its rule aloud.
    Free, and hopeless to search.
  • prothonotary - the chief keeper of the record.
  • rubricator - the hand that added the headings and the color to a finished
    manuscript.
  • pecia - the authorized exemplar a university lent out to be copied from, so
    every copy descended from one approved source.
  • chancellery - the office that drafts, seals, and registers charters. Free,
    and I would not take it, because the strongest association is a head of
    government's office.

F. Animals and Norse, following mcp-beaver and Sirens

Nearly everything here is gone. Two survive.

  • chough - a red-billed crow, and crows are on Kai's list. Pronounced "chuff",
    which is a trap in print.
  • vargr - Old Norse for wolf, and wolves are on Kai's list. Also means outlaw.

G. The shape I have not offered yet

Every compound in the estate's own idiom is available, because compounds are not
squatted. agent-compose, mcp-beaver, galaxy-gen, specgen, and AOSguard
are all compounds, so the house style already permits one. The brief warned that
a compound can read as a tool rather than an authority, and that is true of
-kit, -gen, -lib, and -utils, and not true of a compound whose head noun
is itself an authority noun.

If a compound is acceptable, the space reopens completely and the constraint
stops being availability. Say the word and I will bring a set built that way
instead.

What I think I have learned, so Kai can correct it

  • Bare common words are out, because they collide with ordinary sentences.
  • Coined craft compounds are out, because charterwright and chartersmith both
    went.
  • That leaves rare real words, estate-idiom compounds, or a name from Kai's own
    reference shelf. I have covered the first, offered the second, and found the
    third nearly empty on PyPI.

If I have read any of that wrong, one sentence redirects the next round.

## Wider menu, after two rounds of no Kai declined `eutectic`, `charter`, `regalia`, `armorial`, then declined `charterwright` and `chartersmith` and asked for more options. Taking the second rejection at face value, coined craft compounds are out, which also rules out `chartermaker`, `charterhouse`, and the rest of that shape. Below is the full free pool, grouped by direction, so the next round picks a direction rather than relitigating one word. Every name here is verified free on PyPI today against both the JSON API and the PEP 503 simple index. In-niche GitHub and commercial checks run on the shortlist rather than on all of these, because that is the check that killed `charter`, `investiture`, `chartulary`, and `charterworks` after they cleared the index. ### A. Latin office and authority * `auctoritas` - the Roman distinction between authority and mere power. This engine confers the first kind. * `dignitas` - the standing an office carries, independent of who holds it. * `matricula` - the official roll of the members of a body. The root of "matriculate". * `collegium` - a constituted body of colleagues holding office together. Seven seats, one body. * `consistory` - the council that sits as a governing body. * `quadrum` - Latin for frame or square, and the root of cadre. The frame a body is built on. * `comitia` - the Roman assembly, constituted by fixed divisions that each carry their own voice. * `sodality` - a fellowship constituted under a common rule. ### B. Heraldry and the marks of identity * `insignia` and `insigne` - the marks that say which office someone holds. * `escutcheon` - the shield those marks are borne on. * `cadency` - the system of marks distinguishing members of one house from each other. Seven seats, one estate, one invariant. * `emblazon` - the act of rendering a blazon into a visible achievement. * `dimidiation` - the heraldic operation that combines two coats into one by halving each. Every role in the roster melds exactly two traits. * `quartering` and `impalement` - the other two combining operations. * `lozenge` and `hatchment` - the shapes a coat is borne on in particular cases. ### C. Phenomenon names, which is umbra's own move * `azeotrope` - a mixture that boils at constant composition and cannot be separated back into its components by distillation. * `nucleate` - the act by which a new phase begins from a seed and grows. * `asterism` - the star-figure that is not an official constellation, and also the typographic mark. * `aniline` - the first synthetic dye, and the start of color made rather than found. * `antumbra` and `umbrage` - shadow family. Both free, and I would not take either, because a name from umbra's own metaphor reads as derived from umbra rather than as its peer. ### D. Individuation * `haecceity` - thisness. The property that makes a thing this particular one rather than another of the same kind. Exactly what a seat has and a model does not. * `quiddity` - whatness. What kind of thing something is. * `individuation` - the process by which a general thing becomes a particular one. The whole group is precise and hard to say on sight. I flagged that as disqualifying earlier and I still think so, but it is Kai's call and the group belongs on the menu. ### E. Record, office, and process * `indenture` - a document cut so that two halves must match, which is a bundle digest refusing a stale source, and also the binding of a person to a role. Carries "indentured servitude" as its dominant American association. * `concordat` - a formal agreement between two authorities. * `ordinance` - an authoritative decree. * `tenure` and `incumbency` - the holding of an office. * `repertory` - a standing company that can mount any role in its book at any time. Sits visually close to "repository", which is a real hazard here. * `chapter` - the constituted body that governs a house and reads its rule aloud. Free, and hopeless to search. * `prothonotary` - the chief keeper of the record. * `rubricator` - the hand that added the headings and the color to a finished manuscript. * `pecia` - the authorized exemplar a university lent out to be copied from, so every copy descended from one approved source. * `chancellery` - the office that drafts, seals, and registers charters. Free, and I would not take it, because the strongest association is a head of government's office. ### F. Animals and Norse, following mcp-beaver and Sirens Nearly everything here is gone. Two survive. * `chough` - a red-billed crow, and crows are on Kai's list. Pronounced "chuff", which is a trap in print. * `vargr` - Old Norse for wolf, and wolves are on Kai's list. Also means outlaw. ### G. The shape I have not offered yet Every compound in the estate's own idiom is available, because compounds are not squatted. `agent-compose`, `mcp-beaver`, `galaxy-gen`, `specgen`, and `AOSguard` are all compounds, so the house style already permits one. The brief warned that a compound can read as a tool rather than an authority, and that is true of `-kit`, `-gen`, `-lib`, and `-utils`, and not true of a compound whose head noun is itself an authority noun. If a compound is acceptable, the space reopens completely and the constraint stops being availability. Say the word and I will bring a set built that way instead. ### What I think I have learned, so Kai can correct it * Bare common words are out, because they collide with ordinary sentences. * Coined craft compounds are out, because `charterwright` and `chartersmith` both went. * That leaves rare real words, estate-idiom compounds, or a name from Kai's own reference shelf. I have covered the first, offered the second, and found the third nearly empty on PyPI. If I have read any of that wrong, one sentence redirects the next round.
Author
Member

Anchored on combination, merging, coalescence

Kai's redirect: anchor on combination, merging, coalescence, and note that
coalescence itself is a word Kai can never spell right. So spellability is now
an explicit criterion rather than a tiebreaker, and if this field strikes out we
fall back to a compound in the estate idiom.

I swept the merge field hard: about 130 more candidates across English joining
words, Greek and Latin blending roots, metallurgy, joinery, grafting, winemaking
and distilling, music, linguistics, and physics. Availability checked the same
way, both PyPI surfaces, then GitHub and commercial checks on the finalists.

Reporting one thing first, because Kai named it. coalescence is free. Both
PyPI surfaces, verified today. If the meaning is worth the spelling, it is
sitting there. coalescent is free too. coalesce itself is taken.

The four I would put forward

  • eucrasia - Greek medicine for the good blend. A person's krasis was the
    mixture of humors that constituted their temperament, and eucrasia is that
    mixture correctly proportioned. It is the only word I found that means, in one
    word, "a character that is a well-composed blend." That is the product's whole
    job. Clean on GitHub, two empty repos and two usernames. Clean commercially.
    The cost is that first-sight pronunciation is ambiguous, though "eu-" and
    "-crasy" both have common English anchors in euphoria and idiosyncrasy.
  • azeotrope - a mixture that boils at constant composition, so distillation
    cannot pull it back apart. It claims something specific and true about a meld:
    once composed, not decomposable. Clean on GitHub, two chemistry student
    projects. Spellable. The cost is that it shares a shelf with eutectic, which
    already missed, so it may be the wrong shelf rather than the wrong word.
  • mixis - Greek for mixing, and in biology the term for recombination as
    opposed to apomixis, reproduction without mixing. Five letters, two
    syllables, nothing to misspell. It is the most umbra-shaped name in the whole
    search, and it says the anchor word plainly. The cost is real and specific: it
    is one letter from mixin, which is a live Python concept, and this is a
    Python package.
  • entrainment - two oscillators running at different rhythms lock into one
    shared rhythm while remaining two separate objects. Huygens' clocks. That is
    the most accurate physical model of a meld I found, and it is trivially
    spellable. The cost is the neighbourhood: GitHub carries 192 entrainment repos
    and the loudest cluster is EEG neurofeedback and brainwave entrainment, which
    is a wellness-adjacent association I would rather not stand next to.

Also free, and why each is a tier down

  • syncrasis - the root of idiosyncrasy, syn plus krasis, a blending
    together. Dead on the anchor and easy to spell. Read quickly it shows you
    "crisis", which is why it is not in the four.
  • syncretism and syncretic - combining distinct traditions into one coherent
    system. Very good on doctrine melding. Academic, four syllables, and carries a
    faint pejorative edge in theology.
  • suture - the seam where two things join and heal into one continuous
    structure. Short and spellable. Names the seam rather than the whole, and
    carries a wound.
  • concrescence - Whitehead's term for many entities becoming one entity, which
    is this product stated as metaphysics. Rejected on Kai's own criterion, because
    it is the same spelling trap as coalescence.
  • commingle, commixture, coadunate, coadunation, compaginate,
    amalgamation, conjoin, conjoint, congruity, juncture, interlace,
    adduct, adhere, chelate, agglomerate, hybridize, incorporate,
    marry, grafting, inosculate, agglutinate, syneresis, portmanteau,
    lamella, weldment, jointure, conjuncture, integrant, nucleate,
    dimidiation, attunement, syntony, syntonic, descant, antiphon,
    heterophony, magistery, spagyric, holism, synergism, eurhythmy,
    communion, vatting, cuvee, eucrasia - all free on PyPI today.

Checked and killed after clearing PyPI

Worth recording, because the index said yes and the world said no.

  • solera - the fractional blending system where every bottle carries a trace of
    every year. Best system metaphor in the sweep. Solera Holdings is a large
    software company under Vista Equity Partners, operating in 75 countries, and
    its offerings include digital identification services. Direct software
    collision, on identity. Dead.
  • sangam - Sanskrit for the confluence of rivers, trivially spellable, exactly
    on the anchor. Killed on two counts. It is a common given name and a busy term
    in Indian tech naming, so it is noisy, and the primary referent is the sacred
    Triveni Sangam. Taking a sacred term from a tradition the estate has no
    relationship to, for an agent tooling product, is not a thing I will recommend.
  • chartulary, charterworks, charter, investiture - killed earlier in this
    thread on in-niche and commercial occupation.

If this strikes out

The compound fallback is ready and the constraint changes completely, because
compounds are not squatted. Say so and I will bring a set built as
<authority noun> compounds in the house style rather than scraped from what
single words are left.

## Anchored on combination, merging, coalescence Kai's redirect: anchor on combination, merging, coalescence, and note that `coalescence` itself is a word Kai can never spell right. So spellability is now an explicit criterion rather than a tiebreaker, and if this field strikes out we fall back to a compound in the estate idiom. I swept the merge field hard: about 130 more candidates across English joining words, Greek and Latin blending roots, metallurgy, joinery, grafting, winemaking and distilling, music, linguistics, and physics. Availability checked the same way, both PyPI surfaces, then GitHub and commercial checks on the finalists. Reporting one thing first, because Kai named it. **`coalescence` is free.** Both PyPI surfaces, verified today. If the meaning is worth the spelling, it is sitting there. `coalescent` is free too. `coalesce` itself is taken. ### The four I would put forward * **`eucrasia`** - Greek medicine for the good blend. A person's `krasis` was the mixture of humors that constituted their temperament, and `eucrasia` is that mixture correctly proportioned. It is the only word I found that means, in one word, "a character that is a well-composed blend." That is the product's whole job. Clean on GitHub, two empty repos and two usernames. Clean commercially. The cost is that first-sight pronunciation is ambiguous, though "eu-" and "-crasy" both have common English anchors in euphoria and idiosyncrasy. * **`azeotrope`** - a mixture that boils at constant composition, so distillation cannot pull it back apart. It claims something specific and true about a meld: once composed, not decomposable. Clean on GitHub, two chemistry student projects. Spellable. The cost is that it shares a shelf with `eutectic`, which already missed, so it may be the wrong shelf rather than the wrong word. * **`mixis`** - Greek for mixing, and in biology the term for recombination as opposed to `apomixis`, reproduction without mixing. Five letters, two syllables, nothing to misspell. It is the most umbra-shaped name in the whole search, and it says the anchor word plainly. The cost is real and specific: it is one letter from `mixin`, which is a live Python concept, and this is a Python package. * **`entrainment`** - two oscillators running at different rhythms lock into one shared rhythm while remaining two separate objects. Huygens' clocks. That is the most accurate physical model of a meld I found, and it is trivially spellable. The cost is the neighbourhood: GitHub carries 192 entrainment repos and the loudest cluster is EEG neurofeedback and brainwave entrainment, which is a wellness-adjacent association I would rather not stand next to. ### Also free, and why each is a tier down * `syncrasis` - the root of idiosyncrasy, `syn` plus `krasis`, a blending together. Dead on the anchor and easy to spell. Read quickly it shows you "crisis", which is why it is not in the four. * `syncretism` and `syncretic` - combining distinct traditions into one coherent system. Very good on doctrine melding. Academic, four syllables, and carries a faint pejorative edge in theology. * `suture` - the seam where two things join and heal into one continuous structure. Short and spellable. Names the seam rather than the whole, and carries a wound. * `concrescence` - Whitehead's term for many entities becoming one entity, which is this product stated as metaphysics. Rejected on Kai's own criterion, because it is the same spelling trap as coalescence. * `commingle`, `commixture`, `coadunate`, `coadunation`, `compaginate`, `amalgamation`, `conjoin`, `conjoint`, `congruity`, `juncture`, `interlace`, `adduct`, `adhere`, `chelate`, `agglomerate`, `hybridize`, `incorporate`, `marry`, `grafting`, `inosculate`, `agglutinate`, `syneresis`, `portmanteau`, `lamella`, `weldment`, `jointure`, `conjuncture`, `integrant`, `nucleate`, `dimidiation`, `attunement`, `syntony`, `syntonic`, `descant`, `antiphon`, `heterophony`, `magistery`, `spagyric`, `holism`, `synergism`, `eurhythmy`, `communion`, `vatting`, `cuvee`, `eucrasia` - all free on PyPI today. ### Checked and killed after clearing PyPI Worth recording, because the index said yes and the world said no. * `solera` - the fractional blending system where every bottle carries a trace of every year. Best system metaphor in the sweep. **Solera Holdings** is a large software company under Vista Equity Partners, operating in 75 countries, and its offerings include digital identification services. Direct software collision, on identity. Dead. * `sangam` - Sanskrit for the confluence of rivers, trivially spellable, exactly on the anchor. Killed on two counts. It is a common given name and a busy term in Indian tech naming, so it is noisy, and the primary referent is the sacred Triveni Sangam. Taking a sacred term from a tradition the estate has no relationship to, for an agent tooling product, is not a thing I will recommend. * `chartulary`, `charterworks`, `charter`, `investiture` - killed earlier in this thread on in-niche and commercial occupation. ### If this strikes out The compound fallback is ready and the constraint changes completely, because compounds are not squatted. Say so and I will bring a set built as `<authority noun>` compounds in the house style rather than scraped from what single words are left.
Author
Member

compo-seer, checked

Kai floated it in chat. It is available in every spelling: composeer,
compo-seer, compseer, composeur, composeers, all 404 on both PyPI
surfaces today.

It still dies, and the evidence is unusually clean. GitHub returns exactly
four repositories matching composeer, and all four are misspellings of
Composer. One is a PHP Composer course. The string already exists in the world
only as a typo for something else. Spoken aloud the pun disappears entirely and
the name is "composer", which is PHP's package manager, plus Google Cloud
Composer, with Docker Compose next door. A product name that cannot survive being
said out loud is not a product name.

The insight underneath it is right, and it exposes a gap in my own work. The
joke is compose plus see. This product composes a bundle and then grades what it
composed, and that second half is what keeps the graded artifact and the shipped
artifact identical. Every candidate I have put forward so far forecloses it.
eutectic, charter, regalia, eucrasia, azeotrope, mixis, and
entrainment all say only that things combine. I listed that foreclosure each
time and never treated it as a reason to look further. That was the wrong call
and the joke caught it.

So the brief sharpens: the name should carry compose and judge.

The perfect words for it are gone. assay sets the composition and tests it.
assize is both the statute fixing a standard and the sitting that judges
against it. muster is both the assembling of a body and the inspection that
body must pass. proof is the impression pulled from composed type and the act
of checking it. All four taken.

What survives, verified free today:

  • proofhouse - the statutory authority that test-fires every barrel before it
    may be sold and stamps it with a proof mark. A constituted authority by
    definition, never a helper, and the proof mark maps directly onto the bundle
    digest. The cost is that a proof house is a firearms institution, and that
    association comes with the name.
  • commissioning - in engineering, bringing a system into service and verifying
    it performs as designed. It also carries the other sense, conferring an office
    on someone, which is the charter meaning. Two of the three things this product
    does, in one word. The cost is four syllables and a gerund, and sales
    commission as noise.
  • qualification - proving a part against spec before it ships. Reads as
    credentialing rather than composition.
  • visitation - the formal inspection of a house by the authority that
    constituted it. Reads as custody law and ghosts.
  • cupellation - the assay process itself, in the cupel. Precise, obscure, and
    four syllables of chemistry.
  • foreseer and scryer - the seer half alone, without the compose half.

None of these is a recommendation yet. Recording them so the sharpened brief is
durable rather than living in chat.

## `compo-seer`, checked Kai floated it in chat. It is available in every spelling: `composeer`, `compo-seer`, `compseer`, `composeur`, `composeers`, all 404 on both PyPI surfaces today. **It still dies, and the evidence is unusually clean.** GitHub returns exactly four repositories matching `composeer`, and all four are misspellings of Composer. One is a PHP Composer course. The string already exists in the world only as a typo for something else. Spoken aloud the pun disappears entirely and the name is "composer", which is PHP's package manager, plus Google Cloud Composer, with Docker Compose next door. A product name that cannot survive being said out loud is not a product name. **The insight underneath it is right, and it exposes a gap in my own work.** The joke is compose plus see. This product composes a bundle and then grades what it composed, and that second half is what keeps the graded artifact and the shipped artifact identical. Every candidate I have put forward so far forecloses it. `eutectic`, `charter`, `regalia`, `eucrasia`, `azeotrope`, `mixis`, and `entrainment` all say only that things combine. I listed that foreclosure each time and never treated it as a reason to look further. That was the wrong call and the joke caught it. So the brief sharpens: the name should carry compose **and** judge. The perfect words for it are gone. `assay` sets the composition and tests it. `assize` is both the statute fixing a standard and the sitting that judges against it. `muster` is both the assembling of a body and the inspection that body must pass. `proof` is the impression pulled from composed type and the act of checking it. All four taken. What survives, verified free today: * `proofhouse` - the statutory authority that test-fires every barrel before it may be sold and stamps it with a proof mark. A constituted authority by definition, never a helper, and the proof mark maps directly onto the bundle digest. The cost is that a proof house is a firearms institution, and that association comes with the name. * `commissioning` - in engineering, bringing a system into service and verifying it performs as designed. It also carries the other sense, conferring an office on someone, which is the charter meaning. Two of the three things this product does, in one word. The cost is four syllables and a gerund, and sales commission as noise. * `qualification` - proving a part against spec before it ships. Reads as credentialing rather than composition. * `visitation` - the formal inspection of a house by the authority that constituted it. Reads as custody law and ghosts. * `cupellation` - the assay process itself, in the cupel. Precise, obscure, and four syllables of chemistry. * `foreseer` and `scryer` - the seer half alone, without the compose half. None of these is a recommendation yet. Recording them so the sharpened brief is durable rather than living in chat.
Author
Member

The compose-and-judge field, swept

About 90 more candidates across three rounds: assaying and hallmarking, gun and
barrel proof, typesetting proofs, guild masterpieces, vetting for office,
engineering qualification, coin trial, law, textual criticism, and inspection
offices. Both PyPI surfaces on everything, then GitHub and web on the finalists.

First, a control. I re-verified the checker against nonsense strings mid-sweep
because two results looked wrong. zzqxwvfake123 and blorptangle9 both return
404 on both surfaces, so the tooling is sound and the surprising results below
are real.

The finding that matters beyond this name

The precise-obscure-word vein is being actively mined by AI agent tooling right
now.
Seven independent projects, all from 2026, all reaching for exactly this
register for exactly the reasons we are:

  • dokimasia - deevus/dokimasia, "Pytest-first acceptance testing for agent
    capabilities", Python, created 2026-05-15. This was the best word in the entire
    search. The Athenian examination of a citizen's fitness before they may hold
    office, and the same word in metallurgy for assaying metal. Someone else got
    there in May.
  • euthyna - Euthyna/Euthyna, "a local audit gateway for AI coding agents",
    Python, created 2026-07-22. The Athenian counterpart to dokimasia, the audit
    every official faced on leaving office.
  • vidimus - on PyPI since 2026, "verifiable custody of agent-produced records:
    chained manifests, dual RFC 3161 witnesses, pinned Ed25519".
  • inspeximus - on PyPI, version 2.20.1, 114 releases, last shipped 2026-08-14.
    "Agent memory that does not serve stale facts."
  • charter - meta-llm-charter, 249 stars, updated 2026-08-25.
  • investiture - erikaflowers/investiture, Claude Code doctrine scaffold,
    created 2026-01-31.
  • chartulary - Cavinee/Chartulary, multi-agent repository analysis, created
    2026-08-21.

Four of those seven cleared PyPI and died on the GitHub check, which is why I run
it. The practical consequence: this vein has months, not years. Whatever gets
picked is worth locking soon, and I would register the PyPI name the day it is
chosen rather than the day the repository is ready.

The four that survived

  • alnage - my pick of the four. Alnage was the Crown regime, from Edward I
    to William III, that set the standard for woollen cloth, had a sworn officer
    measure every piece against it, and affixed a seal certifying size and quality
    before it could be sold. Setting a standard and certifying conformance against
    it, as one institution, is compose-and-judge exactly. Six letters, two
    syllables, nothing to misspell. Zero software collisions on PyPI, GitHub, or
    the web. It also reconnects quietly to the fiber register the brief opened with
    without being a loom word. Costs: it is unfamiliar, it has two plausible
    pronunciations, and the string shows up on GitHub as an Arabic surname
    transliteration, so search is slightly noisy.
  • homologation - the official certification that a produced thing conforms
    to the approved specification, so it may be entered or sold. It maps directly
    onto the brief's own sentence about keeping the graded artifact and the shipped
    artifact identical. Trivially spellable. Clean in-niche: 98 GitHub repos, all
    automotive and telecom compliance, none above two stars, none in the agent
    space. Costs: five syllables, and it reads regulatory.
  • assaymaster - the officer of an assay office who assays metal and
    certifies its fineness. This recovers assay, which was the single best word
    in the whole search and is taken, by making it a compound in the house style.
    Zero GitHub hits. Plain English, unambiguous, real historical title rather than
    a coinage. Costs: it is a compound, and "master" is a word some projects now
    avoid.
  • chirograph - a document written out twice on one sheet with a word
    between, then cut apart, so the two halves must match to prove authenticity. It
    is the indenture idea without the servitude connotation, and it maps onto the
    bundle digest refusing a stale source. Costs: the chi is pronounced "kai",
    which is a trap in print, and it carries proving rather than composing. One
    adjacent Go library at five stars.

Also free in this field, and why each is a tier down

docimasy (the English form of dokimasia, free, but the Greek form is now
occupied in this exact niche and the association follows), homologate,
alnager, aulnage, aulnager, commissioning, qualification,
cupellation, proofhouse (firearms), lustrum (the census-closing rite, and
it has "lust" in it), muniment (names the artifact, not the act),
scrutinium, scrutator, agonothete, athlothete, novitiate,
noviciate, approbation, ratification, engrossment, exemplification,
counterpart, estreat, testator, sealer, garbler, saggar, viewhouse,
gauger, empanelment, venire, oyer, voirdire, probate, probation,
visitation, quaestio, censura, cognitio, spectatio, recensio,
collation, emendation, dokimion, dokimos, krites, logistai,
peirasmos, probative, dramaturgy, dramaturge, typeapproval,
nihilobstat, foreseer, scryer, glost, proving.

Taken, and worth recording because they were the best answers

assay, assize, muster, proof, pyx, pyxis, examen, probity,
elenchus, recension, touchstone, hallmark, crucible, refiner,
prover, assayer, scrutiny, rehearsal, audition, masterpiece,
journeyman, conformance, proofmark, kiln, bisque, tally, imprimatur.

assize is the one that still stings. One word meaning both the statute that
fixes a standard and the sitting of the court that judges against it.

## The compose-and-judge field, swept About 90 more candidates across three rounds: assaying and hallmarking, gun and barrel proof, typesetting proofs, guild masterpieces, vetting for office, engineering qualification, coin trial, law, textual criticism, and inspection offices. Both PyPI surfaces on everything, then GitHub and web on the finalists. First, a control. I re-verified the checker against nonsense strings mid-sweep because two results looked wrong. `zzqxwvfake123` and `blorptangle9` both return 404 on both surfaces, so the tooling is sound and the surprising results below are real. ### The finding that matters beyond this name **The precise-obscure-word vein is being actively mined by AI agent tooling right now.** Seven independent projects, all from 2026, all reaching for exactly this register for exactly the reasons we are: * `dokimasia` - `deevus/dokimasia`, "Pytest-first acceptance testing for agent capabilities", Python, created 2026-05-15. This was the best word in the entire search. The Athenian examination of a citizen's fitness before they may hold office, and the same word in metallurgy for assaying metal. Someone else got there in May. * `euthyna` - `Euthyna/Euthyna`, "a local audit gateway for AI coding agents", Python, created 2026-07-22. The Athenian counterpart to dokimasia, the audit every official faced on leaving office. * `vidimus` - on PyPI since 2026, "verifiable custody of agent-produced records: chained manifests, dual RFC 3161 witnesses, pinned Ed25519". * `inspeximus` - on PyPI, version 2.20.1, 114 releases, last shipped 2026-08-14. "Agent memory that does not serve stale facts." * `charter` - `meta-llm-charter`, 249 stars, updated 2026-08-25. * `investiture` - `erikaflowers/investiture`, Claude Code doctrine scaffold, created 2026-01-31. * `chartulary` - `Cavinee/Chartulary`, multi-agent repository analysis, created 2026-08-21. Four of those seven cleared PyPI and died on the GitHub check, which is why I run it. The practical consequence: this vein has months, not years. Whatever gets picked is worth locking soon, and I would register the PyPI name the day it is chosen rather than the day the repository is ready. ### The four that survived * **`alnage`** - my pick of the four. Alnage was the Crown regime, from Edward I to William III, that set the standard for woollen cloth, had a sworn officer measure every piece against it, and affixed a seal certifying size and quality before it could be sold. Setting a standard and certifying conformance against it, as one institution, is compose-and-judge exactly. Six letters, two syllables, nothing to misspell. Zero software collisions on PyPI, GitHub, or the web. It also reconnects quietly to the fiber register the brief opened with without being a loom word. Costs: it is unfamiliar, it has two plausible pronunciations, and the string shows up on GitHub as an Arabic surname transliteration, so search is slightly noisy. * **`homologation`** - the official certification that a produced thing conforms to the approved specification, so it may be entered or sold. It maps directly onto the brief's own sentence about keeping the graded artifact and the shipped artifact identical. Trivially spellable. Clean in-niche: 98 GitHub repos, all automotive and telecom compliance, none above two stars, none in the agent space. Costs: five syllables, and it reads regulatory. * **`assaymaster`** - the officer of an assay office who assays metal and certifies its fineness. This recovers `assay`, which was the single best word in the whole search and is taken, by making it a compound in the house style. Zero GitHub hits. Plain English, unambiguous, real historical title rather than a coinage. Costs: it is a compound, and "master" is a word some projects now avoid. * **`chirograph`** - a document written out twice on one sheet with a word between, then cut apart, so the two halves must match to prove authenticity. It is the indenture idea without the servitude connotation, and it maps onto the bundle digest refusing a stale source. Costs: the `chi` is pronounced "kai", which is a trap in print, and it carries proving rather than composing. One adjacent Go library at five stars. ### Also free in this field, and why each is a tier down `docimasy` (the English form of dokimasia, free, but the Greek form is now occupied in this exact niche and the association follows), `homologate`, `alnager`, `aulnage`, `aulnager`, `commissioning`, `qualification`, `cupellation`, `proofhouse` (firearms), `lustrum` (the census-closing rite, and it has "lust" in it), `muniment` (names the artifact, not the act), `scrutinium`, `scrutator`, `agonothete`, `athlothete`, `novitiate`, `noviciate`, `approbation`, `ratification`, `engrossment`, `exemplification`, `counterpart`, `estreat`, `testator`, `sealer`, `garbler`, `saggar`, `viewhouse`, `gauger`, `empanelment`, `venire`, `oyer`, `voirdire`, `probate`, `probation`, `visitation`, `quaestio`, `censura`, `cognitio`, `spectatio`, `recensio`, `collation`, `emendation`, `dokimion`, `dokimos`, `krites`, `logistai`, `peirasmos`, `probative`, `dramaturgy`, `dramaturge`, `typeapproval`, `nihilobstat`, `foreseer`, `scryer`, `glost`, `proving`. ### Taken, and worth recording because they were the best answers `assay`, `assize`, `muster`, `proof`, `pyx`, `pyxis`, `examen`, `probity`, `elenchus`, `recension`, `touchstone`, `hallmark`, `crucible`, `refiner`, `prover`, `assayer`, `scrutiny`, `rehearsal`, `audition`, `masterpiece`, `journeyman`, `conformance`, `proofmark`, `kiln`, `bisque`, `tally`, `imprimatur`. `assize` is the one that still stings. One word meaning both the statute that fixes a standard and the sitting of the court that judges against it.
Author
Member

Familiar words, which means compounds

Kai's note on the compose-and-judge shortlist: "I haven't heard of any of those
terms." That is the criterion I had been under-weighting through this whole
thread, and it invalidates the approach rather than the shortlist. alnage,
dokimasia, homologation, chirograph, eucrasia, azeotrope, escutcheon,
and most of what I have put forward are words a reader meets for the first time
at the product. A name that needs a glossary entry is a name that is doing the
opposite of its job.

The wall, stated plainly

Every familiar single word on the anchor is taken. Verified today, both surfaces:
merge, blend, meld, mix, alloy, weld, knit, unite, combine,
fuse, join, splice, graft, braid, seam, amalgam, coalesce,
mint, cast, forge, smithy, bindery. Also gone are assay, proof,
muster, hallmark, touchstone, crucible.

So there is no familiar single word available. That is not a failure of searching
harder, it is the shape of PyPI in 2026. Which leaves compounds, and every
compound is free, because nobody squats compounds.

This is also the house style. agent-compose, mcp-beaver, galaxy-gen,
AOSguard, Agent Proxy, Sirens Echo are all compounds. The two Kai passed on
earlier, charterwright and chartersmith, were coined craft-words, which is a
different thing from two plain nouns.

Recommendation: rolemint

Repo rolemint, PyPI rolemint, import rolemint. Verified free
2026-08-25T18:37:15Z on both PyPI surfaces, in bare and hyphenated form, and
zero GitHub repositories match it.

Both halves are words anyone has heard. That is the point.

What a mint actually does is this entire product, which is why the metaphor
carries further than any single word I found:

  • It composes raw material into an alloy of a fixed standard.
  • It strikes each piece with a device carrying identity marks, and a mint mark
    saying which authority issued it.
  • It has its output assayed. The Trial of the Pyx has sampled Royal Mint coin
    before a jury since the twelfth century, and it is the oldest continuous
    judicial procedure in England.
  • What it issues is authoritative because the mint issued it, not because
    anything downstream approved it.

That last line is the structural claim the brief asked for, in one sentence. A
mint is upstream by definition. Nothing about rolemint can be heard as a plugin,
an adapter, or an accessory to acompose.

What it claims. This is where roles are made authoritative. It composes them
to a standard, strikes their identity onto them, and grades what it struck.
What it forecloses. Not much, which is unusual in this thread. It is quieter
than a single evocative word, so it will never be as striking as umbra on a
page. And "mint" in 2026 carries a crypto sense, minting a token, which sits
adjacent whether or not we want it. Linux Mint and Mint.com exist and neither
collides with the compound.

Alternates

  • rolecast - casting a play, which is deciding who plays which role, and
    casting metal, which is pouring a composed melt into a permanent form. Both
    senses are exactly this product and both words are dead familiar. Free on PyPI
    in both forms, and GitHub carries only two empty zero-star repositories. The
    cost is that cast is a live programming concept, so a Python package named
    rolecast invites a type-conversion reading, and the word sits near
    "broadcast" and "podcast".
  • meldbench - a bench is where a craftsperson makes the thing, and the
    Bench is where judgment is delivered. One familiar word carrying compose and
    judge at once, and "bench" also reads as benchmark, which is the eval half.
    Free, zero GitHub hits. The cost is that meld is estate vocabulary rather
    than general vocabulary, so it is familiar to Kai and not to a new reader.
  • mintage - the single-word version of the mint idea, meaning both the act
    of minting and what it produced. Two syllables, transparent from "mint" even
    if unfamiliar. Free on PyPI. The cost is that GitHub's mintage results are
    mostly Linux Mint customization scripts, so the association drags toward the
    distro.

Also free, if the shape is right but the words are not

rolemark, roleseal, rolepress, rolebench, roleboard, roleframe,
rolecore, rostermint, rostercast, seatmint, seatcast, meldmint,
meldcast, meldmark, meldseal, meldpress, meldboard, meldhouse,
meldworks, casthouse, castmark, castworks, castframe, minthouse,
mintworks, mintline, truecast, strikemark, pressroom, castingroom.

Note that roleboard collides with internal vocabulary, since the roster-derived
behavior matrix is already called the board.

## Familiar words, which means compounds Kai's note on the compose-and-judge shortlist: "I haven't heard of any of those terms." That is the criterion I had been under-weighting through this whole thread, and it invalidates the approach rather than the shortlist. `alnage`, `dokimasia`, `homologation`, `chirograph`, `eucrasia`, `azeotrope`, `escutcheon`, and most of what I have put forward are words a reader meets for the first time at the product. A name that needs a glossary entry is a name that is doing the opposite of its job. ### The wall, stated plainly Every familiar single word on the anchor is taken. Verified today, both surfaces: `merge`, `blend`, `meld`, `mix`, `alloy`, `weld`, `knit`, `unite`, `combine`, `fuse`, `join`, `splice`, `graft`, `braid`, `seam`, `amalgam`, `coalesce`, `mint`, `cast`, `forge`, `smithy`, `bindery`. Also gone are `assay`, `proof`, `muster`, `hallmark`, `touchstone`, `crucible`. So there is no familiar single word available. That is not a failure of searching harder, it is the shape of PyPI in 2026. Which leaves compounds, and every compound is free, because nobody squats compounds. This is also the house style. `agent-compose`, `mcp-beaver`, `galaxy-gen`, `AOSguard`, `Agent Proxy`, `Sirens Echo` are all compounds. The two Kai passed on earlier, `charterwright` and `chartersmith`, were coined craft-words, which is a different thing from two plain nouns. ### Recommendation: `rolemint` Repo `rolemint`, PyPI `rolemint`, import `rolemint`. Verified free 2026-08-25T18:37:15Z on both PyPI surfaces, in bare and hyphenated form, and **zero GitHub repositories** match it. Both halves are words anyone has heard. That is the point. **What a mint actually does** is this entire product, which is why the metaphor carries further than any single word I found: * It composes raw material into an alloy of a fixed standard. * It strikes each piece with a device carrying identity marks, and a mint mark saying which authority issued it. * It has its output assayed. The Trial of the Pyx has sampled Royal Mint coin before a jury since the twelfth century, and it is the oldest continuous judicial procedure in England. * What it issues is authoritative **because the mint issued it**, not because anything downstream approved it. That last line is the structural claim the brief asked for, in one sentence. A mint is upstream by definition. Nothing about `rolemint` can be heard as a plugin, an adapter, or an accessory to `acompose`. **What it claims.** This is where roles are made authoritative. It composes them to a standard, strikes their identity onto them, and grades what it struck. **What it forecloses.** Not much, which is unusual in this thread. It is quieter than a single evocative word, so it will never be as striking as `umbra` on a page. And "mint" in 2026 carries a crypto sense, minting a token, which sits adjacent whether or not we want it. Linux Mint and Mint.com exist and neither collides with the compound. ### Alternates * **`rolecast`** - casting a play, which is deciding who plays which role, and casting metal, which is pouring a composed melt into a permanent form. Both senses are exactly this product and both words are dead familiar. Free on PyPI in both forms, and GitHub carries only two empty zero-star repositories. The cost is that `cast` is a live programming concept, so a Python package named `rolecast` invites a type-conversion reading, and the word sits near "broadcast" and "podcast". * **`meldbench`** - a bench is where a craftsperson makes the thing, and the Bench is where judgment is delivered. One familiar word carrying compose and judge at once, and "bench" also reads as benchmark, which is the eval half. Free, zero GitHub hits. The cost is that `meld` is estate vocabulary rather than general vocabulary, so it is familiar to Kai and not to a new reader. * **`mintage`** - the single-word version of the mint idea, meaning both the act of minting and what it produced. Two syllables, transparent from "mint" even if unfamiliar. Free on PyPI. The cost is that GitHub's `mintage` results are mostly Linux Mint customization scripts, so the association drags toward the distro. ### Also free, if the shape is right but the words are not `rolemark`, `roleseal`, `rolepress`, `rolebench`, `roleboard`, `roleframe`, `rolecore`, `rostermint`, `rostercast`, `seatmint`, `seatcast`, `meldmint`, `meldcast`, `meldmark`, `meldseal`, `meldpress`, `meldboard`, `meldhouse`, `meldworks`, `casthouse`, `castmark`, `castworks`, `castframe`, `minthouse`, `mintworks`, `mintline`, `truecast`, `strikemark`, `pressroom`, `castingroom`. Note that `roleboard` collides with internal vocabulary, since the roster-derived behavior matrix is already called the board.
Author
Member

house-meld, proposed by Kai, checked

Availability, 2026-08-25T18:46:56Z:

  • PyPI - housemeld, house-meld, housemelds all 404 on both surfaces.
  • GitHub - zero repositories match housemeld or house-meld.
  • Web - no company or product under either spelling.

This is the best candidate in the thread, and the improvement over rolemint
is Kai's word order rather than the words.
I had offered meldhouse in the
free-compound list and it reads as a facility. house-meld reads as a natural
English noun phrase, the same shape as "house blend" and "house style", and the
estate's own doctrine already says house style. Flipping it is the whole fix.

What it claims

A House constitutes its members, holds one rule they all share, and grants each
one marks that distinguish them from their siblings. That is the roster exactly:
seven seats, one invariant, each with derived identity primitives. A mint issues
currency, and this product does not issue currency, it constitutes people.
house is the better authority noun and it was sitting in plain sight.

Both halves are words anyone has met, neither drifts. No crypto sense on mint,
no Linux distro, and none of the category-noun problem that killed charter. It
cannot be heard as a plugin, because a house is not an accessory to anything.

What it costs, and one of these is sharper than I would like

  • Property Meld is real software. Founded 2014, Rapid City, property
    maintenance software, listed on G2, LinkedIn, and CB Insights. So
    <dwelling word> + meld is a construction already in the software market, and
    house is a near-synonym for property. The compound housemeld itself is
    unoccupied, so this is a reading risk rather than a collision, but it is the
    thing I would want decided with eyes open.
  • house pulls toward real estate in software. A GitHub sweep of house*
    compounds comes back almost entirely housing-market projects. Same gravity that
    produced Property Meld. meld pulls against it, and it is a headwind.
  • Mild circularity. The roster's own word for combining two traits is meld,
    so "house-meld resolves each role's meld" is a live sentence. Milder than
    "charter composes charters" because the product is the compound rather than the
    bare noun, and still present.
  • Two names to hold. PyPI normalizes house-meld and house_meld to the
    same name, and housemeld is a separate name. Register both, ship one.
  • Silent on the eval half, like almost everything in this thread. A house
    putting its name on something is a guarantee, which reaches at the idea, and I
    am calling that a stretch rather than a claim.
  • meld is also a Magic: The Gathering mechanic in which two cards combine into
    one larger card, which is either a pleasing resonance or noise depending on
    taste.

Same shape, if Property Meld is disqualifying

Kai's insight was house plus natural noun-phrase order. It survives the word
change.

  • housecast - a house cast is the resident standing company of a theatre. Free
    on PyPI, and it dodges Property Meld entirely. Costs the cast reading, since
    type casting is a live Python concept.
  • housemark - a house mark is the real historical mark a family used to
    identify its property and goods, the precursor to both heraldry and merchant
    marks. Free. Names the marking rather than the melding.
  • housestyle - the conventions a publishing house imposes on everything it
    publishes, and a phrase the estate's doctrine already uses. Free on PyPI,
    though DonCiccy/housestyle on GitHub is a content linter from 2026-07.
  • houserule, housemint, houseblend - all free, all a tier down.
## `house-meld`, proposed by Kai, checked Availability, 2026-08-25T18:46:56Z: * PyPI - `housemeld`, `house-meld`, `housemelds` all 404 on both surfaces. * GitHub - **zero repositories** match `housemeld` or `house-meld`. * Web - no company or product under either spelling. **This is the best candidate in the thread, and the improvement over `rolemint` is Kai's word order rather than the words.** I had offered `meldhouse` in the free-compound list and it reads as a facility. `house-meld` reads as a natural English noun phrase, the same shape as "house blend" and "house style", and the estate's own doctrine already says house style. Flipping it is the whole fix. ### What it claims A House constitutes its members, holds one rule they all share, and grants each one marks that distinguish them from their siblings. That is the roster exactly: seven seats, one invariant, each with derived identity primitives. A mint issues currency, and this product does not issue currency, it constitutes people. `house` is the better authority noun and it was sitting in plain sight. Both halves are words anyone has met, neither drifts. No crypto sense on `mint`, no Linux distro, and none of the category-noun problem that killed `charter`. It cannot be heard as a plugin, because a house is not an accessory to anything. ### What it costs, and one of these is sharper than I would like * **Property Meld is real software.** Founded 2014, Rapid City, property maintenance software, listed on G2, LinkedIn, and CB Insights. So `<dwelling word> + meld` is a construction already in the software market, and `house` is a near-synonym for `property`. The compound `housemeld` itself is unoccupied, so this is a reading risk rather than a collision, but it is the thing I would want decided with eyes open. * **`house` pulls toward real estate in software.** A GitHub sweep of `house*` compounds comes back almost entirely housing-market projects. Same gravity that produced Property Meld. `meld` pulls against it, and it is a headwind. * **Mild circularity.** The roster's own word for combining two traits is meld, so "house-meld resolves each role's meld" is a live sentence. Milder than "charter composes charters" because the product is the compound rather than the bare noun, and still present. * **Two names to hold.** PyPI normalizes `house-meld` and `house_meld` to the same name, and `housemeld` is a separate name. Register both, ship one. * **Silent on the eval half**, like almost everything in this thread. A house putting its name on something is a guarantee, which reaches at the idea, and I am calling that a stretch rather than a claim. * `meld` is also a Magic: The Gathering mechanic in which two cards combine into one larger card, which is either a pleasing resonance or noise depending on taste. ### Same shape, if Property Meld is disqualifying Kai's insight was `house` plus natural noun-phrase order. It survives the word change. * `housecast` - a house cast is the resident standing company of a theatre. Free on PyPI, and it dodges Property Meld entirely. Costs the `cast` reading, since type casting is a live Python concept. * `housemark` - a house mark is the real historical mark a family used to identify its property and goods, the precursor to both heraldry and merchant marks. Free. Names the marking rather than the melding. * `housestyle` - the conventions a publishing house imposes on everything it publishes, and a phrase the estate's doctrine already uses. Free on PyPI, though `DonCiccy/housestyle` on GitHub is a content linter from 2026-07. * `houserule`, `housemint`, `houseblend` - all free, all a tier down.
Author
Member

Recommendation locked: housecast

Kai chose it. This closes the deliverable in the brief. Availability re-verified
at the moment of the lock, and one finding below that arrived with that
verification and that Kai has not yet seen.

Verification, 2026-08-25T18:50:55Z

  • PyPI - housecast, house-cast, housecasts all 404 on both the JSON API and
    the PEP 503 simple index. Control string zzqxwvfake123 also 404 on both, so
    the checker was sound at the time of the check.
  • Forgejo - coilyco-flight-deck/housecast returns 404. Free.
  • GitHub mirror - coilyco-flight-deck/housecast returns 404. Free.

What it claims

A house cast is the resident standing company of a theatre: a fixed troupe, held
by one house under one set of conventions, able to mount any role in its book.
That is the roster. Seven seats, one invariant, each able to be called.

Both halves are words anyone has met, which was the criterion that invalidated
every rare-word shortlist in this thread. house is the authority noun, since a
House constitutes its members and grants each one marks distinguishing them from
their siblings. cast carries two senses that are both this product: casting a
play, which is deciding who plays which role, and casting metal, which is pouring
a composed melt into a permanent form. The second sense is the immutable bundle.

It sits in umbra's position. A house cast is not an accessory to anything, and
nothing about the name can be heard as a plugin, adapter, or helper to
acompose.

What it forecloses, stated plainly

  • housecast also parses as house plus forecast. This is the finding from
    the lock verification. GitHub carries four housecast repositories, all zero
    stars and all dead, and three of the four are housing-price forecasting
    projects
    . The compound has been independently coined at least three times in
    the Python and ML space as a real-estate forecaster. Combined with the earlier
    sweep showing house* compounds on GitHub skewing almost entirely to housing
    projects, the name inherits real-estate gravity and a competing parse in
    exactly the ecosystem this ships into.
    • Mitigating it: nothing occupies the name, all four repositories are dead
      personal projects, and the product's own context disambiguates on first
      contact. Writing it hyphenated as house-cast forces the correct parse in
      print, and both spellings are free, so that is available as a styling choice
      rather than a constraint.
  • cast is a live Python concept. Type casting. A Python package named
    housecast invites that reading for a beat before the theatre one lands.
  • Silent on the eval half. Like almost every candidate in this thread. The
    name says the company is assembled and held by a house. It does not say the
    house grades what it assembled. compo-seer was the only proposal that reached
    for both, and it died on being an aural homonym for Composer.
  • Quieter than a single evocative word. It will never hit like umbra on a
    page. That was the accepted trade when the search moved to compounds, which it
    had to, because every familiar single word on the anchor is taken.

Act on this soon

From the sweep earlier in this thread: seven independent AI-agent projects
created during 2026 have taken exactly the naming register we searched, four of
them clearing PyPI and dying only on the GitHub check. dokimasia went in May,
euthyna in July, chartulary four days ago. Register the PyPI names the day
this is agreed rather than the day the repository is ready.
Hold both
housecast and house-cast, ship one.

Handed over, not decided here

  • Repository creation, PyPI registration, the CLI verb, the import path, and
    whether repo and distribution names differ.
    All build and packaging work, all
    the platform seat's. This unblocks the packaging slice in #329.
  • The licence. The brief's standing MIT policy applies and nothing in the
    search surfaced a reason to differ.
  • The house-cast hyphen. A styling call that belongs with whoever creates
    the repository, informed by the parse note above.
## Recommendation locked: `housecast` Kai chose it. This closes the deliverable in the brief. Availability re-verified at the moment of the lock, and one finding below that arrived with that verification and that Kai has not yet seen. ### Verification, 2026-08-25T18:50:55Z * PyPI - `housecast`, `house-cast`, `housecasts` all 404 on both the JSON API and the PEP 503 simple index. Control string `zzqxwvfake123` also 404 on both, so the checker was sound at the time of the check. * Forgejo - `coilyco-flight-deck/housecast` returns 404. Free. * GitHub mirror - `coilyco-flight-deck/housecast` returns 404. Free. ### What it claims A house cast is the resident standing company of a theatre: a fixed troupe, held by one house under one set of conventions, able to mount any role in its book. That is the roster. Seven seats, one invariant, each able to be called. Both halves are words anyone has met, which was the criterion that invalidated every rare-word shortlist in this thread. `house` is the authority noun, since a House constitutes its members and grants each one marks distinguishing them from their siblings. `cast` carries two senses that are both this product: casting a play, which is deciding who plays which role, and casting metal, which is pouring a composed melt into a permanent form. The second sense is the immutable bundle. It sits in umbra's position. A house cast is not an accessory to anything, and nothing about the name can be heard as a plugin, adapter, or helper to `acompose`. ### What it forecloses, stated plainly * **`housecast` also parses as house plus forecast.** This is the finding from the lock verification. GitHub carries four `housecast` repositories, all zero stars and all dead, and **three of the four are housing-price forecasting projects**. The compound has been independently coined at least three times in the Python and ML space as a real-estate forecaster. Combined with the earlier sweep showing `house*` compounds on GitHub skewing almost entirely to housing projects, the name inherits real-estate gravity and a competing parse in exactly the ecosystem this ships into. * Mitigating it: nothing occupies the name, all four repositories are dead personal projects, and the product's own context disambiguates on first contact. Writing it hyphenated as `house-cast` forces the correct parse in print, and both spellings are free, so that is available as a styling choice rather than a constraint. * **`cast` is a live Python concept.** Type casting. A Python package named `housecast` invites that reading for a beat before the theatre one lands. * **Silent on the eval half.** Like almost every candidate in this thread. The name says the company is assembled and held by a house. It does not say the house grades what it assembled. `compo-seer` was the only proposal that reached for both, and it died on being an aural homonym for Composer. * **Quieter than a single evocative word.** It will never hit like `umbra` on a page. That was the accepted trade when the search moved to compounds, which it had to, because every familiar single word on the anchor is taken. ### Act on this soon From the sweep earlier in this thread: seven independent AI-agent projects created during 2026 have taken exactly the naming register we searched, four of them clearing PyPI and dying only on the GitHub check. `dokimasia` went in May, `euthyna` in July, `chartulary` four days ago. **Register the PyPI names the day this is agreed rather than the day the repository is ready.** Hold both `housecast` and `house-cast`, ship one. ### Handed over, not decided here * **Repository creation, PyPI registration, the CLI verb, the import path, and whether repo and distribution names differ.** All build and packaging work, all the platform seat's. This unblocks the packaging slice in #329. * **The licence.** The brief's standing MIT policy applies and nothing in the search surfaced a reason to differ. * **The `house-cast` hyphen.** A styling call that belongs with whoever creates the repository, informed by the parse note above.
Sign in to join this conversation.
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/agent-compose#330
No description provided.