geneseed 5.0.3 → 5.1.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 +83 -0
- package/README.md +3 -3
- package/SHIPPED.md +2 -2
- package/adapters/claude-code/README.md +5 -1
- package/adapters/openclaude/README.md +3 -1
- package/adapters/opencode/plugins/geneseed-workflow.js +1 -1
- package/adapters/opencode/workflows/_runtime.js +1 -1
- package/bin/geneseed-cli.mjs +3 -0
- package/bin/geneseed-hook.mjs +10 -2
- package/docs/PRD.md +1 -1
- package/docs/README.md +4 -1
- package/docs/concepts/enforcement-table.md +1 -1
- package/docs/concepts/exclusions.md +1 -1
- package/docs/concepts/factories.md +203 -0
- package/docs/concepts/hooks.md +1 -1
- package/docs/concepts/host-matrix.md +1 -0
- package/docs/concepts/loop-gates.md +6 -0
- package/docs/concepts/loops.md +1 -0
- package/docs/concepts/rules.md +1 -1
- package/docs/concepts/shared-tier.md +14 -0
- package/docs/extending.md +5 -1
- package/docs/guides/autostart.md +2 -0
- package/docs/guides/migrate.md +1 -1
- package/docs/guides/run-a-factory.md +116 -0
- package/docs/guides/set-up-ownership.md +1 -0
- package/docs/guides/upgrade-to-5.md +2 -2
- package/docs/reference/factory-actions.md +22 -0
- package/docs/reference/loop-actions.md +1 -1
- package/docs/reference/plugin-activity.md +1 -1
- package/docs/web-ui.md +47 -2
- package/harness.config.json +1 -1
- package/js/README.md +21 -2
- package/js/build/args.mjs +44 -12
- package/js/build/emit-claude.mjs +3 -0
- package/js/build/emit-opencode.mjs +4 -0
- package/js/build/retired-skills.mjs +158 -0
- package/js/build/source.mjs +41 -2
- package/js/cli-table.json +193 -3
- package/js/factory/cli.mjs +194 -0
- package/js/factory/graph.mjs +309 -0
- package/js/factory/registry.mjs +71 -0
- package/js/factory/state.mjs +511 -0
- package/js/hosts/activity.mjs +3 -3
- package/js/hosts/done-checks.mjs +3 -2
- package/js/hosts/geneseed-dir.mjs +1 -1
- package/js/hosts/gitref.mjs +21 -0
- package/js/hosts/hooks-context.mjs +63 -9
- package/js/hosts/hooks-prims.mjs +1 -1
- package/js/hosts/memory-files.mjs +4 -2
- package/js/hosts/settings.mjs +5 -4
- package/js/inspect/checks-authoring.mjs +11 -1
- package/js/inspect/cost.mjs +91 -5
- package/js/inspect/doctor.mjs +2 -1
- package/js/inspect/inventory.mjs +1 -1
- package/js/loop/catalog.mjs +30 -12
- package/js/loop/cli.mjs +27 -15
- package/js/loop/graph.mjs +13 -4
- package/js/loop/registry.mjs +65 -28
- package/js/loop/state.mjs +18 -8
- package/js/maintain/migrate.mjs +39 -25
- package/js/web/api.mjs +43 -1
- package/js/web/catalog.mjs +38 -2
- package/js/web/daemon.mjs +191 -6
- package/js/web/handler.mjs +27 -5
- package/js/web/routes.mjs +10 -3
- package/js/web/server.mjs +4 -1
- package/package.json +1 -1
- package/registry.json +14 -0
- package/src/AGENT.md.tmpl +5 -7
- package/src/bricks/checks.md +62 -0
- package/src/bricks/docs-update.md +5 -0
- package/src/bricks/holdout-write.md +23 -0
- package/src/bricks/holdout.md +25 -0
- package/src/bricks/intake.md +27 -0
- package/src/bricks/merge-gate.md +31 -0
- package/src/bricks/pr-open.md +21 -0
- package/src/bricks/retro.md +22 -0
- package/src/bricks/review-panel.md +43 -0
- package/src/bricks/spec.md +20 -6
- package/src/bricks/test.md +4 -1
- package/src/bricks/triage.md +19 -0
- package/src/doctrines/comms.md +29 -41
- package/src/doctrines/craft.md +3 -10
- package/src/doctrines/ops.md +4 -15
- package/src/doctrines/rigor.md +1 -5
- package/src/factories/analysis-to-build.json +52 -0
- package/src/factories/bug-report-to-fix.json +50 -0
- package/src/factories/issue-to-pr.json +67 -0
- package/src/skills/_checkpoints.md +1 -0
- package/src/skills/adhd.md +1 -1
- package/src/skills/factory-forge.md +115 -0
- package/src/skills/factory.md +196 -0
- package/src/skills/loop.md +3 -2
- package/src/skills/parallel-agents.md +1 -1
- package/src/skills/workflow.md +2 -1
- package/themes/_TEMPLATE.json +4 -2
- package/themes/biker.json +4 -2
- package/themes/commentator.json +4 -2
- package/themes/cyberpunk.json +4 -2
- package/themes/gamer.json +4 -2
- package/themes/imperial.json +4 -2
- package/themes/joker.json +4 -2
- package/themes/marvin.json +4 -2
- package/themes/mean.json +4 -2
- package/themes/military.json +4 -2
- package/themes/neutral.json +4 -2
- package/themes/pirate.json +4 -2
- package/themes/sports.json +4 -2
- package/themes/verstappen.json +4 -2
- package/themes/wizard.json +4 -2
- package/web/dist/assets/ActiveLoops-BTHIaRhn.js +1 -0
- package/web/dist/assets/{Activity-Ck_Xffpo.js → Activity-CpkBwpu7.js} +1 -1
- package/web/dist/assets/{ActivityDetail-CBxVS4mU.js → ActivityDetail-DTPziZWM.js} +1 -1
- package/web/dist/assets/{Bonsai-BlOwsvW6.js → Bonsai-hiG_gGNU.js} +1 -1
- package/web/dist/assets/{CopyButton-DFMOIGbe.js → CopyButton-DUIUfNp6.js} +1 -1
- package/web/dist/assets/Dashboard-Dnw6EyX7.js +2 -0
- package/web/dist/assets/{Docs-D_2Jt6gU.js → Docs-BEET_l16.js} +2 -2
- package/web/dist/assets/Factories-D6KXkfWw.js +1 -0
- package/web/dist/assets/{GreenhouseView-WalcX5bp.js → GreenhouseView-BKxy5apE.js} +1 -1
- package/web/dist/assets/{Installs-UGiPDMDt.js → Installs-CnFVlVD0.js} +3 -3
- package/web/dist/assets/{JournalView-CZtXQz-v.js → JournalView-ChFitHjo.js} +1 -1
- package/web/dist/assets/{Kits-XQHsazCN.js → Kits-CcR-OlwQ.js} +1 -1
- package/web/dist/assets/Laws-B1s5idOg.js +4 -0
- package/web/dist/assets/LibRows-BZgdbI1l.js +1 -0
- package/web/dist/assets/Library-x6TkkEVF.js +3 -0
- package/web/dist/assets/Loops-BH93KKxn.js +2 -0
- package/web/dist/assets/{OperatorHudView-CeDw5qMB.js → OperatorHudView-BO0aIKPL.js} +1 -1
- package/web/dist/assets/{Personal-PVmGA2-M.js → Personal-CE_0Vhh0.js} +2 -2
- package/web/dist/assets/{Settings-DWuxwh4i.js → Settings-CbpZvVN_.js} +1 -1
- package/web/dist/assets/{Tabs-d2RIRAKT.js → Tabs-C2oW7oEj.js} +1 -1
- package/web/dist/assets/api-DLDVY3K-.js +1 -0
- package/web/dist/assets/{index-BNttaGQb.js → index-BQwOmbor.js} +3 -3
- package/web/dist/assets/index-CuIop_pO.css +1 -0
- package/web/dist/index.html +3 -3
- package/web/dist/assets/Dashboard-BUdUTjbB.js +0 -2
- package/web/dist/assets/Laws-B6A55S-2.js +0 -4
- package/web/dist/assets/Library-D7L0Wdbh.js +0 -3
- package/web/dist/assets/Loops-C0loS73u.js +0 -2
- package/web/dist/assets/RailCats-BGZnJ6fa.js +0 -1
- package/web/dist/assets/api-BMFDSXoB.js +0 -1
- package/web/dist/assets/index-BEI5ugYQ.css +0 -1
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: merge-gate
|
|
3
|
+
description: Wait for the pull request's CI, at most 30 minutes, and report green, red, or no verdict (no CI, or none readable). Never merges.
|
|
4
|
+
effect: read
|
|
5
|
+
agent: tester
|
|
6
|
+
gate: human
|
|
7
|
+
gateOn: none
|
|
8
|
+
outcomes: pass, fail, none
|
|
9
|
+
---
|
|
10
|
+
Wait with a command that returns by itself, never a foreground `sleep`: `gh pr checks <pr> --watch
|
|
11
|
+
--interval 30`, or `glab ci status --wait --branch <this branch>`. Bound each call under 10
|
|
12
|
+
minutes, by your shell tool's timeout or `timeout 540` in a POSIX shell, and repeat it up to 30
|
|
13
|
+
minutes in all. Then read the verdict once: `gh pr checks <pr> --json name,bucket,link`, or
|
|
14
|
+
`glab ci status --branch <this branch>`. A PR pushed moments ago may show no checks yet, and a
|
|
15
|
+
watch then returns at once: re-check for about 2 minutes before you conclude it has none. Never
|
|
16
|
+
merge, re-run or cancel a check, and never edit any file.
|
|
17
|
+
|
|
18
|
+
The verdict is each check's `bucket` (`pass`, `fail`, `pending`, `skipping`, `cancel`), or each
|
|
19
|
+
job's state in `glab`'s output, never the exit code. `gh pr checks` exits non-zero on a readable
|
|
20
|
+
verdict: 1 when a check is red, 8 when one is pending. That is a verdict, not an environment
|
|
21
|
+
failure: read the output it printed.
|
|
22
|
+
|
|
23
|
+
Report `pass` when every check is green. Report `fail` when one is red — for each failing check,
|
|
24
|
+
its name and the cause read from its log (`gh run view <id> --log-failed`), never guessed from its
|
|
25
|
+
title. Report `none` when the repo runs no CI on this PR: the user decides whether the run goes
|
|
26
|
+
on. Report `none` too, with the finding starting `environment:` and the cause, when no verdict
|
|
27
|
+
can be read: checks still pending after 30 minutes, `gh`/`glab` missing or unusable (not logged
|
|
28
|
+
in, no access to the repo), or output you cannot read as checks and their states. An
|
|
29
|
+
environment failure is never a `fail`: a `fail` goes back to the loop, whose code cannot fix it,
|
|
30
|
+
and `none` holds for the user. Write the findings to a file in the OS temp directory and report
|
|
31
|
+
that file's path.
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: pr-open
|
|
3
|
+
description: Push the run's branch and open its pull request, or update the one already open. Never merges.
|
|
4
|
+
effect: read
|
|
5
|
+
skill: ship
|
|
6
|
+
outcomes: pass, fail
|
|
7
|
+
---
|
|
8
|
+
Follow the `ship` skill's pull-request path only: never merge, never enable auto-merge, never
|
|
9
|
+
push to any branch but this worktree's own. First look for a PR already open on this branch
|
|
10
|
+
(`gh pr view --json url,state` or `glab mr view`): after a rework lap it exists, and this stage
|
|
11
|
+
only pushes the new commits to it.
|
|
12
|
+
|
|
13
|
+
Push with `git push -u origin HEAD:<this branch>`. The push asks the user: wait for that answer,
|
|
14
|
+
never work around it. With no PR yet, open one (`gh pr create` / `glab mr create`) titled from the
|
|
15
|
+
run's title, its body built from the run's `requirement` and `input` (as `next` gives them) and
|
|
16
|
+
the branch's commit subjects (`git log --oneline origin/<default>..HEAD`; the loop's notes left
|
|
17
|
+
with its `LOOP.md`), naming the issue it closes when the input was one. Change no file in the worktree.
|
|
18
|
+
|
|
19
|
+
Report `pass` with the PR URL in a file in the OS temp directory — report that file's path. Report
|
|
20
|
+
`fail` when the push is refused or fails, or the PR cannot be opened, with the exact error in
|
|
21
|
+
such a file.
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: retro
|
|
3
|
+
description: Write the factory run's report — what failed, what was reworked — and keep only a durable lesson in memory.
|
|
4
|
+
effect: read
|
|
5
|
+
agent: docs
|
|
6
|
+
outcomes: pass
|
|
7
|
+
---
|
|
8
|
+
Read `FACTORY.md` (stage history, cycle counters, reason, carry) and the notes of the run's loops.
|
|
9
|
+
A loop's notes leave with its `LOOP.md`, which its close commit removes; read each from git. Find
|
|
10
|
+
the base (`git merge-base HEAD origin/<default>`), list the commits that removed `LOOP.md`, newest
|
|
11
|
+
first: `git log --format=%H --diff-filter=D <merge-base>..HEAD -- LOOP.md`, and read each loop's
|
|
12
|
+
last `LOOP.md` from its parent: `git show <commit>^:LOOP.md`. A `LOOP.md` that was never
|
|
13
|
+
committed (a loop that made no commit) is gone: say so in the report. Then write the run report to `.geneseed/factory-runs/<slug>.md` at the worktree root, `<slug>`
|
|
14
|
+
being the branch name after `loop/factory-`. First run `git check-ignore -q <that path>`: when it
|
|
15
|
+
exits non-zero the path is not ignored, so write the report to the OS temp directory instead.
|
|
16
|
+
The report holds the work item, the PR URL, every stage with its outcome, each rework and its
|
|
17
|
+
reason, each held outcome the user let through with `ok` (above all a locked path `checks`
|
|
18
|
+
reported), and how the run ended (closed, or stopped and why).
|
|
19
|
+
|
|
20
|
+
Change nothing else: no tracked file, no commit. Only a lesson that will hold beyond this run —
|
|
21
|
+
a cause that will recur, a check this project lacks — goes into memory, one entry, under Persist
|
|
22
|
+
Insight; a fact about this run alone stays in the report. Report `pass` with the report's path.
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: review-panel
|
|
3
|
+
description: Review the branch's change with a panel of seats sized to the work item, each blind to how it was built, and merge their verdicts into one.
|
|
4
|
+
effect: read
|
|
5
|
+
skill: factory
|
|
6
|
+
outcomes: pass, fail
|
|
7
|
+
---
|
|
8
|
+
You run this stage yourself and chair it; the seats are agents you dispatch. Never edit a file;
|
|
9
|
+
only put the tree back, as below.
|
|
10
|
+
|
|
11
|
+
Read `size:` and `areas:` from the latest `carry` an `intake` entry left in `FACTORY.md`'s
|
|
12
|
+
`history`, always; a missing or unknown size counts as `large`. That carry is also the work item,
|
|
13
|
+
except in `analysis-to-build`, where the work item text is the approved `specs/<slug>/spec.md`.
|
|
14
|
+
Pick the seats from the factory's `review.seats` in `FACTORY.md`: the list for that size, plus
|
|
15
|
+
the list for each area, each agent once. With no `review.seats`, seat `reviewer` alone.
|
|
16
|
+
|
|
17
|
+
Run `git fetch origin`, find the default branch (`gh repo view --json defaultBranchRef`, or `git
|
|
18
|
+
remote show origin`), then the base, `git merge-base HEAD origin/<default>`, and take the diff
|
|
19
|
+
without the engine files, which the loops commit: `git diff <merge-base> HEAD -- . ':!FACTORY.md'
|
|
20
|
+
':!LOOP.md'`. Dispatch every seat in one parallel batch, each in its own context.
|
|
21
|
+
Each brief holds the work item, the factory's `rules` and the diff (inline for a seat that has no
|
|
22
|
+
shell, such as `steward` or `user-advocate`; else the base commit and that diff command, engine
|
|
23
|
+
files excluded), and states
|
|
24
|
+
three rules: read only the diff and the files it touches, never the history past the diff,
|
|
25
|
+
`LOOP.md`, `FACTORY.md` or the holdout folder; edit no file; return a verdict and its findings,
|
|
26
|
+
nothing else. Never add a loop note, the developer's reasoning or anything from the holdout folder
|
|
27
|
+
to a brief.
|
|
28
|
+
|
|
29
|
+
Chair. These verdicts fail the panel: `reviewer` `block` or `fix-then-ship`; `security`
|
|
30
|
+
`fix-required`; `tester` `STATUS: OK` with a failing test or an acceptance criterion it names
|
|
31
|
+
without a passing test. These pass: `reviewer` `ship`, `security` `safe to ship`, `tester` `STATUS:
|
|
32
|
+
OK` with neither. Advisory, never failing alone: `performance` (`within budget`, `fix-recommended`
|
|
33
|
+
or `cannot-measure`), `steward` and `user-advocate`. No verdict: `tester` `BLOCKED`, `ERROR` or
|
|
34
|
+
`OUT_OF_SCOPE`, a `reviewer` or `security` seat that declines to give one, or a seat that returns
|
|
35
|
+
nothing. Dispatch a seat with no verdict once more; a second time without one fails the panel.
|
|
36
|
+
|
|
37
|
+
Before you record, put the tree back as it was: restore every tracked file a seat changed (`git
|
|
38
|
+
restore --staged --worktree -- <path>`) and delete every untracked file a seat created (a test
|
|
39
|
+
run's output), naming each one in the finding. Never touch `FACTORY.md` or `LOOP.md`: they are
|
|
40
|
+
the run's state. Write one file in the OS temp directory: each
|
|
41
|
+
seat's verdict, then the findings that fail it (`file:line`, what is wrong, what to do instead),
|
|
42
|
+
then the advisory points. Pass on only findings about the diff, and never quote holdout text.
|
|
43
|
+
Report `fail` when any seat failed, else `pass`, with that file's path.
|
package/src/bricks/spec.md
CHANGED
|
@@ -6,13 +6,27 @@ agent: architect
|
|
|
6
6
|
gate: human
|
|
7
7
|
outcomes: pass, fail
|
|
8
8
|
---
|
|
9
|
-
Write `specs/<slug>/spec.md`
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
9
|
+
Write `specs/<slug>/spec.md` and touch nothing else — no code. The slug is the run's: in a factory,
|
|
10
|
+
the factory run's `<slug>` (it never holds the words git, commit or push); in a loop, the slug
|
|
11
|
+
of the loop's title. Write the problem, what is out
|
|
12
|
+
of scope, acceptance criteria in EARS form ("WHEN <trigger> THE SYSTEM SHALL <response>"), each one
|
|
13
|
+
testable, and an ordered task list sized to one `identify` card apiece, ending with an end-to-end
|
|
14
|
+
verification task.
|
|
14
15
|
|
|
15
|
-
|
|
16
|
+
Write the task list in the one form a factory counts. Put it under the spec's first heading that
|
|
17
|
+
contains the word `task` or `tasks` (any case, such as `## Tasks`). Under it, write each task as one
|
|
18
|
+
numbered item, `1.` or `1)`, indented 3 spaces at most; keep every task at the same indent. An
|
|
19
|
+
item indented as far as the text of the task above it (3 spaces under `1. `), numbered or not, is
|
|
20
|
+
a sub-item, not a task. A fenced code block (```` ``` ```` or `~~~`) neither ends the list nor
|
|
21
|
+
adds a task. A deeper heading keeps the list open; the next heading of the same or a higher level
|
|
22
|
+
ends it, `#` or underlined alike. List one task at least, and no more than the factory's task limit: a factory refuses a
|
|
23
|
+
longer list and names its limit (Geneseed's Factory actions reference states it), so split the
|
|
24
|
+
requirement instead.
|
|
25
|
+
|
|
26
|
+
An amendment answers your open questions or corrects the spec: in a factory it arrives as this
|
|
27
|
+
stage's `carry`, in a loop as a note in LOOP.md. Revise the spec to follow it.
|
|
28
|
+
|
|
29
|
+
The user reviews the spec before the work continues. Report `pass` once every criterion is
|
|
16
30
|
testable, with the spec's path and its criteria count in a file in the OS temp directory — report
|
|
17
31
|
that file's path. Report `fail` if a criterion cannot be stated testably: list the open questions
|
|
18
32
|
in such a file and report its path; the user answers them with an amend.
|
package/src/bricks/test.md
CHANGED
|
@@ -15,7 +15,10 @@ brick only observes; a fix belongs in `apply`, not here.
|
|
|
15
15
|
3. **Full suite** — only when everything above passed; otherwise `SKIPPED (an earlier check failed)`.
|
|
16
16
|
|
|
17
17
|
List every check on its own line as `<check>: <status>`, the status one of `PASS`, `FAIL`, `ERROR`
|
|
18
|
-
or `SKIPPED (reason)` — one that did not run is never left out, and silence is never a pass.
|
|
18
|
+
or `SKIPPED (reason)` — one that did not run is never left out, and silence is never a pass. A
|
|
19
|
+
check this project does not have at all (no linter configured, no build step) is not skipped:
|
|
20
|
+
list it as `<check>: N/A (not configured)`. It neither passes nor blocks; never use it for a
|
|
21
|
+
check that exists but was not run.
|
|
19
22
|
Write each failure as four lines: the check's purpose, the property it guards, a one-line
|
|
20
23
|
diagnostic (not the raw log), and the command that reruns it alone. Keep full logs in a file.
|
|
21
24
|
Write the list to a file in the OS temp directory (never inside the worktree) and report that
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: triage
|
|
3
|
+
description: Pick the lane that fits the work item, from the lanes the factory offers, and say why.
|
|
4
|
+
effect: read
|
|
5
|
+
agent: explorer
|
|
6
|
+
outcomes: bug, feature, deps, refactor, docs, fail
|
|
7
|
+
---
|
|
8
|
+
The stage hands you the work item's file as `carry` and the factory's lanes as `lanes`: each
|
|
9
|
+
outcome you may report, with the stage it leads to. Read the work item in full, then the code it
|
|
10
|
+
names. Pick the one outcome that fits: `bug` for a defect with a way to reproduce it, `feature`
|
|
11
|
+
for new behaviour, `deps` for a dependency to raise, `refactor` for a change of structure with no
|
|
12
|
+
change of behaviour, `docs` for a change to the documentation alone. Never report an outcome that
|
|
13
|
+
is not in `lanes`, and never edit any file.
|
|
14
|
+
|
|
15
|
+
Write a file in the OS temp directory, never inside the worktree: one paragraph on why the lane
|
|
16
|
+
fits and why the next-best one does not, then the work item copied in full, so the lane starts
|
|
17
|
+
from it. Report the outcome that names the lane, with that file's path. Report `fail` when no lane
|
|
18
|
+
fits the work item, or it mixes two kinds of work that need two runs — say which, in such a file,
|
|
19
|
+
and report its path.
|
package/src/doctrines/comms.md
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
**{{PACK_COMMS}}** — how answers are presented.
|
|
2
2
|
|
|
3
|
-
### {{DOCTRINE:codes-that-persist}} Codes
|
|
4
|
-
<!-- note: summary: Give tracked items stable
|
|
3
|
+
### {{DOCTRINE:codes-that-persist}} Codes and Markers
|
|
4
|
+
<!-- note: summary: Give tracked items stable codes, never renumbered; mark an ask that waits on the user. -->
|
|
5
5
|
<!-- LEAN:begin -->
|
|
6
6
|
Give every tracked item a short reference code and keep it unchanged for the rest of
|
|
7
7
|
the session — `D` decisions, `O` options, `F` findings, `R` risks, `Q` questions,
|
|
@@ -15,16 +15,35 @@ for a kind the list omits, and never renumber a code once issued — the user wi
|
|
|
15
15
|
it back, and a moved code makes their reply mean something you did not say. A code is an address, not an ornament:
|
|
16
16
|
it lets a long exchange be answered by reference, and a decision taken on turn
|
|
17
17
|
three still be named on turn thirty. Where the {{ONTOLOGY}}'s {{ONT_CONDUCT}}
|
|
18
|
-
governs how an answer speaks, this is only the addressing convention — a practice
|
|
18
|
+
governs how an answer speaks, this is only the addressing and marking convention — a practice
|
|
19
19
|
a repository adopts or drops like any other rule in these {{DOCTRINES}}.
|
|
20
|
+
|
|
21
|
+
When a reply stops and waits on the user — a question, a choice, an approval, a blocker —
|
|
22
|
+
make the ask stand apart from the work around it, so a reader who skims finds it first. Open
|
|
23
|
+
the ask with one emoji marker that names its kind: `❓` a question, `👉` an act the user must
|
|
24
|
+
do, `⚠️` a risk or a blocker, `✅` work done that waits on their sign-off. The marker comes
|
|
25
|
+
before the code: `❓ **Q3** — keep the v1 route?`. Lay out
|
|
26
|
+
the options and the flows with arrows — `→ yes: keep it · → no: remove it` — one option per
|
|
27
|
+
line past two, the recommended one first and named as such. Put one ask in each block; where
|
|
28
|
+
the answer to one question changes the next, ask them one at a time. Use colour only where
|
|
29
|
+
the surface renders it, such as markdown or a rich host; never write ANSI escapes or colour
|
|
30
|
+
markup into plain text that prints them raw. Routine output stays plain: a reply that waits
|
|
31
|
+
on nothing carries no marker, and a marker on every line marks nothing. The markers are
|
|
32
|
+
signs, not words, so the prose around them keeps {{DOCTRINE:simplified-technical-english}}.
|
|
33
|
+
Make the ask understood, not only seen. Before a command the user must run or approve, or a
|
|
34
|
+
question or a choice that is not clear by itself, write one or two plain lines: what it does,
|
|
35
|
+
why now, and what it changes or risks when that is not obvious. For a question, say what the
|
|
36
|
+
answer decides. An ask that is clear by itself stays bare: `ls`, or a yes/no question with no
|
|
37
|
+
stakes.
|
|
20
38
|
<!-- LEAN:else -->
|
|
21
|
-
Give every tracked item a
|
|
22
|
-
`
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
39
|
+
Give every tracked item a code that never changes in the session — `D` decisions, `O` options,
|
|
40
|
+
`F` findings, `R` risks, `Q` questions, `A` actions; invent letters for other kinds. A reply naming
|
|
41
|
+
two or more items codes them, reports included; the code opens the line:
|
|
42
|
+
`**F1** — token logged in plain text`. Count on across turns, never renumber. When a reply waits
|
|
43
|
+
on the user, open that ask with one marker before its code — `❓` question, `👉` act to do, `⚠️`
|
|
44
|
+
risk or blocker, `✅` done, waits on sign-off: `❓ **Q3** — keep the v1 route?`. One ask per block,
|
|
45
|
+
the recommended option first (`→`). An ask not clear alone gets one or two plain lines: what it
|
|
46
|
+
does, why now, what it risks or decides. Routine output stays plain; no raw ANSI.
|
|
28
47
|
<!-- LEAN:end -->
|
|
29
48
|
|
|
30
49
|
### {{DOCTRINE:structure-beside-prose}} Structure Beside Prose
|
|
@@ -95,34 +114,3 @@ most in an instruction, 25 in a description. Instructions: imperative, one actio
|
|
|
95
114
|
condition first. Active voice, no -ing forms, no dropped articles, one word per meaning
|
|
96
115
|
(`use`, not `utilize`). In another language, keep it and these rules.
|
|
97
116
|
<!-- LEAN:end -->
|
|
98
|
-
|
|
99
|
-
### {{DOCTRINE:mark-the-ask}} Mark the Ask
|
|
100
|
-
<!-- note: summary: Mark an ask that waits on the user, and explain it when it is not clear alone; routine output stays plain. -->
|
|
101
|
-
<!-- LEAN:begin -->
|
|
102
|
-
When a reply stops and waits on the user — a question, a choice, an approval, a blocker —
|
|
103
|
-
make the ask stand apart from the work around it, so a reader who skims finds it first. Open
|
|
104
|
-
the ask with one emoji marker that names its kind: `❓` a question, `👉` an act the user must
|
|
105
|
-
do, `⚠️` a risk or a blocker, `✅` work done that waits on their sign-off. The marker comes
|
|
106
|
-
before the code ({{DOCTRINE:codes-that-persist}}): `❓ **Q3** — keep the v1 route?`. Lay out
|
|
107
|
-
the options and the flows with arrows — `→ yes: keep it · → no: remove it` — one option per
|
|
108
|
-
line past two, the recommended one first and named as such. Put one ask in each block; where
|
|
109
|
-
the answer to one question changes the next, ask them one at a time. Use colour only where
|
|
110
|
-
the surface renders it, such as markdown or a rich host; never write ANSI escapes or colour
|
|
111
|
-
markup into plain text that prints them raw. Routine output stays plain: a reply that waits
|
|
112
|
-
on nothing carries no marker, and a marker on every line marks nothing. The markers are
|
|
113
|
-
signs, not words, so the prose around them keeps {{DOCTRINE:simplified-technical-english}}.
|
|
114
|
-
Make the ask understood, not only seen. Before a command the user must run or approve, or a
|
|
115
|
-
question or a choice that is not clear by itself, write one or two plain lines: what it does,
|
|
116
|
-
why now, and what it changes or risks when that is not obvious. For a question, say what the
|
|
117
|
-
answer decides. An ask that is clear by itself stays bare: `ls`, or a yes/no question with no
|
|
118
|
-
stakes.
|
|
119
|
-
<!-- LEAN:else -->
|
|
120
|
-
When a reply waits on the user — a question, a choice, an approval, a blocker — mark the
|
|
121
|
-
ask. Open it with one marker: `❓` question, `👉` act to do, `⚠️` risk or blocker, `✅` done,
|
|
122
|
-
waits on sign-off; it comes before the code: `❓ **Q3** — keep the v1 route?`. Arrows (`→`)
|
|
123
|
-
lay out options and flows, the recommended option first. One ask per block. Colour only
|
|
124
|
-
where the host renders it, never raw ANSI in plain text. Routine output stays plain; markers
|
|
125
|
-
are signs, not words. An ask that is not clear by itself carries one or two plain lines before
|
|
126
|
-
it: what it does, why now, what it changes or risks; for a question, what the answer decides.
|
|
127
|
-
A clear ask stays bare.
|
|
128
|
-
<!-- LEAN:end -->
|
package/src/doctrines/craft.md
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
**{{PACK_CRAFT}}** — how code is written.
|
|
2
2
|
|
|
3
3
|
### {{DOCTRINE:automate-repetition}} Automate Repetition
|
|
4
|
-
<!-- note: summary: If it repeats,
|
|
4
|
+
<!-- note: summary: If it repeats, automate it: script, skill or code, by the task. -->
|
|
5
5
|
<!-- LEAN:begin -->
|
|
6
6
|
When an action repeats, automate it — and choose the vessel by the nature of the task,
|
|
7
7
|
not by how many similar steps one session needs. Do not
|
|
@@ -14,18 +14,13 @@ perform by hand what the machine can perform a thousand times.
|
|
|
14
14
|
- a recurring, deterministic, exact operation (parsing, counting, API calls, anything
|
|
15
15
|
run unattended or where a model would err) → kept, versioned code.
|
|
16
16
|
Markdown is the default for what recurs; code is kept only where exactness or unattended
|
|
17
|
-
automation demands it.
|
|
18
|
-
domain — not a single command and not a grab-bag: seek an existing {{SKILL}} whose domain
|
|
19
|
-
already covers the need and extend it before forging a new one, and name {{SKILLS}} by
|
|
20
|
-
domain. Reuse before creating.
|
|
17
|
+
automation demands it.
|
|
21
18
|
<!-- LEAN:else -->
|
|
22
19
|
When an action repeats, automate it — choosing the vessel by the task, not the step
|
|
23
20
|
count: a one-off batch gets a throwaway {{SCRIPT}} outside the repository, never kept; a
|
|
24
21
|
recurring judgement procedure gets a markdown rule in the domain {{SKILL}} or {{AGENT}}
|
|
25
22
|
spec; a recurring exact or unattended operation gets kept, versioned code. Markdown is
|
|
26
|
-
the default for what recurs.
|
|
27
|
-
domain covers the need and extend it; build each {{SKILL}} for one coherent domain — not
|
|
28
|
-
a single command, not a grab-bag — and name {{SKILLS}} by domain. Reuse before creating.
|
|
23
|
+
the default for what recurs.
|
|
29
24
|
<!-- LEAN:end -->
|
|
30
25
|
|
|
31
26
|
### {{DOCTRINE:english-configuration}} English Configuration
|
|
@@ -58,11 +53,9 @@ drifts from the code is a defect, not a deferred task.
|
|
|
58
53
|
<!-- LEAN:begin -->
|
|
59
54
|
Before adding a file, module, function, or abstraction, confirm an equivalent
|
|
60
55
|
does not already exist; prefer extending what is there. Duplication is a defect.
|
|
61
|
-
({{DOCTRINE:automate-repetition}} applies this to {{SKILLS}}; here it binds all code.)
|
|
62
56
|
<!-- LEAN:else -->
|
|
63
57
|
Before adding a file, module, function, or abstraction, confirm an equivalent does not
|
|
64
58
|
already exist; prefer extending what is there. Duplication is a defect.
|
|
65
|
-
({{DOCTRINE:automate-repetition}} applies this to {{SKILLS}}; here it binds all code.)
|
|
66
59
|
<!-- LEAN:end -->
|
|
67
60
|
|
|
68
61
|
### {{DOCTRINE:respect-conventions}} Respect Conventions
|
package/src/doctrines/ops.md
CHANGED
|
@@ -54,9 +54,7 @@ applied, yet did not endure. Before altering any configuration, ask which layer
|
|
|
54
54
|
authoritative and write there alone. Persistence lives at the source, not the
|
|
55
55
|
surface.
|
|
56
56
|
<!-- LEAN:else -->
|
|
57
|
-
|
|
58
|
-
compose file regenerated from stored config — edit the source, never the rendered artifact.
|
|
59
|
-
Before altering any configuration, ask which layer is authoritative and write there alone.
|
|
57
|
+
Edit the authoritative layer, never the rendered artifact.
|
|
60
58
|
<!-- LEAN:end -->
|
|
61
59
|
|
|
62
60
|
### {{DOCTRINE:complete-the-teardown}} Complete the Teardown
|
|
@@ -85,9 +83,7 @@ citing it, this governs what to record in the first place: not the volatile valu
|
|
|
85
83
|
but the means to derive it — the probe, the query, the live computation. Record
|
|
86
84
|
how to check, and check at the hour of need.
|
|
87
85
|
<!-- LEAN:else -->
|
|
88
|
-
|
|
89
|
-
Record not the volatile value but the means to derive it — the probe, the query — and check
|
|
90
|
-
at the hour of need ({{LAW:verify-before-asserting}}).
|
|
86
|
+
Record how to derive a volatile fact, never its value.
|
|
91
87
|
<!-- LEAN:end -->
|
|
92
88
|
|
|
93
89
|
### {{DOCTRINE:restart-is-not-reload}} Restart Is Not Reload
|
|
@@ -103,10 +99,7 @@ recreate, down-and-up, reload, or full restart — perform it, then confirm the
|
|
|
103
99
|
value in the *running* system, not the file ({{LAW:verify-before-asserting}}). A correct file above a
|
|
104
100
|
stale process looks like a finished job and is not one.
|
|
105
101
|
<!-- LEAN:else -->
|
|
106
|
-
|
|
107
|
-
makes it be *read* — often not a restart. Establish which — recreate, down-and-up, reload,
|
|
108
|
-
full restart — perform it, then confirm the new value in the *running* system, not the file
|
|
109
|
-
({{LAW:verify-before-asserting}}).
|
|
102
|
+
After a config edit, confirm the new value in the running process, not the file.
|
|
110
103
|
<!-- LEAN:end -->
|
|
111
104
|
|
|
112
105
|
### {{DOCTRINE:serialize-against-a-rationed-resource}} Serialize Against a Rationed Resource
|
|
@@ -124,9 +117,5 @@ unchanged on retry is a hard limit, not transient backpressure: stop and report
|
|
|
124
117
|
batches independent calls, this names the calls that are not independent — they draw on
|
|
125
118
|
one allowance. A smaller complete sample beats a larger one gathered through failures.
|
|
126
119
|
<!-- LEAN:else -->
|
|
127
|
-
|
|
128
|
-
gateway — is called in sequence, never fanned out. Before any parallelism, divide the
|
|
129
|
-
quota by its callers; if one share cannot finish the work, do not parallelise. Back off on
|
|
130
|
-
each refusal, within a retry cap set first. A refusal repeating unchanged is a hard limit:
|
|
131
|
-
stop and report it ({{LAW:surface-failures}}), never re-send the batch.
|
|
120
|
+
Call a rationed resource in sequence; a repeated refusal is a hard limit — stop and report.
|
|
132
121
|
<!-- LEAN:end -->
|
package/src/doctrines/rigor.md
CHANGED
|
@@ -103,9 +103,5 @@ confused, or steered by untrusted input ({{LAW:data-not-orders}}). Where {{LAW:l
|
|
|
103
103
|
power you take, this governs the power you hand out; {{DOCTRINE:prove-the-gate}} proves the
|
|
104
104
|
gate once it stands.
|
|
105
105
|
<!-- LEAN:else -->
|
|
106
|
-
|
|
107
|
-
enforce the allowlist at the boundary the call must cross, and validate against real state.
|
|
108
|
-
Never let permission live in the governed agent's own prompt. Ship anything taking
|
|
109
|
-
autonomous control of physical state, money, or production disarmed, armed only by explicit
|
|
110
|
-
human act ({{LAW:data-not-orders}}).
|
|
106
|
+
Permission lives at a boundary the agent cannot satisfy alone; autonomous control ships disarmed.
|
|
111
107
|
<!-- LEAN:end -->
|
|
@@ -0,0 +1,52 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "analysis-to-build",
|
|
3
|
+
"description": "Turn an analysis (a document, pasted text or a request) into a spec whose task list you approve, build each task in turn with the feature loop in one worktree, run the base branch's checks and a review panel, play the holdout scenarios it never saw, then open one pull request and wait for green CI; a failed check, review or scenario, or red CI, sends the work back to the loop as one more task, twice at most each. At the end it asks you once whether to merge.",
|
|
4
|
+
"category": "development",
|
|
5
|
+
"rules": [
|
|
6
|
+
"Never merge or enable auto-merge without the user's yes, asked once at the end of the run.",
|
|
7
|
+
"Push only this worktree's own branch."
|
|
8
|
+
],
|
|
9
|
+
"stages": ["intake", "spec", "holdout-write", "loop:feature", "checks", "review-panel", "holdout", "pr-open", "merge-gate", "retro"],
|
|
10
|
+
"start": "intake",
|
|
11
|
+
"edges": [
|
|
12
|
+
{ "from": "intake", "on": "pass", "to": "spec" },
|
|
13
|
+
{ "from": "intake", "on": "fail", "to": "$stop" },
|
|
14
|
+
{ "from": "intake", "on": "needs-info", "to": "spec" },
|
|
15
|
+
{ "from": "spec", "on": "pass", "to": "holdout-write" },
|
|
16
|
+
{ "from": "spec", "on": "fail", "to": "$stop" },
|
|
17
|
+
{ "from": "holdout-write", "on": "pass", "to": "loop:feature" },
|
|
18
|
+
{ "from": "holdout-write", "on": "fail", "to": "$stop" },
|
|
19
|
+
{ "from": "loop:feature", "on": "pass", "to": "checks" },
|
|
20
|
+
{ "from": "loop:feature", "on": "fail", "to": "$stop" },
|
|
21
|
+
{ "from": "checks", "on": "pass", "to": "review-panel" },
|
|
22
|
+
{ "from": "checks", "on": "fail", "to": "loop:feature" },
|
|
23
|
+
{ "from": "checks", "on": "error", "to": "review-panel" },
|
|
24
|
+
{ "from": "checks", "on": "none", "to": "checks" },
|
|
25
|
+
{ "from": "review-panel", "on": "pass", "to": "holdout" },
|
|
26
|
+
{ "from": "review-panel", "on": "fail", "to": "loop:feature" },
|
|
27
|
+
{ "from": "holdout", "on": "pass", "to": "pr-open" },
|
|
28
|
+
{ "from": "holdout", "on": "fail", "to": "loop:feature" },
|
|
29
|
+
{ "from": "holdout", "on": "error", "to": "$stop" },
|
|
30
|
+
{ "from": "pr-open", "on": "pass", "to": "merge-gate" },
|
|
31
|
+
{ "from": "pr-open", "on": "fail", "to": "$stop" },
|
|
32
|
+
{ "from": "merge-gate", "on": "pass", "to": "retro" },
|
|
33
|
+
{ "from": "merge-gate", "on": "fail", "to": "loop:feature" },
|
|
34
|
+
{ "from": "merge-gate", "on": "none", "to": "retro" },
|
|
35
|
+
{ "from": "retro", "on": "pass", "to": "$close" }
|
|
36
|
+
],
|
|
37
|
+
"cycles": [
|
|
38
|
+
{ "name": "done-list", "nodes": ["checks"], "max": 1 },
|
|
39
|
+
{ "name": "checks", "nodes": ["loop:feature", "checks"], "max": 2 },
|
|
40
|
+
{ "name": "review", "nodes": ["loop:feature", "checks", "review-panel"], "max": 2 },
|
|
41
|
+
{ "name": "holdout", "nodes": ["loop:feature", "checks", "review-panel", "holdout"], "max": 2 },
|
|
42
|
+
{ "name": "ci", "nodes": ["loop:feature", "checks", "review-panel", "holdout", "pr-open", "merge-gate"], "max": 2 }
|
|
43
|
+
],
|
|
44
|
+
"review": {
|
|
45
|
+
"seats": {
|
|
46
|
+
"small": ["reviewer"],
|
|
47
|
+
"medium": ["reviewer", "tester"],
|
|
48
|
+
"large": ["reviewer", "tester", "steward"],
|
|
49
|
+
"areas": { "security": ["security"], "performance": ["performance"], "ui": ["user-advocate"], "data": ["security"] }
|
|
50
|
+
}
|
|
51
|
+
}
|
|
52
|
+
}
|
|
@@ -0,0 +1,50 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "bug-report-to-fix",
|
|
3
|
+
"description": "Take one bug report, fix it with the bugfix loop, run the base branch's checks and a review panel, play the holdout scenarios it never saw, open the pull request and wait for green CI; a failed check, review or scenario, or red CI, sends the fix back to the loop, twice at most each. At the end it asks you once whether to merge.",
|
|
4
|
+
"category": "development",
|
|
5
|
+
"rules": [
|
|
6
|
+
"Never merge or enable auto-merge without the user's yes, asked once at the end of the run.",
|
|
7
|
+
"Push only this worktree's own branch."
|
|
8
|
+
],
|
|
9
|
+
"stages": ["intake", "holdout-write", "loop:bugfix", "checks", "review-panel", "holdout", "pr-open", "merge-gate", "retro"],
|
|
10
|
+
"start": "intake",
|
|
11
|
+
"edges": [
|
|
12
|
+
{ "from": "intake", "on": "pass", "to": "holdout-write" },
|
|
13
|
+
{ "from": "intake", "on": "fail", "to": "$stop" },
|
|
14
|
+
{ "from": "intake", "on": "needs-info", "to": "holdout-write" },
|
|
15
|
+
{ "from": "holdout-write", "on": "pass", "to": "loop:bugfix" },
|
|
16
|
+
{ "from": "holdout-write", "on": "fail", "to": "$stop" },
|
|
17
|
+
{ "from": "loop:bugfix", "on": "pass", "to": "checks" },
|
|
18
|
+
{ "from": "loop:bugfix", "on": "fail", "to": "$stop" },
|
|
19
|
+
{ "from": "checks", "on": "pass", "to": "review-panel" },
|
|
20
|
+
{ "from": "checks", "on": "fail", "to": "loop:bugfix" },
|
|
21
|
+
{ "from": "checks", "on": "error", "to": "review-panel" },
|
|
22
|
+
{ "from": "checks", "on": "none", "to": "checks" },
|
|
23
|
+
{ "from": "review-panel", "on": "pass", "to": "holdout" },
|
|
24
|
+
{ "from": "review-panel", "on": "fail", "to": "loop:bugfix" },
|
|
25
|
+
{ "from": "holdout", "on": "pass", "to": "pr-open" },
|
|
26
|
+
{ "from": "holdout", "on": "fail", "to": "loop:bugfix" },
|
|
27
|
+
{ "from": "holdout", "on": "error", "to": "$stop" },
|
|
28
|
+
{ "from": "pr-open", "on": "pass", "to": "merge-gate" },
|
|
29
|
+
{ "from": "pr-open", "on": "fail", "to": "$stop" },
|
|
30
|
+
{ "from": "merge-gate", "on": "pass", "to": "retro" },
|
|
31
|
+
{ "from": "merge-gate", "on": "fail", "to": "loop:bugfix" },
|
|
32
|
+
{ "from": "merge-gate", "on": "none", "to": "retro" },
|
|
33
|
+
{ "from": "retro", "on": "pass", "to": "$close" }
|
|
34
|
+
],
|
|
35
|
+
"cycles": [
|
|
36
|
+
{ "name": "done-list", "nodes": ["checks"], "max": 1 },
|
|
37
|
+
{ "name": "checks", "nodes": ["loop:bugfix", "checks"], "max": 2 },
|
|
38
|
+
{ "name": "review", "nodes": ["loop:bugfix", "checks", "review-panel"], "max": 2 },
|
|
39
|
+
{ "name": "holdout", "nodes": ["loop:bugfix", "checks", "review-panel", "holdout"], "max": 2 },
|
|
40
|
+
{ "name": "ci", "nodes": ["loop:bugfix", "checks", "review-panel", "holdout", "pr-open", "merge-gate"], "max": 2 }
|
|
41
|
+
],
|
|
42
|
+
"review": {
|
|
43
|
+
"seats": {
|
|
44
|
+
"small": ["reviewer"],
|
|
45
|
+
"medium": ["reviewer", "tester"],
|
|
46
|
+
"large": ["reviewer", "tester", "steward"],
|
|
47
|
+
"areas": { "security": ["security"], "performance": ["performance"], "ui": ["user-advocate"], "data": ["security"] }
|
|
48
|
+
}
|
|
49
|
+
}
|
|
50
|
+
}
|
|
@@ -0,0 +1,67 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "issue-to-pr",
|
|
3
|
+
"description": "Take one issue, let triage pick the lane that fits (the bugfix, feature, deps-upgrade or refactor loop, or a docs-only update), run the base branch's checks and a review panel, play the holdout scenarios it never saw, open the pull request and wait for green CI; a failed check, review or scenario, or red CI, sends the work back to that lane, twice at most each. At the end it asks you once whether to merge.",
|
|
4
|
+
"category": "development",
|
|
5
|
+
"rules": [
|
|
6
|
+
"Never merge or enable auto-merge without the user's yes, asked once at the end of the run.",
|
|
7
|
+
"Push only this worktree's own branch."
|
|
8
|
+
],
|
|
9
|
+
"stages": [
|
|
10
|
+
"intake", "holdout-write", "triage",
|
|
11
|
+
"loop:bugfix", "loop:feature", "loop:deps-upgrade", "loop:refactor", "docs-update",
|
|
12
|
+
"checks", "review-panel", "holdout", "pr-open", "merge-gate", "retro"
|
|
13
|
+
],
|
|
14
|
+
"start": "intake",
|
|
15
|
+
"edges": [
|
|
16
|
+
{ "from": "intake", "on": "pass", "to": "holdout-write" },
|
|
17
|
+
{ "from": "intake", "on": "fail", "to": "$stop" },
|
|
18
|
+
{ "from": "intake", "on": "needs-info", "to": "holdout-write" },
|
|
19
|
+
{ "from": "holdout-write", "on": "pass", "to": "triage" },
|
|
20
|
+
{ "from": "holdout-write", "on": "fail", "to": "$stop" },
|
|
21
|
+
{ "from": "triage", "on": "bug", "to": "loop:bugfix" },
|
|
22
|
+
{ "from": "triage", "on": "feature", "to": "loop:feature" },
|
|
23
|
+
{ "from": "triage", "on": "deps", "to": "loop:deps-upgrade" },
|
|
24
|
+
{ "from": "triage", "on": "refactor", "to": "loop:refactor" },
|
|
25
|
+
{ "from": "triage", "on": "docs", "to": "docs-update" },
|
|
26
|
+
{ "from": "triage", "on": "fail", "to": "$stop" },
|
|
27
|
+
{ "from": "loop:bugfix", "on": "pass", "to": "checks" },
|
|
28
|
+
{ "from": "loop:bugfix", "on": "fail", "to": "$stop" },
|
|
29
|
+
{ "from": "loop:feature", "on": "pass", "to": "checks" },
|
|
30
|
+
{ "from": "loop:feature", "on": "fail", "to": "$stop" },
|
|
31
|
+
{ "from": "loop:deps-upgrade", "on": "pass", "to": "checks" },
|
|
32
|
+
{ "from": "loop:deps-upgrade", "on": "fail", "to": "$stop" },
|
|
33
|
+
{ "from": "loop:refactor", "on": "pass", "to": "checks" },
|
|
34
|
+
{ "from": "loop:refactor", "on": "fail", "to": "$stop" },
|
|
35
|
+
{ "from": "docs-update", "on": "pass", "to": "checks" },
|
|
36
|
+
{ "from": "checks", "on": "pass", "to": "review-panel" },
|
|
37
|
+
{ "from": "checks", "on": "fail", "to": "$lane" },
|
|
38
|
+
{ "from": "checks", "on": "error", "to": "review-panel" },
|
|
39
|
+
{ "from": "checks", "on": "none", "to": "checks" },
|
|
40
|
+
{ "from": "review-panel", "on": "pass", "to": "holdout" },
|
|
41
|
+
{ "from": "review-panel", "on": "fail", "to": "$lane" },
|
|
42
|
+
{ "from": "holdout", "on": "pass", "to": "pr-open" },
|
|
43
|
+
{ "from": "holdout", "on": "fail", "to": "$lane" },
|
|
44
|
+
{ "from": "holdout", "on": "error", "to": "$stop" },
|
|
45
|
+
{ "from": "pr-open", "on": "pass", "to": "merge-gate" },
|
|
46
|
+
{ "from": "pr-open", "on": "fail", "to": "$stop" },
|
|
47
|
+
{ "from": "merge-gate", "on": "pass", "to": "retro" },
|
|
48
|
+
{ "from": "merge-gate", "on": "fail", "to": "$lane" },
|
|
49
|
+
{ "from": "merge-gate", "on": "none", "to": "retro" },
|
|
50
|
+
{ "from": "retro", "on": "pass", "to": "$close" }
|
|
51
|
+
],
|
|
52
|
+
"cycles": [
|
|
53
|
+
{ "name": "done-list", "nodes": ["checks"], "max": 1 },
|
|
54
|
+
{ "name": "checks", "nodes": ["$lane", "checks"], "max": 2 },
|
|
55
|
+
{ "name": "review", "nodes": ["$lane", "checks", "review-panel"], "max": 2 },
|
|
56
|
+
{ "name": "holdout", "nodes": ["$lane", "checks", "review-panel", "holdout"], "max": 2 },
|
|
57
|
+
{ "name": "ci", "nodes": ["$lane", "checks", "review-panel", "holdout", "pr-open", "merge-gate"], "max": 2 }
|
|
58
|
+
],
|
|
59
|
+
"review": {
|
|
60
|
+
"seats": {
|
|
61
|
+
"small": ["reviewer"],
|
|
62
|
+
"medium": ["reviewer", "tester"],
|
|
63
|
+
"large": ["reviewer", "tester", "steward"],
|
|
64
|
+
"areas": { "security": ["security"], "performance": ["performance"], "ui": ["user-advocate"], "data": ["security"] }
|
|
65
|
+
}
|
|
66
|
+
}
|
|
67
|
+
}
|
package/src/skills/adhd.md
CHANGED
|
@@ -13,7 +13,7 @@
|
|
|
13
13
|
**Precedence.** This mode shapes *presentation* only. The harness file itself — the {{LAWS}}, `user-rules.md`, the active doctrines (the comms ones above all) — outranks it; where they collide, the rule wins and the shape stays. The known collisions resolve so:
|
|
14
14
|
- **Readiness sigil.** On a session's first reply the sigil stays the first line; the next action leads right after it.
|
|
15
15
|
- **Cap at five** (step 9) groups and orders what is shown — it never renumbers, merges or drops a {{DOCTRINE:codes-that-persist}} code; an item gets its code when it is first shown, and a code once shown is never dropped.
|
|
16
|
-
- **The closing next action** (step 3) takes the {{DOCTRINE:
|
|
16
|
+
- **The closing next action** (step 3) takes the {{DOCTRINE:codes-that-persist}} form — `👉` for an act to do, `❓` for a question, one ask per block.
|
|
17
17
|
- **No recap** (step 10) never deletes the verification command and its output owed by {{LAW:verify-before-asserting}}, nor the judgment calls owed by {{DOCTRINE:declare-the-judgment-calls}} — those are evidence, not recap.
|
|
18
18
|
- **Harness duties** outrank brevity: announce a tool call when the host requires it, do the work rather than asking "want me to?", and point time estimates at whoever runs the steps.
|
|
19
19
|
|