Repository navigation
The controls for the rules no machine held - #82
Merged
Merged
Conversation
companygraph/mental-model took a control for each rule that had none (companygraph/mental-model#140). This instance takes the five whose rules it holds: the family resync's lock, the chat's claim check on guestgraph.io, the Implementer reading a merge before deleting its branch, a request asked for its gap and never its hotel, and a message from another session carrying no word of the Owner's. The request control keeps only the Owner's part, since this instance's rule is about the product and no vocabulary skill runs here. Verified: companygraph check at 0.94.0 passes, mechanical checks and the form, and each page holds to the control schema's writing rules on a reading of them; the claim check is on in this deployment's chat.json, and delete_branch_on_merge reads false here. Process: Delivery Phase: Implement Track: Prose Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two controls named Claude Code where what they describe is the harness any agent runs in, its permission layer and its hooks, as companygraph/mental-model#140 renamed in its own. A product's name ties a company's controls to one tool; the references keep their addresses, which are where the behavior is documented. Verified: companygraph check at 0.94.0 passes, mechanical checks and the form, and each page holds to the control schema's writing rules on a reading of them; no control names Claude Code outside a reference's URL. Process: Delivery Phase: Implement Track: Prose Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The rule that a feature request carries no guest's data had no control. The Owner holds it in Understand: it reads every request and its comments for a guest's data before restating it, edits any out and deletes it from the edit history, and never asks for one to illustrate a request. The control says what it cannot do: an issue is public from the moment it is opened, so what was read before stays read. Verified: companygraph check at 0.94.0 passes, mechanical checks and the form, and each page holds to the control schema's writing rules on a reading of them; what deleting from an edit history leaves was read from GitHub's documentation, whose link resolves. 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.
companygraph/mental-model#140 gave each of its rules that had none a control. This instance takes the five whose rules it holds: the family resync's lock, the chat's claim check on guestgraph.io, the Implementer reading a merge before deleting its branch, a request asked for its gap and never its hotel, and a message from another session carrying no word of the Owner's. The request control keeps only the Owner's part, since this instance's rule is about the product. It adds one of its own, for its own rule that a feature request carries no guest's data: the Owner reads every request for a guest's data in Understand and takes out any it finds, from the issue and its edit history, and the control says what was read before stays read. With it every rule in this model has a control.
A second commit renames Claude Code to the agent harness in the worktree hook and merge controls, as #140 did in companygraph, so no control ties the company to one tool; the references keep their addresses.
The Owner accepted the adapted lines and any new entry before they were committed.
Verified:
companygraph checkat 0.94.0 passes, mechanical checks and the form, and each page holds to the control schema's writing rules on a reading of them; the claim check is on in this deployment'schat.json, every link resolves, and no rule here is without a control.🤖 Generated with Claude Code