Repository navigation
The profile names every pack, its talk and what comes next - #53
Merged
Merged
Conversation
The profile said three packs in four places while four ship, and it linked only the introduction among the talks companygraph.io carries. Each pack now has one line: the kind of company it is for, its types by name, and links to its README and its talk; core links the talk on core and the packs, and the introduction points to the others. The second instance takes every pack, so it is held to use cases and requirements too. What is not built, market and obligation in core and add in the command, moves out of the shipped items into a short section of its own, sourced from the two designs that named them. The pack rule in AGENTS.md now allows a pack's types by name and the two links, never what a type carries, and no sentence counts the packs. Verified: conventions-check and conventions-format pass. Process: Delivery Phase: Implement Track: Prose Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The section on what comes next listed two pieces that are not built, market and obligation in core and add in the command. It now says what decides the next step instead: the packs that come next are the ones the companies adopting the model ask for, a request starts as an issue on the meta-model, and nothing beyond that is promised. With nothing in core left ahead, the core item carries its check mark like every other shipped item. Verified: conventions-check and conventions-format pass. Process: Delivery Phase: Implement Track: Prose Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The organization profile said three packs in four places while four ship, and among the talks companygraph.io carries it linked only the introduction. Each pack now has one line in the roadmap: the kind of company it is for, its types by name, and links to its README and its talk. Core links the talk on core and the packs, and the introduction's paragraph points to the other talks. The second instance takes every pack, so item 9 adds what its product is held to, as use cases and requirements.
A new section, "What comes next", says what decides the next step: the packs that come next are the ones the companies adopting the model ask for, a request starts as an issue on the meta-model, and nothing beyond that is promised. The two lines about what is not built, market and obligation in core and
addin the command, are no longer on the page, and with nothing in core left ahead the core item carries its ✅ like every other shipped item. The diagram and the repository table say "every pack" and "the packs a kind of company adds", so no sentence counts them.The pack rule in
AGENTS.mdsaid a pack is named "only by what kind of company it is for". It now allows a pack's types by name with links to its README and its talk, and still never what a type carries, as the page already does for core. The sibling change on blust.ch is robertblust/robertblust.github.io#392.Verified: conventions-check and conventions-format pass.
🤖 Generated with Claude Code