Skip to content

t1k:lane-kernel

FieldValue
Modulet1k-base
Version5.15.36
Effortlow
Tools—
/t1k:lane-kernel

Lane Kernel — what a lane needs beyond the leaf kernel

Section titled “Lane Kernel — what a lane needs beyond the leaf kernel”

Preloaded together with t1k:leaf-kernel. Your own body carries the lane contract (worktree, pathspec commits, PR, --auto rules, stop-at-PR, report); this adds only what it lacks.

  • Remotes are SSH: git@github.com:Org/Repo.git, never https://github.com/.... PR base is staging if the remote has that branch, else the default branch.
  • Surgical change: every changed line traces to the brief; no adjacent refactors.
  • On Windows, never call python3: it resolves to the Microsoft Store WindowsApps stub, which does not run the heredoc and does not exit non-zero — it hangs, so a || node fallback never fires and the rest of the command is skipped, leaving the stub running after you report done (#4388). Prefer node; for Python use python only after command -v python shows it is not under WindowsApps, and pass -I.
  • Errors, not silent fallbacks: throw with a clear message; no empty catch.
  • Off-scope findings: do not act and do not ask; name each in one line of your report.
  • You cannot ask the user. State the assumption with a confidence and proceed.
  • Rollout Impact: a PR in a kit repo that changes .claude/modules/**, .claude/t1k-modules.json or .claude/metadata.json MUST carry a ## Rollout Impact section (the CI gate’s exact scope; skills/agents/hooks-only PRs do not need it). A runtime-path change (test files under .claude/{agents,rules,hooks,skills,scripts} included) also needs ## Cost & latency impact with non-empty Tokens:/Latency: lines; fill every section of the repo’s PR template. Full pre-PR gate list: agents/t1k-lane-worker.md Workflow step 7 (pre-pr-kit-gates.cjs denies the PR otherwise).
  • Never pin a tool/runtime/package version until that exact version is confirmed published (releases page or registry), never copied from a local binary’s --version.
  • Heavy shared resource (Unity batch editor, build, full suite): t1k gate run backgrounded, one Monitor, never a poll; hand the job to your spawner if its ETA outlives your budget (skills/t1k-team/references/lane-wait-protocol.md).
  • Hard NEVERs (your body lists them; repeated because each costs a lane the most): no git stash in any form; no git checkout -b/switch/checkout <branch> (your worktree is already on its branch: git branch --show-current); no force-push, --admin, git add -A, commit -a, --amend.