Skip to content

Agent neutrality PR-1: vendor-neutral cross-project rules and checkpoint procedure - #13

Merged
varunkatta merged 1 commit into
masterfrom
agents/neutral-operating-model
Oct 8, 2026
Merged

varunkatta merged 1 commit into
masterfrom
agents/neutral-operating-model

Conversation

@varunkatta

Copy link
Copy Markdown
Owner

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

Rule File Source
Model tiers deep, standard, light, premium; deep only for reasoning, design and planning; standard by default; light for simple work; clean, lean brief for every sub-agent operating-model/working-style.md (Model tiers, Cost-aware delegation rewritten in tier words) Owner, 2026-10-06, tier rule
Vendor mapping table: Claude Opus/Sonnet/Haiku/Fable; Codex per D5 (deep = default model at high reasoning effort, standard = default model, light = default model at low effort, premium = the owner's per-launch call) working-style.md (Model tier mapping), the only place model names appear D5
A premium launch needs the owner's explicit per-launch yes working-style.md (Premium launches) Owner, 2026-10-06
Ask first for any new service, monitor, workflow or scheduled wakeup; never set a cap; $0 by default; the owner approves every cost working-style.md (Launches and costs) Owner, 2026-09-27, reaffirmed 2026-10-06
Owner pronouns: the owner, or they/them working-style.md (Addressing the owner) Owner rule in the design lane's briefs
A scope change goes in a fresh agent's brief operating-model/execution-and-handoffs.md (Briefs and scope changes) Owner orchestration rulings (2026-09-30 to 2026-10-06); incident of 2026-09-25 where a mid-task amendment was ignored
Files only under ~/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 /tmp execution-and-handoffs.md (Scratch files and agent worktrees; the Claude path example is gone) Owner, 2026-09-27 and 2026-10-05; D3
Data location and Shared Mastrix repositories rows (D1: only these two uncommitted rows carried), plus product-strategy is read-only working-style.md Owner, 2026-10-05
Vendor-neutral checkpoint and resume procedure operating-model/procedures/checkpoint.md (new), indexed from operating-model/README.md and both root loaders Adapted from the Claude pre-compaction-checkpoint skill
The Claude skill becomes a thin loader pointing at the procedure claude/skills/pre-compaction-checkpoint/SKILL.md, claude/skills/README.md Plan section 5
Decision record operating-model/decision-log.md R1008-27

Notes

  • Based on origin/master. The owner's old checkout has other uncommitted edits (README.md, bootstrap/*, bootstrap/brew/aws.Brewfile); none are carried here (D1).
  • Overlap: the unmerged branch claude/dispatcher-loop (2 commits) touches operating-model/README.md and operating-model/decision-log.md as well as agent-work-loop.md. This PR does not touch agent-work-loop.md; the README and decision-log changes here are one table row each, so whichever merges second needs a trivial rebase.
  • The previous Cost-aware delegation row quoted the owner's 2026-09-27 words with vendor model names. The quote is kept verbatim in the existing decision-log row of that date; the working-style row now says the rule in tier words.
  • Left out: the Fireworks $50 spend cap (project-specific, DIS); DIS and Mastrix-core write grants beyond the carried row (PR-2); the Codex and Claude global loaders (D2, local, after PR-1 to PR-3).
  • Docs only; no code.

🤖 Generated with Claude Code

…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>
@varunkatta varunkatta added the ready to review Owner approved; ready to merge label Oct 8, 2026
@varunkatta
varunkatta merged commit 1097881 into master Oct 8, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready to review Owner approved; ready to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant