|
| 1 | +# OB1 Agent Instructions |
| 2 | + |
| 3 | +## Parallel Agent Worktrees |
| 4 | + |
| 5 | +When multiple AI agents or assistant chats work on this repo, do not put them in the same checkout. |
| 6 | + |
| 7 | +### Setup pattern |
| 8 | + |
| 9 | +- Treat the main repo checkout as the canonical repo for pulling, inspection, and creating worktrees. |
| 10 | +- Create one Git worktree per active agent, task, or PR-sized workstream. |
| 11 | +- Give each worktree a descriptive folder name and a matching branch name. |
| 12 | +- Start every agent task by naming the exact absolute worktree path it owns. |
| 13 | +- The assigned worktree path is the boundary. The chat is not the boundary. |
| 14 | + |
| 15 | +### Agent assignment template |
| 16 | + |
| 17 | +Start each parallel-agent task with: |
| 18 | + |
| 19 | +```text |
| 20 | +Repository worktree: |
| 21 | +/ABSOLUTE/PATH/TO/PROJECT-WORKTREE |
| 22 | +
|
| 23 | +Branch: |
| 24 | +codex/SHORT-TASK-NAME |
| 25 | +
|
| 26 | +Task: |
| 27 | +DESCRIBE THE EXACT WORK. |
| 28 | +``` |
| 29 | + |
| 30 | +### Rules |
| 31 | + |
| 32 | +- Do not switch branches in the canonical repo while another agent may be working. |
| 33 | +- Do not edit sibling worktrees unless explicitly asked. |
| 34 | +- Before staging or committing, run `git status --short` and stage only files that belong to the current task. |
| 35 | +- If `main` or another branch changed underneath the worktree, pause before merging or rebasing unless the task explicitly says to finish the PR end to end. |
| 36 | +- After a branch is merged and the worktree is clean, remove the finished worktree with `git worktree remove /ABSOLUTE/PATH/TO/PROJECT-WORKTREE`. |
| 37 | + |
| 38 | +### Quick checks |
| 39 | + |
| 40 | +- If another chat suddenly changed branches, both chats were probably in the same working directory. |
| 41 | +- If `git worktree add` says a branch is already checked out, create a new branch name or remove the old clean worktree. |
| 42 | +- If cleanup fails, inspect `git status --short` and preserve uncommitted work. |
| 43 | + |
| 44 | +## Required Step: Update Linear |
| 45 | + |
| 46 | +- For feature work tied to a Linear issue, update Linear at the start of the work, at meaningful checkpoints, and before handing back to the user. |
| 47 | +- Use the parent issue as the living implementation log and keep child issues aligned with the files and behavior being changed. |
| 48 | +- For the OB1 Agent Memory / OpenClaw launch work, the parent issue is `NAT-833`. Record architecture notes, implementation milestones, blockers, and verification results there. |
| 49 | +- Do not wait until the end to document decisions. If a decision changes schema, API contract, trust policy, user-facing workflow, or publishing path, capture it in Linear while it is still fresh. |
| 50 | + |
| 51 | +## Agent Memory Product Guardrails |
| 52 | + |
| 53 | +- Keep `OB1 Agent Memory` runtime-neutral. OpenClaw is the flagship launch runtime, not the product boundary. |
| 54 | +- Treat inferred or generated memory as evidence by default. Instruction-grade memory requires human confirmation or trusted import. |
| 55 | +- Avoid raw transcript, model reasoning trace, secret, and large-code-block storage by default. |
| 56 | +- Avoid profanity in all content. Keep docs, examples, seed data, UI copy, prompts, walkthroughs, and generated assets clean and professional. |
| 57 | +- Prefer diagram-first documentation for this work: diagram, short explanation, copy-paste setup, then deeper reference. |
| 58 | +- Carry Nate B. Jones / OB1 provenance through product surfaces, docs, diagrams, screenshots, and starter seed data. Keep it subtle and useful: micro-branding, source labels, logo marks, and provenance language instead of loud marketing copy. |
| 59 | +- Treat public OB1 assets as helpful-first audience growth for Nate Jones. Every public guide, recipe, tutorial, package page, release note, and walkthrough should point back to Nate's Substack and site in a natural way: https://substack.com/@natesnewsletter and https://natebjones.com. |
| 60 | +- Make the case by being genuinely useful. The CTA should feel earned: "Nate gives away practical systems like this" rather than generic marketing copy. |
| 61 | +- For ClawHub/OpenClaw publishing, do not fall back to Jonathan's personal handle or any non-Nate namespace. If `@natebjones` / Nate OB1 ownership is not available, stop and record the blocker. |
0 commit comments