Skip to content

The chat says which unit of the meta-model it drew - #124

Merged
robertblust merged 1 commit into
mainfrom
the-meta-model-is-shown-a-unit-at-a-time
Oct 13, 2026
Merged

robertblust merged 1 commit into
mainfrom
the-meta-model-is-shown-a-unit-at-a-time

Conversation

@robertblust

Copy link
Copy Markdown
Contributor

The model server draws a meta-model of more types than one picture holds a unit at a time, core or one pack, in companygraph/mcp-server#173, and where it is asked for the whole it draws core. On that host the released chat draws the picture again, where it drew nothing, but describes core as the schemas behind the whole model, so a visitor cannot tell that the packs were left out or that one can be asked for.

The note that follows a picture of the schemas now carries the unit drawn and every unit there is with how many types it declares, and asks the answer to say which unit this is, to name the others as what can be shown next, and to say that the meta-model is drawn a unit at a time where the whole was asked for. The diagram rule gains one clause: a visitor who names core or a pack is shown the schema shape by unit, where the host's tool takes one, and never by type. Neither field goes to the widget. A host that does not send them reads as before.

What it costs downstream: nothing breaks for a deployment that re-pins, and the change does nothing until its host takes the model server's release, so the host is re-pinned first. Release notes to write at tagging: the chat says which unit of the meta-model a picture draws and names the other units, and shows core or a pack by name.

Verified: the two new tests failed before the change; npm test, npm run typecheck, npm run build:check, conventions-check and conventions-format pass; a local chat from this branch, against a host serving companygraph/mental-model from the model server's branch, drew core for the whole meta-model in five of five asks, three in English and two in German, and the two read in full named the four packs as what can be shown next; a pack named in three wordings drew that pack each time.

🤖 Generated with Claude Code

The host now draws a meta-model of more types than one picture holds a unit at a time, core or one pack, and where it is asked for the whole it draws core. The chat drew that picture and described it as the schemas behind the whole model, so a visitor could not tell that the packs were left out or that one could be asked for.

The note that follows a picture of the schemas now carries the unit drawn and every unit there is, and asks the answer to say which unit this is, to name the others as what can be shown next, and to say that the meta-model is drawn a unit at a time where the whole was asked for. The diagram rule sends a visitor who names core or a pack to the schema shape by unit, where the host's tool takes one. Neither field goes to the widget, which draws the picture and needs no list of units.

Verified: the two new tests failed before the change; npm test, npm run typecheck, npm run build:check, conventions-check and conventions-format pass; a local chat from this branch, against a host serving companygraph/mental-model from the model server's branch, drew core for the whole meta-model in five of five asks, three in English and two in German, and the two read in full named the four packs as what can be shown next; a pack named in three wordings drew that pack each time.

Process: Delivery
Phase: Implement
Track: Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@robertblust
robertblust merged commit b5b2e73 into main Oct 13, 2026
3 checks passed
@robertblust
robertblust deleted the the-meta-model-is-shown-a-unit-at-a-time branch October 13, 2026 05:55
@robertblust robertblust mentioned this pull request Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant