Repository navigation
Agent neutrality PR-1: vendor-neutral cross-project rules and checkpoint procedure - #13
Merged
Merged
Conversation
…int procedure - working-style: model tiers (deep, standard, light, premium) with a vendor mapping table, premium launches need the owner's per-launch yes, launches and costs, addressing the owner; carry the Data location and Shared Mastrix repositories rows, product-strategy read-only - execution-and-handoffs: fresh brief for a scope change; scratch and worktree locations without a vendor path, never /tmp - procedures/checkpoint.md: vendor-neutral checkpoint and resume; the Claude skill becomes a thin loader - decision-log and README index 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
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.
What
PR-1 of the agent-neutrality plan. The owner's cross-project working rules, today only in one vendor's local memory, get one vendor-neutral home in
operating-model/so any agent works the way the owner wants. Owner rulings, 2026-10-08: R1008-27 ("n1-n8 is good", accepting decisions D1-D8 as recommended) and "any agent can work exactly like the way I want it to on the repo".Plan:
~/work/code/mastrix/handoffs/2026-10-05-zero-input-design/AGENT-NEUTRALITY-PLAN.md(sections 2, 5, 6 PR-1, 7).Rules added
operating-model/working-style.md(Model tiers, Cost-aware delegation rewritten in tier words)working-style.md(Model tier mapping), the only place model names appearworking-style.md(Premium launches)working-style.md(Launches and costs)working-style.md(Addressing the owner)operating-model/execution-and-handoffs.md(Briefs and scope changes)~/work; scratch in the harness's scratchpad, or~/work/code/mastrix/wt/<repo>-<task>-notes/when there is none; worktrees at~/work/code/mastrix/wt/<repo>-<task>; never/tmpexecution-and-handoffs.md(Scratch files and agent worktrees; the Claude path example is gone)working-style.mdoperating-model/procedures/checkpoint.md(new), indexed fromoperating-model/README.mdand both root loadersclaude/skills/pre-compaction-checkpoint/SKILL.md,claude/skills/README.mdoperating-model/decision-log.mdNotes
origin/master. The owner's old checkout has other uncommitted edits (README.md,bootstrap/*,bootstrap/brew/aws.Brewfile); none are carried here (D1).claude/dispatcher-loop(2 commits) touchesoperating-model/README.mdandoperating-model/decision-log.mdas well asagent-work-loop.md. This PR does not touchagent-work-loop.md; the README and decision-log changes here are one table row each, so whichever merges second needs a trivial rebase.🤖 Generated with Claude Code