geneseed 5.3.1 → 5.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +68 -0
- package/README.md +21 -18
- package/SHIPPED.md +7 -7
- package/adapters/opencode/README.md +3 -2
- package/adapters/opencode/plugins/geneseed-context.js +6 -0
- package/adapters/opencode/plugins/geneseed-guard.js +5 -3
- package/bin/geneseed-cli.mjs +7 -0
- package/bin/geneseed-hook.mjs +3 -3
- package/docs/PRD.md +1 -1
- package/docs/README.md +1 -0
- package/docs/concepts/agents.md +1 -1
- package/docs/concepts/collaboration.md +2 -2
- package/docs/concepts/enforcement-table.md +5 -2
- package/docs/concepts/exclusions.md +16 -2
- package/docs/concepts/footprint.md +1 -1
- package/docs/concepts/foreman-mode.md +1 -1
- package/docs/concepts/hook-gates.md +3 -3
- package/docs/concepts/hooks.md +4 -3
- package/docs/concepts/host-matrix.md +2 -2
- package/docs/concepts/kits.md +12 -2
- package/docs/concepts/loop-bricks.md +3 -3
- package/docs/concepts/loops.md +6 -4
- package/docs/concepts/ownership.md +1 -1
- package/docs/concepts/rules.md +2 -2
- package/docs/concepts/skills.md +1 -1
- package/docs/extending.md +63 -28
- package/docs/guides/auto-merge.md +100 -0
- package/docs/guides/choose-your-setup.md +1 -1
- package/docs/guides/headless.md +1 -1
- package/docs/guides/install-clone.md +1 -1
- package/docs/guides/install.md +1 -1
- package/docs/guides/loop-finish.md +3 -3
- package/docs/guides/loop-running.md +4 -4
- package/docs/guides/project-context.md +1 -1
- package/docs/guides/run-a-factory.md +2 -2
- package/docs/guides/setup-doctrines.md +2 -2
- package/docs/guides/setup-footprint.md +1 -1
- package/docs/guides/uninstall.md +3 -3
- package/docs/guides/upgrade.md +1 -1
- package/docs/guides/worktree.md +1 -1
- package/docs/reference/environment.md +4 -2
- package/docs/reference/plugin-activity.md +1 -1
- package/docs/reference/plugin-guard.md +1 -1
- package/docs/reference/plugin-learn.md +1 -1
- package/docs/reference/plugin-workflow.md +1 -1
- package/docs/reference/troubleshoot-doctor.md +1 -1
- package/docs/reference/troubleshoot-hooks.md +2 -2
- package/docs/reference/troubleshoot-install.md +3 -3
- package/docs/reference/troubleshoot-tools.md +1 -1
- package/docs/token-footprint.md +2 -2
- package/docs/understand/enforced-vs-asked.md +1 -1
- package/docs/understand/machine-claude.md +2 -2
- package/docs/understand/on-your-machine.md +1 -1
- package/docs/web-ui.md +5 -5
- package/harness.config.json +1 -1
- package/js/README.md +2 -1
- package/js/build/args.mjs +12 -1
- package/js/build/driver.mjs +33 -6
- package/js/build/emit-claude.mjs +8 -4
- package/js/build/emit-opencode.mjs +13 -9
- package/js/build/generate.mjs +10 -156
- package/js/build/profile.mjs +318 -0
- package/js/build/render.mjs +81 -3
- package/js/build/retired-skills.mjs +60 -13
- package/js/build/source.mjs +15 -1
- package/js/build/stubs.mjs +4 -1
- package/js/cli-table.json +48 -3
- package/js/hosts/hooks-done.mjs +345 -55
- package/js/hosts/hooks-learn.mjs +4 -3
- package/js/hosts/hooks-prims.mjs +5 -3
- package/js/hosts/hooks.mjs +153 -6
- package/js/hosts/installs.mjs +19 -1
- package/js/hosts/native.mjs +19 -2
- package/js/hosts/settings.mjs +29 -3
- package/js/inspect/checks-constitution.mjs +32 -0
- package/js/inspect/diff.mjs +21 -3
- package/js/inspect/inventory.mjs +1 -1
- package/js/maintain/setup.mjs +5 -1
- package/js/maintain/update.mjs +4 -2
- package/js/web/actions.mjs +16 -3
- package/js/web/api.mjs +7 -2
- package/package.json +1 -1
- package/registry.json +14 -0
- package/src/AGENT.md.tmpl +15 -17
- package/src/bricks/pr-open.md +3 -2
- package/src/doctrines/ops.md +2 -2
- package/src/doctrines/process.md +40 -36
- package/src/factories/analysis-to-build.json +1 -1
- package/src/factories/bug-report-to-fix.json +1 -1
- package/src/factories/issue-to-pr.json +1 -1
- package/src/kits/terminal-tools/rules.md +10 -0
- package/src/kits/terminal-tools.json +13 -0
- package/src/licenses/herdr.txt +201 -0
- package/src/modes/foreman.md +6 -3
- package/src/skills/_self-improvement.md +9 -7
- package/src/skills/commit.md +17 -17
- package/src/skills/debug/ci.md +1 -1
- package/src/skills/dependencies.md +3 -3
- package/src/skills/document-project.md +3 -2
- package/src/skills/factory.md +13 -4
- package/src/skills/geneseed.md +4 -2
- package/src/skills/git-history.md +5 -7
- package/src/skills/herdr.md +135 -0
- package/src/skills/loop.md +3 -2
- package/src/skills/opencode-cli.md +84 -0
- package/src/skills/pipeline.md +1 -1
- package/src/skills/release.md +5 -8
- package/src/skills/review-response.md +4 -2
- package/src/skills/rule.md +27 -1
- package/src/skills/ship.md +54 -7
- package/src/skills/worktree.md +2 -2
- package/src/upstreams.json +7 -0
- package/themes/_TEMPLATE.json +2 -0
- package/themes/biker.json +2 -0
- package/themes/commentator.json +2 -0
- package/themes/cyberpunk.json +2 -0
- package/themes/gamer.json +2 -0
- package/themes/imperial.json +2 -0
- package/themes/joker.json +2 -0
- package/themes/marvin.json +2 -0
- package/themes/mean.json +2 -0
- package/themes/military.json +2 -0
- package/themes/neutral.json +2 -0
- package/themes/pirate.json +2 -0
- package/themes/sports.json +2 -0
- package/themes/verstappen.json +2 -0
- package/themes/wizard.json +2 -0
- package/web/dist/assets/Activity-D2kOc3yi.js +1 -0
- package/web/dist/assets/ActivityDetail-By3xOr21.js +1 -0
- package/web/dist/assets/{Bonsai-BBl4XXqs.js → Bonsai-CBWDTBA4.js} +1 -1
- package/web/dist/assets/{CopyButton-Beven8yn.js → CopyButton-BVbpriMB.js} +1 -1
- package/web/dist/assets/Dashboard-CIJLPHM9.js +2 -0
- package/web/dist/assets/Docs-CiRRIELs.js +5 -0
- package/web/dist/assets/Factories-DhyK0O8d.js +1 -0
- package/web/dist/assets/{GreenhouseView-Bce212qd.js → GreenhouseView-DW3PgTPy.js} +1 -1
- package/web/dist/assets/Installs-B6nlo-Ly.js +3 -0
- package/web/dist/assets/{JournalView-CV4omyww.js → JournalView-O65qEWfp.js} +1 -1
- package/web/dist/assets/Kits-C5U-yT6Z.js +1 -0
- package/web/dist/assets/Laws-CuTw_XNf.js +4 -0
- package/web/dist/assets/{LibRows-Dag1s0ZX.js → LibRows-D6-CVa3K.js} +1 -1
- package/web/dist/assets/Library-CzPlerd6.js +3 -0
- package/web/dist/assets/Loops-CqNF_-nS.js +2 -0
- package/web/dist/assets/{OperatorHudView-JmYY1pBR.js → OperatorHudView-BNr8K5qj.js} +1 -1
- package/web/dist/assets/Personal-DeDb9e8O.js +2 -0
- package/web/dist/assets/Settings-B8MPN_AD.js +1 -0
- package/web/dist/assets/{Tabs-8zsyEPSK.js → Tabs-DJzAez4h.js} +1 -1
- package/web/dist/assets/index-BL3P-9Rg.js +6 -0
- package/web/dist/index.html +1 -1
- package/web/dist/assets/Activity-WQ3ykgxU.js +0 -1
- package/web/dist/assets/ActivityDetail-7rt04SkS.js +0 -1
- package/web/dist/assets/Dashboard-BgLArtgu.js +0 -2
- package/web/dist/assets/Docs-B5aHp86J.js +0 -5
- package/web/dist/assets/Factories-BjqzXAw8.js +0 -1
- package/web/dist/assets/Installs-B1OsrHXF.js +0 -3
- package/web/dist/assets/Kits-CW1e7xNa.js +0 -1
- package/web/dist/assets/Laws-1Ckf1lbs.js +0 -4
- package/web/dist/assets/Library-B3FuFLel.js +0 -3
- package/web/dist/assets/Loops-CwqgnLNw.js +0 -2
- package/web/dist/assets/Personal-DKLgLa7Z.js +0 -2
- package/web/dist/assets/Settings-BwErnh-R.js +0 -1
- package/web/dist/assets/index-Ce6qF2nG.js +0 -6
package/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,74 @@ label. For the capability ↔ spec map, see [SHIPPED.md](SHIPPED.md).
|
|
|
8
8
|
|
|
9
9
|
## [Unreleased]
|
|
10
10
|
|
|
11
|
+
## [5.4.0] — 2026-11-13
|
|
12
|
+
|
|
13
|
+
**Upgrade note.** *Consent Before Push* changes meaning: run `geneseed rebuild-all` after the
|
|
14
|
+
update. An install that excluded *Consent Before Push* because it asked on every commit can switch
|
|
15
|
+
it back on (`--exclude-rules` without it, or its row on the console's Constitution page). A repo
|
|
16
|
+
whose remote was added by hand has no default branch recorded, and every commit there asks:
|
|
17
|
+
`git remote set-head origin --auto` records it.
|
|
18
|
+
|
|
19
|
+
### Changed
|
|
20
|
+
- **An edited deployed file reads as kept or diverged, and only a diverged one alerts.** "Kept" means the source still renders what the last emit wrote; it shows as neutral in the console and in `geneseed diff`. The base hash survives rebuilds (manifest `kept_hashes`). An edited `.md` file still alerts when kept. The self-improvement text no longer claims the doctor reports such an edit.
|
|
21
|
+
- **Worker briefs never open a command with `cd` into the worktree.** The Foreman worker brief and the pipeline crew brief tell workers to run from the worktree or with absolute paths (`git -C`, `npm --prefix`), because Claude Code asks the user to approve a compound command that opens with `cd` into another folder. Text only; reaches an install on its next emit.
|
|
22
|
+
- **The README opens with a hero image and each main section with a banner.** Seven new SVGs under `docs/assets/` share one dark panel, the brand teal and a gene-seed helix; the terminal demo is redrawn to match, says five targets, types no counts and shows each gate's first two ask lines as the hook prints them. Repository page only: none of it ships in the package.
|
|
23
|
+
- **`herdr` is a skill name again.** It left `RETIRED_SKILL_IDS`, where it sat since its removal in 2026-10: the kit skill drives the same tool, so an install whose `Excluded skills:` line names `herdr` now excludes the kit skill, which is what that line meant. It is listed in the new `REVIVED_SKILL_IDS`, so an old herdr skill folder that no manifest owns is still moved to `archived-skills/` on a global emit: with the kit off nothing replaces it, and with the kit on the current kit copy is written in its place. A herdr skill you edited, and that an emit already kept as yours, is never moved, with the kit on or off.
|
|
24
|
+
- **Consent Before Push guards the main branch, not every commit.** The main branch (`main`,
|
|
25
|
+
`master`, a remote's default, and from a linked worktree the main checkout's branch) changes
|
|
26
|
+
only through a pull request with green checks; a green one is merged on the user's yes or
|
|
27
|
+
under the standing auto-merge rule below, a red, pending or unchecked one never. On any other branch, commits, local merges and plain
|
|
28
|
+
pushes of the checked-out branch run without a prompt, a quoted Conventional Commits message
|
|
29
|
+
(`fix(x): y`) or a bash `-F -` heredoc with a quoted delimiter included.
|
|
30
|
+
- **The git gate follows on Claude Code, OpenClaude and Bob.** It asks for a commit or push onto
|
|
31
|
+
the main branch, a forced push, a bare `git push`, a push of another branch, or a command it
|
|
32
|
+
cannot read; and for everything in a repo with no remote, or a remote with no default branch
|
|
33
|
+
recorded. On Claude Code and OpenClaude a sub-agent's push asks too. Bob sends no sub-agent
|
|
34
|
+
field, so there a worker's push of its own branch passes like a session's; dispatched workers
|
|
35
|
+
are still told never to push. OpenCode keeps its static `git commit*`/`git push*` asks,
|
|
36
|
+
since a glob cannot read the branch, and its carrier says so. The rule id and name stay. The
|
|
37
|
+
`loop/*` exemption now matters only under strict consent.
|
|
38
|
+
- **The done gate may block up to 3 times per continuation, each time only after a new edit or a changed background verdict.** It used to block once per turn. A task notification starts a new continuation with a fresh count. Over the whole turn, up to the next human prompt, it blocks at most 10 times, so a red suite relaunched in the background cannot loop. A Stop with no new edit and no new verdict since the last block ends the turn with the `done-gate-cap` ledger line. A block names the checks whose background run is still running or reported a failure. The count is kept per session (and per sub-agent) in the install's `notebook/done-gate/`.
|
|
39
|
+
- **The startup text states its order without shouting.** The readiness-sigil paragraph loses "required", "MUST", "verbatim" and "do not paraphrase"; §9 loses "not deferrable" and "this is not a suggestion". Every ordering clause stays: read the rules and load the project context before the first reply, begin it with the sigil line, and a matching skill is still the first tool call. Strong current models over-apply emphatic wording; a weak model keeps the same sequence. The sigil line itself is unchanged, so theme detection and Bob's own first-reply override are untouched. Reaches an install on its next emit.
|
|
40
|
+
- **A build no longer resets an install's settings in silence; a bare build over one now exits 1.**
|
|
41
|
+
A `geneseed build` (or `geneseed-build`) over an existing install of the same host compares
|
|
42
|
+
each setting it was not given — theme, footprint, posture, mode, trust, packs, excluded rules
|
|
43
|
+
and skills, kits, shared tier, gate switches — with the install's own. If one would change, it
|
|
44
|
+
refuses before writing anything, exit 1: it lists each change as `name: current -> new` and
|
|
45
|
+
prints the install's own rebuild command with the flags you passed applied on top. A flag you
|
|
46
|
+
pass is never compared. A build that ran before and reset a setting now stops there; the new
|
|
47
|
+
`--reset` flag accepts the defaults for one build. `rebuild-all`, `upgrade`, `migrate` and
|
|
48
|
+
the console's rebuild replay an install's whole profile and run as before; the console's
|
|
49
|
+
install and deploy forms, its Build onto another emit, and the setup wizard, which compose a
|
|
50
|
+
whole selection, pass `--reset`. A rebuild command now spells `--posture` and `--mode`
|
|
51
|
+
unless they equal `harness.config.json`'s default, not the literal `peer`/`direct`. The first
|
|
52
|
+
`geneseed upgrade` into this version still replays with the old code, so an OpenCode project
|
|
53
|
+
bundle with the shared tier on can be refused once: run `geneseed upgrade` again.
|
|
54
|
+
`installProfile`, `setupBuildArgs` and `rebuildCommand` moved to `js/build/profile.mjs` so the
|
|
55
|
+
generator can read an install without reaching a module that spawns.
|
|
56
|
+
|
|
57
|
+
### Added
|
|
58
|
+
- **A new opt-in kit, `terminal-tools`, for terminal programs the agent drives through their own CLI.** It adds two skills and no agent. `herdr` controls Herdr workspaces, tabs, panes and agents from inside a Herdr pane, gated on `HERDR_ENV=1` and on the user naming Herdr; it is adapted from the official skill of [herdrdev/herdr](https://github.com/herdrdev/herdr) (Apache-2.0), pinned at the v0.9.4 metadata sync, and carries the Windows notes of herdr's own docs page (native support generally available; signed binaries and SmartScreen avoidance unsupported; one x86_64 Windows asset in v0.9.5). `opencode-cli` drives OpenCode V2 from another session: headless `opencode run` with JSON output, the background service against `--standalone` and `--server`, sessions, MCP, plugins, models, stats and debug; it is first-party, verified against the V2 source at v2.3.0, and leaves every credential command to the user. The kit's rules gate on the environment, read live state before acting, close only what the agent opened, and never stop the user's server or service. It is off by default; turn it on with `--kits terminal-tools`.
|
|
59
|
+
- **`--strict-consent`** (the *Strict consent* switch on the console's Constitution page)
|
|
60
|
+
brings back the old behaviour: every commit and push asks, own branch included. The install
|
|
61
|
+
records it (`Own-branch pass: off`), every rebuild and upgrade keeps it, and the carrier
|
|
62
|
+
says so under the rule.
|
|
63
|
+
- **Auto-merge green PRs, off by default.** Say "turn on auto-merge" and the `rule` skill writes a standing rule into `user-rules.md` (global or per project; the project layer wins). With it, the `ship` skill and a factory's close step arm the forge's auto-merge on a PR the agent opens, on the reviewed head, only when the base branch has required checks: docs and tests only can arm at once, other code waits for one approving review (or the blind reviewer, for a solo repo), and a sensitive diff never arms, whatever the rule says. An armed PR is disarmed before any later push. Without the rule nothing changes, and the agent says once per session in a repo how to turn it on. No host gates a merge command, so the rule is text on every host; see `docs/guides/auto-merge.md`.
|
|
64
|
+
- **Sub-agents are judged at SubagentStop.** The done gate reads the sub-agent's own transcript and judges each git root it wrote under against that root's own list. A block keeps the sub-agent working; an inferred check there is a stderr line and a ledger entry only.
|
|
65
|
+
- **The `geneseed` skill covers a reinstall.** Its trigger now names reinstalling, updating,
|
|
66
|
+
upgrading, repairing and re-running the install, and it opens with the rule: start from the
|
|
67
|
+
install's `rebuild` command, change only the named flag, run the command a refusal prints, and
|
|
68
|
+
add `--reset` only when the user asked for the defaults.
|
|
69
|
+
|
|
70
|
+
### Fixed
|
|
71
|
+
- **Bob prints the readiness banner once.** Bob's first-reply override told it to begin with the sigil line, and Bob also echoed the theme's fenced banner block right under it: two banners in every first reply. The override now says to print the sigil line once and never reproduce the banner block. Reaches a Bob install on its next emit.
|
|
72
|
+
- **`install.cmd` puts `geneseed` on PATH, as `./install` does.** After the setup wizard, when `geneseed` is not on PATH, the Windows installer now runs `geneseed link`, which writes `%LOCALAPPDATA%\Geneseed\bin\geneseed.cmd` and adds that folder to the user Path. Before, a fresh Windows clone had no `geneseed` command until the user found `geneseed.cmd link`. The check is `where $PATH:geneseed`: a bare `where` also searches the current folder and would find the clone's own launcher. A failed link only warns; `geneseed.cmd` still works from the clone. npm installs are unchanged, since npm already puts `geneseed` on PATH.
|
|
73
|
+
- **A background launch is not a pass.** A check started with `run_in_background`, or moved to the background after its foreground timeout, counts only when its task notification says it completed with exit code 0. Before, the launch itself counted, which was 76 of 112 accepted passes in 30 days of real transcripts. A task notification no longer opens a turn.
|
|
74
|
+
- **An excluded rule is no longer cited by the instructions file.** Owner decision D3 (2026-11-11) made an excluded rule off, but the carrier still cited it: an install that excluded process 5 read `(*Consent Before Push*)` in §3, Foreman mode and three process rules. The render now removes a parenthetical citation of an excluded rule, and only that name from a list of citations. The rule files on disk keep every citation. `geneseed doctor` refuses a carrier parenthetical that mixes a doctrine citation with other words; the three such sites (§3 twice, §6) and one in ops 4 were rewritten. Reaches an install on its next emit; a build with no exclusion is unchanged.
|
|
75
|
+
- **Skill and agent descriptions no longer end in `;`.** A description keeps the first clause of the trigger, and a clause that ended at a `;` kept it: six skills (dependencies, geneseed, loop, review-response, skill-forge, wayfinder) ended their `description:` in a `;`, which reads as text cut short. That `;` is now a `.`. Reaches an install on its next emit.
|
|
76
|
+
- **`geneseed help <hook-verb>` prints the hook's help instead of refusing.** `geneseed help context` (and `geneseed context --help`) answered with the hook-verb refusal and exit 2. It now prints one line saying the host runs it as `geneseed-hook context`, then that binary's own help for the verb, and exits 0. A bare `geneseed context` still refuses.
|
|
77
|
+
- **The notebook path names `.claude/` or `.bob/` on a project install.** On a Claude Code or Bob project install the notebook is `.claude/notebook/` or `.bob/notebook/`, but the Foreman mode's ledger and status files and the notes file of every skill and agent self-improvement loop said `notebook/…`, a folder that does not exist at the repo root. They now carry the prefix, as §6 already did; Bob's global `rules/geneseed.md` says `../notebook/`. OpenCode and OpenClaude project installs, plain bundles and the shared tier's notes path are unchanged. Reaches an install on its next emit.
|
|
78
|
+
|
|
11
79
|
## [5.3.1] — 2026-11-12
|
|
12
80
|
|
|
13
81
|
**Upgrade note.** The fixed hook commands, matchers and plugins reach an install only when it is emitted again: run `geneseed rebuild-all` after the update.
|
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
<div align="center">
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
<h1 align="center"><img src="docs/assets/hero.svg" alt="Geneseed" width="880"></h1>
|
|
4
4
|
|
|
5
5
|
**A portable, theme-able harness you implant once and use everywhere to grow a disciplined AI coding agent.**
|
|
6
6
|
|
|
@@ -39,9 +39,9 @@ A hand-written instructions file is prose the model may or may not honour, copie
|
|
|
39
39
|
|
|
40
40
|
- **Laws are enforced, not suggested.** A force-push to `main`, a `reset --hard` that abandons unpushed commits, or a credential written into a tracked file is caught by a hook *before* the tool runs, in the host's own dialect — a prompt on Claude Code and OpenClaude, a hard block on OpenCode, exit 2 on Bob. The gates fail closed, and every catch is one line in a ledger that `geneseed status` counts.
|
|
41
41
|
- **The developer stays the owner of the code.** In a production application the agent proposes and the developer decides — per feature, per file or per function, as the team sets in a committed `AGENTS.md`. Interfaces and sensitive zones are always a checkpoint, complex parts are explained before they land, and a hook stops the first write in an application that has not chosen yet. [Ownership →](#-ownership-of-production-code)
|
|
42
|
-
- **One source, five targets.** Skills are byte-identical on every host; only the wiring differs. Every commit renders all
|
|
42
|
+
- **One source, five targets.** Skills are byte-identical on every host; only the wiring differs. Every commit renders all 268 emit configurations, and a second emit into the same tree must change nothing.
|
|
43
43
|
- **Costs are measured, not guessed.** Zero runtime dependencies. The hook path loads in about 14 ms per tool call. The default *lean* footprint keeps the always-on context small and puts the full rationale one read away — the numbers are in [docs/token-footprint.md](docs/token-footprint.md).
|
|
44
|
-
- **It follows you.** Install once, globally; every repo inherits it. One `git pull` or `npm install -g geneseed@latest` rebuilds every active install.
|
|
44
|
+
- **It follows you.** Install once, globally; every repo inherits it. One `geneseed upgrade` (a `git pull`), or `npm install -g geneseed@latest` then `geneseed rebuild-all`, rebuilds every active install.
|
|
45
45
|
|
|
46
46
|
This page is the overview. **New to agent harnesses?** Start with [Understand](docs/understand/harness.md) — a short course on what a harness is, what lands on your machine, what changes in your day, and what is enforced versus only asked. Everything else — every install path, configuration knob, and troubleshooting step — is in the **[documentation](docs/README.md)**, which the web console also renders.
|
|
47
47
|
|
|
@@ -51,7 +51,7 @@ This page is the overview. **New to agent harnesses?** Start with [Understand](d
|
|
|
51
51
|
|
|
52
52
|
<p align="center"><sub>31 deterministic checks, no LLM — <a href="#ai-harness-scorecard">how this is scored, and how to score your own repo</a></sub></p>
|
|
53
53
|
|
|
54
|
-
|
|
54
|
+
<p align="center"><img src="docs/assets/banner-why.svg" alt="" width="880"></p>
|
|
55
55
|
|
|
56
56
|
## 🧬 1 · Why Geneseed
|
|
57
57
|
|
|
@@ -70,7 +70,7 @@ geneseed-build # default theme (neutral)
|
|
|
70
70
|
geneseed-build --theme imperial # Warhammer 40k voice, identical structure
|
|
71
71
|
```
|
|
72
72
|
|
|
73
|
-
|
|
73
|
+
<p align="center"><img src="docs/assets/banner-setup.svg" alt="" width="880"></p>
|
|
74
74
|
|
|
75
75
|
## 🚀 2 · Setup
|
|
76
76
|
|
|
@@ -82,7 +82,7 @@ The harness is published on npm as **[`geneseed`](https://www.npmjs.com/package/
|
|
|
82
82
|
npx geneseed setup # the guided wizard
|
|
83
83
|
```
|
|
84
84
|
|
|
85
|
-
The wizard asks for a **theme** (each one
|
|
85
|
+
The wizard asks for a **theme** (each one listed with a one-line description) and an **install mode** — a host (OpenCode, Claude Code, IBM Bob or OpenClaude) installed globally or per repo, *OpenCode global* being the recommended one (every repo inherits it), or the *plain bundle* for any `AGENT.md` tool — then builds and offers a health check. It works the same on macOS, Linux and Windows (cmd, PowerShell, or a POSIX shell).
|
|
86
86
|
|
|
87
87
|
Keeping it around is the same command with `npm`:
|
|
88
88
|
|
|
@@ -137,7 +137,7 @@ Node ≥ 22.7 is the entire dependency list — every command, all six hook verb
|
|
|
137
137
|
- **Run it from anywhere** — a global `npm install -g geneseed` already does this; from a checkout see [Run geneseed from anywhere](docs/guides/run-anywhere.md).
|
|
138
138
|
- **Something wrong?** [Troubleshooting](docs/reference/troubleshooting.md) is organised by what you see.
|
|
139
139
|
|
|
140
|
-
|
|
140
|
+
<p align="center"><img src="docs/assets/banner-console.svg" alt="" width="880"></p>
|
|
141
141
|
|
|
142
142
|
## 🖥 3 · Web & terminal
|
|
143
143
|
|
|
@@ -158,7 +158,7 @@ geneseed web stop # stop the daemon
|
|
|
158
158
|
geneseed web status # is it running, and where
|
|
159
159
|
```
|
|
160
160
|
|
|
161
|
-
The sidebar has
|
|
161
|
+
The sidebar has eleven pages: **Overview** (what's deployed, health, recent jobs), **Constitution** (the rules and doctrine switches), **Library** (skills, agents, the wiki), **Kits** (opt-in stack bundles), **Loops** (the loop catalogue), **Personal** (your rules, profile, memory, notebook), **Installs** (hosts, local edits, doctor, server), **Factories** (the factory catalogue and its runs), **Activity** (what the sessions did), **Settings** and **Docs** — this documentation, opening on the Understand track, with a map of what Geneseed put on your machine.
|
|
162
162
|
|
|
163
163
|
It binds to `127.0.0.1` only and runs entirely offline — no npm needed at runtime; the UI build ships in `web/dist/`. Mutating actions run in the background and report back as toasts (fire-and-notify), guarded by a per-session token so other sites can't trigger them. A global **Spotlight** search in the topbar jumps to any agent, skill, rule, doc, or MCP server. Rebuild the UI after changing anything under `web/src/` with `cd web && npm install && npm run build`. If `web/dist/` is missing (fresh clone, never built), `geneseed web` offers to run that build for you — answer `Y` and it installs, builds, and starts the server; in non-interactive shells it prints the manual recipe instead.
|
|
164
164
|
|
|
@@ -168,11 +168,11 @@ Full reference — every view, the launch/daemon/PWA surface, the security model
|
|
|
168
168
|
|
|
169
169
|
No browser? Every action the console offers is also a verb: `build`, `doctor`, `diff`, `rebuild-all`, `status`, `memory`, `catalog`, `exclude`, `mcp`, `link`/`unlink`, `uninstall` (global **or** per-repo). `geneseed setup` runs the install wizard — plain text prompts, every console, every OS; see [Setup](#-2--setup) above for the walkthrough. `geneseed --help` lists every command, and bare `geneseed` (or `./geneseed`) opens the web console when it can, else prints the command list. There is no full-screen panel: `menu` prints the command list (`tui` is retired, and says so).
|
|
170
170
|
|
|
171
|
-
|
|
171
|
+
<p align="center"><img src="docs/assets/banner-contents.svg" alt="" width="880"></p>
|
|
172
172
|
|
|
173
173
|
## 📦 4 · What you get
|
|
174
174
|
|
|
175
|
-
The harness ships as a small set of layers, and the web console's rail is the same shape — Constitution
|
|
175
|
+
The harness ships as a small set of layers, and the web console's rail is the same shape — Constitution has its own entry; skills, agents and the wiki sit under Library; memory and notebook under Personal:
|
|
176
176
|
|
|
177
177
|
| Layer | What it is |
|
|
178
178
|
| --- | --- |
|
|
@@ -222,7 +222,7 @@ Pick with `--theme NAME` or via the setup wizard; upgrades remember it. More in
|
|
|
222
222
|
|
|
223
223
|
A second per-install dial sets how much of the constitution the root file carries *inline* every turn — a token-cost knob, not a change to which Rules apply. **lean** (the default) carries each rule's hand-written short form and points to the full text on disk; **full** inlines every rule with its rationale. Every rule is in force either way. More in [Footprint](docs/concepts/footprint.md) and [Footprint, loop trust and changing later](docs/guides/setup-footprint.md).
|
|
224
224
|
|
|
225
|
-
|
|
225
|
+
<p align="center"><img src="docs/assets/banner-harnesses.svg" alt="" width="880"></p>
|
|
226
226
|
|
|
227
227
|
## 🔌 Supported harnesses
|
|
228
228
|
|
|
@@ -306,11 +306,11 @@ Geneseed/
|
|
|
306
306
|
## 🧪 Validate & test
|
|
307
307
|
|
|
308
308
|
```bash
|
|
309
|
-
node bin/geneseed-cli.mjs doctor
|
|
309
|
+
node bin/geneseed-cli.mjs doctor --all # every theme + parity + authoring + drift
|
|
310
310
|
node --test --test-reporter=tap "tests/**/*.test.mjs" # the suites (node expands the glob)
|
|
311
311
|
```
|
|
312
312
|
|
|
313
|
-
`doctor` checks each theme for unresolved tokens, dead/non-hermetic links, theme-key parity, author-time gates (every spec has a purpose line, the plugins parse, the learn-prompt literal stays extractable), and that a committed bundle still matches a fresh render of `src/`. CI (`.github/workflows/ci.yml`) runs both on every
|
|
313
|
+
`doctor` checks each theme for unresolved tokens, dead/non-hermetic links, theme-key parity, author-time gates (every spec has a purpose line, the plugins parse, the learn-prompt literal stays extractable), and that a committed bundle still matches a fresh render of `src/`. CI (`.github/workflows/ci.yml`) runs both on every PR and on every push to `main`, on both Linux and Windows. Publishing is a separate workflow (`.github/workflows/publish.yml`) that runs when CI finishes green on `main` and releases only a version npm does not have yet — see [Contributing](#-contributing).
|
|
314
314
|
|
|
315
315
|
### AI Harness Scorecard
|
|
316
316
|
|
|
@@ -325,7 +325,7 @@ geneseed scorecard --json # every check with its evidence
|
|
|
325
325
|
|
|
326
326
|
## 🔄 Keeping it current
|
|
327
327
|
|
|
328
|
-
**Installed from npm** —
|
|
328
|
+
**Installed from npm** — two commands: the second rebuilds every active install for you:
|
|
329
329
|
|
|
330
330
|
```bash
|
|
331
331
|
npm install -g geneseed@latest
|
|
@@ -335,13 +335,15 @@ geneseed rebuild-all # re-render every registered install in its own theme + m
|
|
|
335
335
|
**Installed from a clone** — the `git pull` route, which also refreshes the launchers:
|
|
336
336
|
|
|
337
337
|
```bash
|
|
338
|
-
./geneseed
|
|
339
|
-
./geneseed upgrade --setup
|
|
340
|
-
./geneseed
|
|
338
|
+
./geneseed upgrade # git pull, validate, then rebuild every install (remembers theme + emit mode)
|
|
339
|
+
./geneseed upgrade --setup # the same, then drop into the setup wizard (was: bootstrap)
|
|
340
|
+
./geneseed update # an alias of upgrade
|
|
341
341
|
```
|
|
342
342
|
|
|
343
343
|
**Local edits survive.** The self-improvement loops write to notes under `notebook/`, which no rebuild touches. If you or the agent edited deployed agent/skill files in place anyway, an upgrade exports those edits to an `improvements/` file inside the install; the rebuild then keeps each edited file instead of overwriting it. Details: [Upgrade](docs/guides/upgrade.md).
|
|
344
344
|
|
|
345
|
+
<p align="center"><img src="docs/assets/banner-docs.svg" alt="" width="880"></p>
|
|
346
|
+
|
|
345
347
|
## 📚 Documentation
|
|
346
348
|
|
|
347
349
|
| Page | Read it when… |
|
|
@@ -365,7 +367,7 @@ geneseed rebuild-all # re-render every registered install in its own theme + m
|
|
|
365
367
|
|
|
366
368
|
## 🤝 Contributing
|
|
367
369
|
|
|
368
|
-
Issues and PRs welcome at [github.com/Arylmera/Geneseed](https://github.com/Arylmera/Geneseed). The CI
|
|
370
|
+
Issues and PRs welcome at [github.com/Arylmera/Geneseed](https://github.com/Arylmera/Geneseed). The CI runs on every PR and on `main`, and the package has zero runtime dependencies — keep `doctor` green and the test suites passing. Adding a new theme is one JSON file in `themes/` with the same voice-token keys; `doctor` will tell you if any are missing.
|
|
369
371
|
|
|
370
372
|
Start with [`AGENTS.md`](AGENTS.md), the repo's working guide (`CLAUDE.md` imports it). Three things that bite when you don't know them:
|
|
371
373
|
|
|
@@ -387,6 +389,7 @@ Some skills and agents are adapted from other open-source skill collections, und
|
|
|
387
389
|
- `vibe-wise` — [nykooi1/vibe-wise](https://github.com/nykooi1/vibe-wise) by Noah Kim (MIT): the state file, levels and checkpoints of learn-mode, and the checkpoint rules ownership shares.
|
|
388
390
|
- `piomin-spring-boot` — [piomin/claude-ai-spring-boot](https://github.com/piomin/claude-ai-spring-boot) by Piotr Mińkowski (Apache-2.0): the Spring Boot kit's skills and agents, rewritten and condensed for Boot 4.
|
|
389
391
|
- `everything-claude-code` — [affaan-m/everything-claude-code](https://github.com/affaan-m/everything-claude-code) by Affaan Mustafa (MIT): the React kit's skills and agents, rewritten and condensed for Vite and Jest, and part of the docker kit's compose-ops skill, rewritten for operations.
|
|
392
|
+
- `herdr` — [herdrdev/herdr](https://github.com/herdrdev/herdr) by herdrdev (Apache-2.0): the terminal-tools kit's herdr skill, condensed into house format with a Windows note.
|
|
390
393
|
- `i-have-adhd` — [ayghri/i-have-adhd](https://github.com/ayghri/i-have-adhd) by Ayoub Ghriss (MIT): the rules, rule-breaking cases and pre-send check of the adhd mode.
|
|
391
394
|
|
|
392
395
|
## 📄 License
|
package/SHIPPED.md
CHANGED
|
@@ -20,7 +20,7 @@ historical references, not files distributed with the repo.
|
|
|
20
20
|
> **On version numbers.** [`harness.config.json`](harness.config.json)'s `version` is a
|
|
21
21
|
> human-readable label only. The canonical identity of an installed harness is the
|
|
22
22
|
> **source fingerprint** stamped in `.geneseed-version` (see `geneseed version`), not the
|
|
23
|
-
> string. Current label: **5.
|
|
23
|
+
> string. Current label: **5.4.0**.
|
|
24
24
|
|
|
25
25
|
## Capabilities
|
|
26
26
|
|
|
@@ -30,12 +30,12 @@ Every row below is present in the tree today; "Spec" names the design record.
|
|
|
30
30
|
| --- | --- | --- |
|
|
31
31
|
| **Themed generator** | One neutral `src/` → 14 themed bundles via `geneseed-build` (zero dependencies); structure stays theme-independent | [DESIGN.md](DESIGN.md) |
|
|
32
32
|
| **Laws / Agents / Skills / Memory / Notebook** | 9 laws, 20 agents, 51 skills, the memory convention, and the agent's sovereign notebook | `2026-06-11-notebook-sovereign-space` · `2026-06-10-notebook-agent-own-space` |
|
|
33
|
-
| **Three-tier constitution** | The governance surface splits into an always-on **Ontology** (Telos, Evidence, Decisions, Ownership, Conduct — the Pact absorbed into Telos), the nine always-on **Invariants**, and five toggleable **Doctrine** packs (craft, rigor, ops, process, comms) addressed `<pack> <n>`. Every rule carries a permanent id; its number is its position, computed at render time, and a citation renders as the rule's principle name. Packs are chosen at build time with `--doctrines` or the setup wizard; the whole catalogue ships on disk either way, so a citation into an inactive pack still resolves. Precedence, in order:
|
|
33
|
+
| **Three-tier constitution** | The governance surface splits into an always-on **Ontology** (Telos, Evidence, Decisions, Ownership, Conduct — the Pact absorbed into Telos), the nine always-on **Invariants**, and five toggleable **Doctrine** packs (craft, rigor, ops, process, comms) addressed `<pack> <n>`. Every rule carries a permanent id; its number is its position, computed at render time, and a citation renders as the rule's principle name. Packs are chosen at build time with `--doctrines` or the setup wizard; the whole catalogue ships on disk either way, so a citation into an inactive pack still resolves. Precedence, in order: the Invariants, then the user's `user-rules.md`, then the Ontology, then the active Doctrines, then the mode, then `PROFILE.md`, posture and theme, which inform and never bind. `doctor`'s `constitutionProblems` gates rule ids (declared, unique, never a retired one), the per-rule Principle column, every `{{LAW:<id>}}` / `{{DOCTRINE:<id>}}` citation in `src/`, and the rule that an always-on tier may never cite a toggleable one | `2026-08-19-three-tier-constitution-design` |
|
|
34
34
|
| **`doctor`** | One check: unresolved tokens, dead/non-hermetic links, theme-key parity, authoring gates, rendered-bundle drift | `2026-06-07-theme-aware-doctor-diff` |
|
|
35
|
-
| **`diff` + improvements export** | Deployed-vs-source drift report; export an `improvements
|
|
35
|
+
| **`diff` + improvements export** | Deployed-vs-source drift report; export an `improvements/improvements-<date>-<time>.md` back-port inside the install | `2026-06-12-improvements-export` |
|
|
36
36
|
| **`status` / `version`** | Headless dashboard + fingerprint verdict (no TUI needed) | `2026-06-07-status-command` · `2026-06-07-version-and-uninstall` |
|
|
37
|
-
| **Terminal rendering** | There is no full-screen control panel: `
|
|
38
|
-
| **Web console** | Local browser UI (
|
|
37
|
+
| **Terminal rendering** | There is no full-screen control panel: `menu` is a verb that says so and prints the command list, and the retired `tui` points at `menu`. The display-width and glyph layer ships on, behind `status` and the install animation | `2026-06-07-tui-refactor-polish` · `2026-06-08-tui-modern-refresh` · `2026-06-11-windows-tui` |
|
|
38
|
+
| **Web console** | Local browser UI (Overview; Govern: Constitution, Personal; Build: Library, Kits, Loops, Factories; Run: Installs, Activity; Help: Docs, Settings), auto-build, in-app docs menu | `2026-06-12-web-ui-v2` · `2026-06-12-web-auto-build` · `2026-06-13-docs-menu` |
|
|
39
39
|
| **OpenCode adapter** | Native agents/skills mapping + plugins (context, learn, guard, workflow, notify, ponytail, activity); global-emit link integrity; JSONC config target | `2026-06-07-opencode-adapter-features` · `2026-06-07-global-emit-link-integrity` · `2026-06-12-opencode-jsonc-target` · `2026-06-16-ponytail-minimal-code-mode` |
|
|
40
40
|
| **Host hooks, per dialect** | Every host gets the hook surface its runtime offers, spoken in that runtime's own verdict dialect via `--host`: Claude Code asks (`permissionDecision`), OpenClaude asks exactly as Claude does (a Claude Code fork, under `~/.openclaude` / `.openclaude/`), Bob refuses by exit code 2 (five Claude-named events, nested `~/.bob/settings/settings.json`, no subagent event), OpenCode's guard throws. Laws I/IV are the hard tier everywhere; the consent rules ask where a host can ask and warn where it cannot. `tool-gate` fuses the two gates for hosts that run one command per event; `PreCompact` runs `learn` before Claude compacts; every block or ask lands in `notebook/gates.jsonl` on every host | [bob](adapters/bob/README.md) · [claude-code](adapters/claude-code/README.md) · [candidate hosts](docs/candidate-hosts.md) |
|
|
41
41
|
| **Workflow primitive** | Saved, code-driven subagent orchestration (`workflow` tool + runtime); shipped scripts include `dispatch` — decompose a goal, route each subtask to its owning agent, converge | `2026-06-09-opencode-workflow-primitive` |
|
|
@@ -43,9 +43,9 @@ Every row below is present in the tree today; "Spec" names the design record.
|
|
|
43
43
|
| **Wiki integration** | Machine-wide knowledge base (`geneseed-wiki.jsonc`): eager/lazy loading, conventions, protected folders enforced at the tool boundary | `2026-06-11-wiki-knowledge-base` |
|
|
44
44
|
| **Collaboration layer** | Negotiated postures (peer/mentor/expert/assistant/artisan, chosen at setup, inlined in AGENT.md), the bidirectional Pact, epistemically-typed memory (`force:` + Bridge rule), and a seed-once `PROFILE.md` identity with a web editor tab and a `profile` skill that interviews the user to draft it | `2026-07-12-collaboration-layer` |
|
|
45
45
|
| **Ownership** | The developer keeps ownership of production code: a Credo section (the code belongs to whoever answers for it), the `ownership` skill (setup from the code and a short interview, `feature`/`file`/`function` granularity, interfaces and sensitive zones always a checkpoint, announce-don't-ask), a `## Ownership` section in the committed root `AGENTS.md` (`mode: on\|off`), and a first-write gate on every host that stops the session's first write once in an application repo without one. learn-mode always comes first; `develop`, the `developer` agent and Foreman hold the checkpoints. Off per repo (`mode: off`), per install (`--no-ownership-gate`), per session ("proceed without") | `2026-10-26-ownership` |
|
|
46
|
-
| **Rule front door** | Both durable stores enter through the `rule` skill's fork (*standing rule, or fact to remember?* — always asked, never inferred): the memory branch elicits the binding `force` and shows the file before writing, the rule branch pressure-tests by reformulation and a mandatory counter-example. Doctrine process 1 carries the norm on every host; a `rule-gate` PreToolUse hook (Claude, Bob) and OpenCode's own prompt behind `geneseed-guard` hold it at the tool boundary | `2026-07-30-rule-front-door` |
|
|
46
|
+
| **Rule front door** | Both durable stores enter through the `rule` skill's fork (*standing rule, or fact to remember?* — always asked, never inferred): the memory branch elicits the binding `force` and shows the file before writing, the rule branch pressure-tests by reformulation and a mandatory counter-example. Doctrine process 1 carries the norm on every host; a `rule-gate` PreToolUse hook (Claude, OpenClaude; on Bob inside its `tool-gate`) and OpenCode's own prompt behind `geneseed-guard` hold it at the tool boundary | `2026-07-30-rule-front-door` |
|
|
47
47
|
| **Entity registry** | `registry.json` records a lifecycle status, version, owner and add-date for every agent and skill in the tree (maintainer-side — never rendered into a bundle, so it costs no session context). `doctor` gates it against `src/` in both directions, sweeps everything that ships for credentials, and holds each vendored skill folder to an immutable upstream commit. The status surfaces as a badge in the web catalog, shown only where it deviates from `approved` | `2026-07-31-entity-registry` |
|
|
48
|
-
| **Node runtime + npm package** | The whole harness runs from Node: every command `js/cli-table.json` declares, all
|
|
48
|
+
| **Node runtime + npm package** | The whole harness runs from Node: every command `js/cli-table.json` declares, all six hook verbs, every web-console endpoint (the OS-native folder picker excepted, and declined on purpose) and both generators. Every commit runs the unit suite, `doctor --all` across every theme × host × footprint, the generator's two self-comparisons and its CLI expectation matrix, on Linux and Windows both; the frozen emit/cli/web recordings that also gated it retired on 2026-08-17 (see the 2.0.0 entry in [CHANGELOG.md](CHANGELOG.md)). It ships as the zero-dependency `geneseed` package (`geneseed`, `geneseed-hook`, `geneseed-build`), so `npx geneseed setup` needs no clone and nothing else installed; `geneseed migrate` moves an existing checkout install across. Node is the only runtime it asks for: the `token-report` skill's own script is `token_report.mjs`, gated over seeded transcripts for all four hosts, and `daydream` calls `node -e` | `2026-08-06-npx-distribution` |
|
|
49
49
|
| **Runtime awareness** | MCP discovery, web research, tool-call batching, review discipline — carried by the doctrine packs (`ops 1` tool discovery, `process 4` read the docs first, `rigor 2`/`rigor 3` honest tests and cover-and-verify), not by the invariants | `2026-06-07-runtime-awareness-and-review-discipline` |
|
|
50
50
|
| **Shared tier** | One machine-wide folder (`~/.config/geneseed`) for memory, standing rules, profile, wiki manifest, exclude paths and notes, read by every global install on every host. Layered reads (project over host over shared), a fold in each global emit that moves existing stores aside, `user-rules.draft.md` decided only through the `rule` skill, and `--shared-tier on` for a project install | `2026-11-05-shared-tier` |
|
|
51
51
|
| **Run from anywhere / uninstall** | `link`/`unlink` onto PATH; global uninstall that keeps the memory store | `2026-06-07-version-and-uninstall` |
|
|
@@ -408,8 +408,9 @@ behaviour** — nothing changes the machine's current agent/model unless you opt
|
|
|
408
408
|
- **Default permissions.** A fresh `opencode.json` gets a minimal policy that **asks**
|
|
409
409
|
before `git reflog expire`, `git gc --prune` and a force-push or delete of `main`/`master` —
|
|
410
410
|
**Rule IV**'s territory, in every build; the guard plugin decides every other data loss — and, **on an install that built the `process` pack in**, before every
|
|
411
|
-
`git commit` and `git push` (the host-level backstop for **Consent Before Push
|
|
412
|
-
|
|
411
|
+
`git commit` and `git push` (the host-level backstop for **Consent Before Push**). The
|
|
412
|
+
rule asks only for a commit or push onto the main branch, but a permission glob cannot read
|
|
413
|
+
which branch is checked out, so OpenCode asks for every commit and push. Build with
|
|
413
414
|
`--doctrines` leaving `process` out and those two entries are simply not written.
|
|
414
415
|
The whole block is added only when you have no `permission` key; an existing policy is
|
|
415
416
|
reconciled key by key — Geneseed adds back what a returning pack wants and removes
|
|
@@ -1421,6 +1421,12 @@ function patchSections(patchText) {
|
|
|
1421
1421
|
|
|
1422
1422
|
// The checks still owed, judged over the previous turn and the current one: a reminder lasts
|
|
1423
1423
|
// one turn, not the whole session. Our own injected messages (`geneseed-*` ids) open no turn.
|
|
1424
|
+
// BACKGROUND RUNS: js/hosts/hooks-done.mjs holds a Claude Code `run_in_background` launch as
|
|
1425
|
+
// pending until its notification says exit 0. Nothing here does. OpenCode 2's bash tool takes
|
|
1426
|
+
// `background: true` ("Background commands return immediately", seen in the @opencode/cli 2.2.5
|
|
1427
|
+
// binary, 2026-11), but V2 is not judged. Whether V1's bash tool has a background mode is
|
|
1428
|
+
// UNVERIFIED (no V1 binary was inspected); if it has one, a launch would pass here, since only a
|
|
1429
|
+
// numeric non-zero `metadata.exit` refuses a completed call.
|
|
1424
1430
|
function doneOwed(messages, checks, root) {
|
|
1425
1431
|
const groups = checks.map((c) => (typeof c === "string" ? { label: c, forms: [c] } : c))
|
|
1426
1432
|
const prompts = []
|
|
@@ -1254,9 +1254,11 @@ const GATE_ASKS = {
|
|
|
1254
1254
|
impact: 'the scan can run for hours', tail: 'search one named directory',
|
|
1255
1255
|
can: 'You can name the directory to search.' }),
|
|
1256
1256
|
// Routine and frequent, so one line: three more would train the user to stop reading all of them.
|
|
1257
|
-
|
|
1258
|
-
|
|
1259
|
-
|
|
1257
|
+
// `strict`: the install asks for every commit and push (`--strict-consent`), not only main's.
|
|
1258
|
+
commit: (f) => ({ rule: 'Consent Before Push', quote: true, short: true,
|
|
1259
|
+
line: f.strict ? 'This command commits or pushes with git, which needs your approval each time.'
|
|
1260
|
+
: 'This command commits or pushes onto the main branch, forces a push, or takes a form the gate cannot read, so it needs your approval.',
|
|
1261
|
+
why: f.strict ? 'every commit and push is your decision' : 'the main branch changes only through a pull request', can: GATE_RUN_IT }),
|
|
1260
1262
|
// The next four are the OpenCode guard's alone: no hook reads a key path, a stream, a wiki manifest
|
|
1261
1263
|
// or an unknown tool's arguments, and the guard only refuses them. `wiki` has no rule to name.
|
|
1262
1264
|
'secret-file': (f) => ({ rule: 'Sealed Secrets', line: `This edit writes to ${gateName(gatePath(f.name))}, a file that holds a secret or key.`,
|
package/bin/geneseed-cli.mjs
CHANGED
|
@@ -387,6 +387,13 @@ async function main(argv) {
|
|
|
387
387
|
// A hook verb (`context`, `tool-gate`, …) is in the table but not here: the emitted
|
|
388
388
|
// settings call it through `geneseed-hook`, and saying so beats "unknown command".
|
|
389
389
|
if (cliCommand(verb) !== null) {
|
|
390
|
+
// Its help is a fair question, and `help context` arrives here as `context --help`: answer
|
|
391
|
+
// it with the hook binary's own help, under a line naming the binary that runs it.
|
|
392
|
+
if (argv.slice(1).some((t) => t === '-h' || t === '--help')) {
|
|
393
|
+
printOut(`'${verb}' is a hook verb: the host runs it as \`geneseed-hook ${verb}\` `
|
|
394
|
+
+ '(bin/geneseed-hook.mjs), not through this command.\n\n');
|
|
395
|
+
return printHelp('geneseed-hook', verb);
|
|
396
|
+
}
|
|
390
397
|
return die(2, `'${verb}' is a hook verb: the host runs it through geneseed-hook `
|
|
391
398
|
+ '(bin/geneseed-hook.mjs), not this command. See geneseed --help.');
|
|
392
399
|
}
|
package/bin/geneseed-hook.mjs
CHANGED
|
@@ -82,7 +82,7 @@ const VERBS = {
|
|
|
82
82
|
flags: HOSTED,
|
|
83
83
|
switches: {
|
|
84
84
|
'--no-consent': 'noConsent', '--no-deletion-gate': 'noDeletionGate', '--no-external-gate': 'noExternalGate',
|
|
85
|
-
'--no-rule-store': 'noRuleStore', '--no-root-scan': 'noRootScan',
|
|
85
|
+
'--no-rule-store': 'noRuleStore', '--no-root-scan': 'noRootScan', '--strict-consent': 'strictConsent',
|
|
86
86
|
},
|
|
87
87
|
},
|
|
88
88
|
'rule-gate': {
|
|
@@ -103,7 +103,7 @@ const VERBS = {
|
|
|
103
103
|
'--no-ownership-gate': 'noOwnershipGate', '--no-external-gate': 'noExternalGate',
|
|
104
104
|
'--no-test-note': 'noTestNote', '--no-rule-store': 'noRuleStore', '--no-root-scan': 'noRootScan',
|
|
105
105
|
// Bob's commit/push warning, when process 5 is off: `gitDecide` reads it as on git-gate.
|
|
106
|
-
'--no-consent': 'noConsent',
|
|
106
|
+
'--no-consent': 'noConsent', '--strict-consent': 'strictConsent',
|
|
107
107
|
},
|
|
108
108
|
},
|
|
109
109
|
learn: {
|
|
@@ -238,7 +238,7 @@ function hostNamed(argv) {
|
|
|
238
238
|
*/
|
|
239
239
|
function parse(spec, argv) {
|
|
240
240
|
const args = {
|
|
241
|
-
root: null, host: null, event: null, memory: null, consolidate: false, noConsent: false,
|
|
241
|
+
root: null, host: null, event: null, memory: null, consolidate: false, noConsent: false, strictConsent: false,
|
|
242
242
|
noDeletionGate: false, noSecretsGate: false, noDoneGate: false, noOwnershipGate: false,
|
|
243
243
|
noExternalGate: false, noTestNote: false, noRuleStore: false, noRootScan: false, file: null,
|
|
244
244
|
};
|
package/docs/PRD.md
CHANGED
|
@@ -104,7 +104,7 @@ sequenceDiagram
|
|
|
104
104
|
| NFR-002 | The hook is cheap: it loads on every tool call. | ~14 ms to load | Stated in `AGENTS.md`; no automated budget found, `⚠ to confirm` | ◐ | `bin/geneseed-hook.mjs` |
|
|
105
105
|
| NFR-003 | Context hook output stays under the host's cap. | 9 000 characters | `OUTPUT_BUDGET` | ✅ | `js/hosts/hooks-context.mjs` |
|
|
106
106
|
| NFR-004 | The rules file stays within its size ceiling. | 40 312 lean, 66 432 full | `CARRIER_CEILING` | ✅ | `js/inspect/cost.mjs` |
|
|
107
|
-
| NFR-005 | The generator and hook path cannot spawn beyond what is declared. | No `child_process` on the generator;
|
|
107
|
+
| NFR-005 | The generator and hook path cannot spawn beyond what is declared. | No `child_process` on the generator; two spawn sites on the hook path (`learn`'s model CLI, `loss.mjs`'s one `git` read) | Closure walks | ✅ | `tests/unit/hook_cli.test.mjs` |
|
|
108
108
|
| NFR-006 | The upgrade doctor gate is bounded. | 300 s | A timeout reports a gate that did not finish | ✅ | `js/maintain/update.mjs` |
|
|
109
109
|
| NFR-007 | The console serves only this machine. | Local port 4747 by default, with request guards | [Web console security](web-ui.md#security-model) | ✅ | `js/web/server.mjs` |
|
|
110
110
|
| NFR-008 | Runs on Windows, macOS and Linux with no build step. | CI: Ubuntu and Windows. macOS: `⚠ to confirm`, no CI row | `web/dist/` tracked; `install`, `install.cmd`, `install.command` | ◐ | `.github/workflows/ci.yml` |
|
package/docs/README.md
CHANGED
|
@@ -30,6 +30,7 @@
|
|
|
30
30
|
| Set up | [MCP servers](guides/mcp.md) · [MarkItDown](guides/mcp-markitdown.md) · [GitLab](guides/mcp-gitlab.md) · [Filesystem](guides/mcp-filesystem.md) · [Reading non-markdown docs](guides/read-non-markdown.md) | Where the config lives, the three presets, and reading PDF and Office files |
|
|
31
31
|
| Loops | [Run a loop](guides/run-a-loop.md) · [Which loop template](guides/loop-which-template.md) · [While a loop runs](guides/loop-running.md) · [Finish a loop](guides/loop-finish.md) | Working a requirement as small, validated, committed iterations |
|
|
32
32
|
| Factories | [Run a factory](guides/run-a-factory.md) | Carrying one bug report or issue to an open PR with green CI |
|
|
33
|
+
| Factories | [Auto-merge green PRs](guides/auto-merge.md) | Letting the forge merge a PR the agent opens once its required checks pass |
|
|
33
34
|
| Keep it running | [Upgrade](guides/upgrade.md) | Getting a new version onto every install |
|
|
34
35
|
| Keep it running | [Upgrade to 5.0](guides/upgrade-to-5.md) | A 4.x machine reaching 5.0: what moves, what to check, how to go back |
|
|
35
36
|
| Keep it running | [Migrate from a clone to npm](guides/migrate.md) | Moving an old clone install to the npm package |
|
package/docs/concepts/agents.md
CHANGED
|
@@ -36,7 +36,7 @@ Ten read-only debaters — `advocate`, `skeptic`, `pragmatist`, `steward`, `oper
|
|
|
36
36
|
|
|
37
37
|
An agent is picked by **what the work needs**, not by **where the file lives**. There is no "agent for `src/api/`": a change to any folder goes to the `developer`, and its review to the `reviewer`. You can name one ("have the reviewer look at this"), or let the main session route the request to the right specialist itself.
|
|
38
38
|
|
|
39
|
-
In [foreman mode](foreman-mode.md) the session
|
|
39
|
+
In [foreman mode](foreman-mode.md) the session hands each task that would block it to one background `developer` worker. A pipeline crew — explorer, developer and tester, plus whatever specialists the task needs — runs only when you ask for one.
|
|
40
40
|
|
|
41
41
|
### Agents learn too
|
|
42
42
|
|
|
@@ -22,7 +22,7 @@ A **posture** is the register the agent works in. You choose it at setup and it
|
|
|
22
22
|
| **assistant** | precise execution, low initiative — you steer |
|
|
23
23
|
| **artisan** | a peer with toolsmith reflexes — terminal-first, automates repetition |
|
|
24
24
|
|
|
25
|
-
Posture is separate from the [theme](themes.md): the theme is the *voice*, the posture is the *relationship*. Every posture obeys the same rules; what shifts is how firmly and how loudly the agent voices disagreement. Change it with `geneseed setup`, the web console's
|
|
25
|
+
Posture is separate from the [theme](themes.md): the theme is the *voice*, the posture is the *relationship*. Every posture obeys the same rules; what shifts is how firmly and how loudly the agent voices disagreement. Change it with `geneseed setup`, the install's panel on the web console's Installs page, or:
|
|
26
26
|
|
|
27
27
|
```bash
|
|
28
28
|
geneseed build --emit claude-global --posture mentor
|
|
@@ -38,7 +38,7 @@ The **Pact** is stated in the first section of the Ethos, the layer that is alwa
|
|
|
38
38
|
2. serve your intent;
|
|
39
39
|
3. keep its own honesty.
|
|
40
40
|
|
|
41
|
-
Unusually,
|
|
41
|
+
Unusually, the Pact also has a side that *you* owe back. The install's text only points to it; the README states it:
|
|
42
42
|
|
|
43
43
|
- **Don't punish candour.** When the agent contradicts you with evidence, flags a risk or admits a doubt, that is the Pact working. Penalising it teaches the agent to flatter.
|
|
44
44
|
- **Give the context up front.** The agent cannot weigh what it was not told.
|
|
@@ -24,9 +24,9 @@ silently guarding the wrong rule after a renumber. See [ADR 0005](../adr/0005-st
|
|
|
24
24
|
| `sealed-secrets` | law | ask: rule-gate (credential-shaped content outside `.env*`). Switchable per install with `--no-secrets-gate` (see [Exclusions](exclusions.md)): this scan stands down on every host, the guard plugin's path block included | same as Claude Code | block: guard plugin (key/credential file path, or vendor-prefixed secret content); warns only on `.env*` | block (exit 2) |
|
|
25
25
|
| `deletion-is-deliberate` | law | ask: git-gate, only on real data loss judged against the repository's state (the list in [Hooks](hooks.md): a protected branch deleted or force-pushed, an unpushed unmerged branch deleted, unpushed commits abandoned by `reset --hard`, uncommitted work discarded other than by `reset --hard`, a stash dropped, the reflog pruned, files git cannot restore removed); asks when it cannot verify. Switchable per install with `--no-deletion-gate` (see [Exclusions](exclusions.md)): the real-loss check and the Law IV `permission.bash` keys stand down, everything else in this table stays **+** ask: git-gate, catastrophic shell (`rm -rf` of `/`, a drive root or `~`, `mkfs`, `dd` over a raw disk, `format`, fork bomb), whatever the state and even with the switch off | same as Claude Code | ask: permission prompt (`git reflog expire*`, `git gc --prune*`, a force push or delete of `main`/`master` by name) **+** block: guard plugin (catastrophic shell, the hook's check plus its own stricter text match: `rm -rf` of `/`, a drive root or `~`, fork bomb, `format`, `dd` over a raw disk) **+** block: guard plugin (every other real-loss case, the same state-aware decisions as the hook) | block (exit 2) |
|
|
26
26
|
| `persist-insight` | process | ask: rule-gate (a write to `user-rules.md` or `user-rules.draft.md`; memory is written freely, and the [change report](hooks.md#the-change-report) and the web console show it). Togglable: build without the process pack, or drop this rule alone with `--exclude-rules`: the hook goes on every host (`--no-rule-store`), OpenCode's `permission.edit` keys on the rule files too. The change report still lists rule-file changes | same as Claude Code | ask: OpenCode's own prompt (`permission.edit`, and `evaluate` on OpenCode 2); the guard plugin refuses a file-tool write the host cannot prompt for | block a file-tool write: exit 2, no ask tier; a parsed shell write only warns |
|
|
27
|
-
| `consent-before-push` | process | ask: git-gate (
|
|
27
|
+
| `consent-before-push` | process | ask: git-gate, on a commit or push onto the main branch (`main`, `master`, a remote's default branch, or the branch the main checkout holds when the command runs in a linked worktree). Off the main branch, a session's commit, local merge and plain push of the checked-out branch (`git push [-u] <remote> <branch>`, or `HEAD:<branch>`) pass. A bare `git push`, a push of another branch, a forced push, a tag push, or any form the gate cannot read still asks, and so does everything in a repository with no remote or whose remote has no default branch recorded (`git remote set-head origin --auto`). A sub-agent's push always asks. With `--strict-consent` (the *Strict consent* switch on the console's Constitution page), every commit and push asks again, as before 2026-11. A sub-agent's commit or merge (`agent_id` in the payload) in a linked worktree, on a branch that is not shared, passes: a Foreman worker's own batch ([Foreman mode](foreman-mode.md) has the exact conditions). A git hook or `core.hooksPath` that pushes on commit is not seen. A push, or a command that mixes one in, still asks. Togglable: build without the process pack, or drop this rule alone with `--exclude-rules` (see [Exclusions](exclusions.md)). Only this question drops; the `deletion-is-deliberate` gate stays. | same as Claude Code | ask: permission prompt (`git commit*`/`git push*`), wired only when the process pack is on; a `loop/*` push is statically allowed. A glob sees only the command, never the worktree, so a worker's commit still asks | log only |
|
|
28
28
|
| `external-gate` | rigor | ask: rule-gate (a write under a project's `.geneseed/protected-checks.txt` list, or to a gate's own configuration: hook settings, `excludes.json`, `AGENT.md` gate markers, the hook shim) | same as Claude Code | ask: OpenCode's own `permission.edit` rules, written by the emit (every `opencode.json(c)`, the hook settings, the install's `AGENT.md`, `excludes.json`, manifest, plugins, the hook shim); block: guard plugin (the protected-checks list, and the other hosts' Geneseed-only files) | block (exit 2), writes only; a hook `settings.json` only when the edit changes Geneseed's own hook entries |
|
|
29
|
-
| `verify-before-asserting` | law | block at Stop,
|
|
29
|
+
| `verify-before-asserting` | law | block at Stop, again only after a new edit or a changed background verdict, at most 3 times per continuation and 10 per turn: the done gate in `learn`, at SubagentStop too for a sub-agent's own turn (a turn that edited files, while a check in the project's `.geneseed/done-checks.txt` has not passed since the last edit). Without that file, the checks are inferred from the git root's manifests and only warn (a `systemMessage` at Stop, never a block); switchable per install with `--no-done-gate` (see [Exclusions](exclusions.md)) | same as Claude Code (a frozen fork, and no check runs a model turn: [What is verified](host-matrix.md#what-is-verified)); that its SubagentStop sends `agent_transcript_path` is unverified, and without it a sub-agent's turn is not judged | remind: context plugin, on the next request (OpenCode 1 only; OpenCode 2 is not judged, and logs so) | not judged: Stop carries no transcript (log line) |
|
|
30
30
|
| `commands-must-return` | ops | ask: git-gate (a recursive scan rooted at a filesystem root: `find /`, `du`, `grep -r`, `rg`, `Get-ChildItem -Recurse` at `/`, `/c`, `C:\`). Togglable: build without the ops pack, or drop this rule alone with `--exclude-rules`: the check goes on every host (`--no-root-scan`) | same as Claude Code | block: guard plugin (same root-scan pattern) | block (exit 2) |
|
|
31
31
|
|
|
32
32
|
Bob has no "ask" tier (see [ADR 0007](../adr/0007-gates-fail-closed-per-host-ceiling.md)), so a
|
|
@@ -45,6 +45,9 @@ not a boundary:** `bash -c`, `pwsh -c`, an interpreter and a variable stay unrea
|
|
|
45
45
|
command permission is the backstop, and the [change report](hooks.md#the-change-report) tells you
|
|
46
46
|
afterwards.
|
|
47
47
|
|
|
48
|
+
No host gates a forge merge (`gh pr merge`, `glab mr merge`, an MCP merge tool): the
|
|
49
|
+
[auto-merge guide](../guides/auto-merge.md) says what guards it instead.
|
|
50
|
+
|
|
48
51
|
See [ADR 0008](../adr/0008-host-parity-ceiling-of-the-weakest-host.md) for why a gate that only
|
|
49
52
|
one host can run still ships for every host it can.
|
|
50
53
|
|
|
@@ -58,11 +58,13 @@ geneseed build --emit claude-global --exclude-rules "process 7"
|
|
|
58
58
|
|
|
59
59
|
The install records it (`Excluded rules: process 7` beside its pack list) and every rebuild and upgrade keeps it. If a later version retires the rule, the rebuild prints a WARN, drops that address, and goes on. The WARN says what the exclusion no longer does: comms 5 (*Mark the Ask*) merged into comms 1 on 2026-11-08, so excluding `comms 5` no longer removes the ask markers, which now bind inside comms 1. If a new rule later takes a retired rule's address, an old exclusion of that address removes the new rule; the build then prints a loud WARN that names both rules, and the exclusion still applies until you remove it. The always-on Rules and the Ethos cannot be excluded.
|
|
60
60
|
|
|
61
|
+
**Its citations go with it.** The instructions file stops citing an excluded rule: a parenthetical such as `(*Consent Before Push*)` after a sentence is removed, and in a list of citations only that name goes. A mention in running prose ("Where *Search Before Creating* refuses …") stays, because it describes a relation and binds nothing. The rule files on disk keep every citation, because they are the complete text. `geneseed doctor` refuses a parenthetical in the instructions-file sources that mixes a doctrine citation with other words, because the render could not remove it cleanly.
|
|
62
|
+
|
|
61
63
|
**A hook goes with its rule.** Three doctrine rules are also enforced by a hook with no switch of its own, and excluding the rule, or building without its pack, drops that hook in the same rebuild. Including the rule again re-arms it at the next rebuild.
|
|
62
64
|
|
|
63
65
|
| Rule | What stops | Flag |
|
|
64
66
|
| --- | --- | --- |
|
|
65
|
-
| process 5, *Consent Before Push* | the commit/push ask of `git-gate` and OpenCode's `git commit*`/`git push*` keys. Bob keeps its warning line | `--no-consent` |
|
|
67
|
+
| process 5, *Consent Before Push* | the main-branch commit/push ask of `git-gate` (every commit and push under `--strict-consent`) and OpenCode's `git commit*`/`git push*` keys. Bob keeps its warning line | `--no-consent` |
|
|
66
68
|
| process 1, *Persist Insight* | the ask (on Bob the block or warning) on a write to `user-rules.md` or `user-rules.draft.md`, by write tool or parsed shell write, the hard-link check included: `rule-gate`, `git-gate`, Bob's `tool-gate`, the OpenCode guard, and OpenCode's `permission.edit` keys on those files | `--no-rule-store` |
|
|
67
69
|
| ops 2, *Commands Must Return* | the root-scan check of `git-gate`, Bob's `tool-gate` and the OpenCode guard | `--no-root-scan` |
|
|
68
70
|
|
|
@@ -111,10 +113,22 @@ The console's Constitution page has a switch on Rule I's and Rule III's rows too
|
|
|
111
113
|
|
|
112
114
|
What stops, per host:
|
|
113
115
|
- **`--no-secrets-gate`**: the credential scan of `rule-gate` (Claude Code, OpenClaude) and of `tool-gate` (Bob, which then no longer exits 2 for it), and on OpenCode the guard plugin's *Sealed Secrets* block — both the key/credential file path block and the content scan. *External Gate*, *Persist Insight*, the deletion gate and the root-scan check stay.
|
|
114
|
-
- **`--no-done-gate`**: the done check `learn` runs on Stop, listed or inferred (Claude Code, OpenClaude; on Bob, the "turn not judged" log line), and on OpenCode the context plugin's reminder (OpenCode 1), its one-line notice (OpenCode 2), and on every host the `Done gate:` line at session start. Learning itself still runs, and `.geneseed/done-checks.txt` stays protected by *External Gate*.
|
|
116
|
+
- **`--no-done-gate`**: the done check `learn` runs on Stop and SubagentStop, listed or inferred (Claude Code, OpenClaude; on Bob, the "turn not judged" log line), and on OpenCode the context plugin's reminder (OpenCode 1), its one-line notice (OpenCode 2), and on every host the `Done gate:` line at session start. Learning itself still runs, and `.geneseed/done-checks.txt` stays protected by *External Gate*.
|
|
115
117
|
|
|
116
118
|
Limits: OpenCode reads both switches from the install's `AGENT.md` when it starts, so restart it after flipping one. A global install beside a project install: `rule-gate` and Bob's `tool-gate` do not stand down for a project install on any host, and neither does the OpenCode guard, so an armed global install still asks about (or blocks) a credential write inside a project whose own install has the secrets gate off. `learn` does stand down on Claude Code and OpenClaude, so there the project's done gate switch decides. And the older-shim limit above is sharper for the done gate: its flag rides on `learn`, so while the shim points at an older checkout an install with the done gate off **loses learning too**, not only the gate. Run `geneseed rebuild-all` before switching either gate off.
|
|
117
119
|
|
|
120
|
+
### Strict consent — every commit and push asks
|
|
121
|
+
|
|
122
|
+
By default *Consent Before Push* asks only for a commit or push onto the main branch: your own branch takes commits, local merges and plain pushes without a prompt. Strict consent brings back the ask on every commit and push.
|
|
123
|
+
|
|
124
|
+
```bash
|
|
125
|
+
geneseed build --emit claude-global --strict-consent
|
|
126
|
+
```
|
|
127
|
+
|
|
128
|
+
The console's Constitution page has the same switch on the rule's row (*Strict consent*). The install records `Own-branch pass: off` beside the other gate markers, the carrier adds one sentence under the rule, and rebuilds, upgrades and `geneseed status` carry it. The switch adds asks, so its flag does not read `--no-*`; the marker still follows the gate-switch contract: written only when the pass is off.
|
|
129
|
+
|
|
130
|
+
What changes, per host: `git-gate` on Claude Code and OpenClaude asks for every commit and push again (the `loop/*` and Foreman worker passes stay), and Bob's `tool-gate` prints its warning line for each. OpenCode is unchanged: its `git commit*`/`git push*` keys already ask for every one. With process 5 excluded, the switch does nothing, because no consent check runs.
|
|
131
|
+
|
|
118
132
|
### External Gate and the test note — on or off
|
|
119
133
|
|
|
120
134
|
Two more switches. Both are armed by default and written only when off, so an armed install does not change.
|
|
@@ -59,6 +59,6 @@ Footprint is stored in a `.geneseed-footprint` marker in the install and kept ac
|
|
|
59
59
|
geneseed build --emit claude-global --footprint full
|
|
60
60
|
```
|
|
61
61
|
|
|
62
|
-
On the command line, a flag you leave out takes the generator's default, not the install's current value. `geneseed status --json` shows
|
|
62
|
+
On the command line, a flag you leave out takes the generator's default, not the install's current value. A build that would change a setting of an existing install that you did not pass refuses: it lists each change and prints the command that keeps them. `geneseed status --json` shows that command for every install. Add `--reset` only to accept the defaults.
|
|
63
63
|
|
|
64
64
|
The walkthrough for all build-time choices is [Choose your setup](../guides/choose-your-setup.md).
|
|
@@ -76,7 +76,7 @@ A worker or crew commits only in its own worktree, never pushes, and never merge
|
|
|
76
76
|
2. shows you the diff from the base it recorded, and the green output;
|
|
77
77
|
3. commits and merges **only once you accept**.
|
|
78
78
|
|
|
79
|
-
Push, and every merge beyond a worker's own branch, belong to the session alone, under *Consent Before Push
|
|
79
|
+
Push, and every merge beyond a worker's own branch, belong to the session alone, under *Consent Before Push*: the session pushes the worker's branch and lands it on the main branch through a pull request with green checks ([Rules](rules.md)). A worker or crew that cannot get to green reports back instead of landing broken work.
|
|
80
80
|
|
|
81
81
|
You can also start a pipeline without foreman mode: ask the agent to "run a pipeline" for a task, and the `pipeline` [skill](skills.md) takes it from there.
|
|
82
82
|
|
|
@@ -10,7 +10,7 @@ How Geneseed's [hooks](hooks.md) behave when something goes wrong, where they ar
|
|
|
10
10
|
|
|
11
11
|
## Gates fail closed, and leave a trace
|
|
12
12
|
|
|
13
|
-
If a gate cannot evaluate a call — an unreadable payload, a bug — it asks, with the error as its reason, rather than silently letting the call through. Every prompt a gate raises adds one line to `notebook/gates.jsonl` in the install: the rule and the
|
|
13
|
+
If a gate cannot evaluate a call — an unreadable payload, a bug — it asks, with the error as its reason, rather than silently letting the call through. Every prompt a gate raises adds one line to `notebook/gates.jsonl` in the install: the time, the verb, the rule and the working directory, never the command or content. `geneseed status` counts them by rule.
|
|
14
14
|
|
|
15
15
|
```bash
|
|
16
16
|
geneseed status
|
|
@@ -34,10 +34,10 @@ The merge is surgical. Every other key and every hook of your own survive, and t
|
|
|
34
34
|
|
|
35
35
|
**OpenClaude** is a Claude Code fork: it gets the same hooks and the same prompts, unchanged.
|
|
36
36
|
|
|
37
|
-
**Bob** has its own contract. It uses Claude's event names but ignores a hook's output before a tool call — the only way to refuse is exit code 2 — and it has no tool matcher
|
|
37
|
+
**Bob** has its own contract. It uses Claude's event names but ignores a hook's output before a tool call — the only way to refuse is exit code 2 — and it has no `SubagentStop`. Bob does document a regex matcher on the tool name, but Geneseed wires none: Bob's tool list and regex dialect are unverified, and a wrong matcher would silence the gate. Bob 2.2.3 does have `PreCompact` and `PostCompact`, but Geneseed does not wire them yet. So Bob gets four hooks:
|
|
38
38
|
|
|
39
39
|
- `SessionStart` → `geneseed-hook context`.
|
|
40
|
-
- `PreToolUse` → `geneseed-hook tool-gate`, the git gate and the rule gate fused into one command that decides from the shape of the call. It **blocks** (exit 2) exactly the rules whose Bob cell says *block* in [Rule enforcement, by host](enforcement-table.md). The commit/push check and a shell write to a rule store become a warning line, because a hard block would leave Bob unable to commit at all. The [ownership](ownership.md) gate also exits 2, but only once per session and repo: the same write passes after the developer answers.
|
|
40
|
+
- `PreToolUse` → `geneseed-hook tool-gate`, the git gate and the rule gate fused into one command that decides from the shape of the call. (On Claude Code and OpenClaude the same verb only counts skill and subagent calls: see [Hooks](hooks.md).) It **blocks** (exit 2) exactly the rules whose Bob cell says *block* in [Rule enforcement, by host](enforcement-table.md). The commit/push check and a shell write to a rule store become a warning line, because a hard block would leave Bob unable to commit at all. The [ownership](ownership.md) gate also exits 2, but only once per session and repo: the same write passes after the developer answers.
|
|
41
41
|
- `Stop` → `geneseed-hook learn`. Bob's `Stop` carries no transcript, so nothing is learned there; the [change report](hooks.md#the-change-report) still runs.
|
|
42
42
|
- `UserPromptSubmit` → `geneseed-hook activity`, which records the turn for the Activity view.
|
|
43
43
|
|