Skip to content
Komputa Practice
Esc
↑↓navigate↵open⌘Jpreview
On this page

Changes

Every pull request merged into the practice, under the version it shipped in.

This page is generated. Do not edit it: change the source it names, and the next build changes this page. The source is the git history of main and its version tags.

Not released yet

  • 2026-11-12 · #141 handover gives the fresh session only the newest handoff
  • 2026-11-12 · #140 The docs say how to find the lead after a night of handovers
  • 2026-11-12 · #139 The lead keeps a lead label that each handover moves
  • 2026-11-12 · #138 The scorecard reads squash merges and names the practice version
  • 2026-11-12 · #137 Tooling the product does not ship lives in tools/
  • 2026-11-12 · #136 Replace the evidence page with a Changes page built from git

v1.2.0 (2026-11-12)

  • 2026-11-12 · #134 The template writes a gate workflow for a GitHub repo
  • 2026-11-12 · #133 The life of a program follows the one-session default
  • 2026-11-12 · #131 The docs deploy switch is DOCS_DEPLOY; the site is public
  • 2026-11-12 · #132 The watcher tests fix the clock, so a slow runner cannot fail them
  • 2026-11-12 · #130 The docs name the real repos under komputa-io
  • 2026-11-11 · #129 Move the documentation plan to docs/research as a record
  • 2026-11-11 · #127 Slim the README to a front door; the repo layout moves to the site
  • 2026-11-11 · #126 Retire the Docmost mirror; team-only docs move to their own space
  • 2026-11-11 · #125 Deploy the docs site to Cloudflare at docs.komputa.io, behind a guard
  • 2026-11-11 · #122 Add the Deployment and Contribute guides, the FAQ, and two imports
  • 2026-11-11 · #121 Generate the skills and template-question pages; add Configuration
  • 2026-11-11 · #120 Add guides for overnight runs and for turning a finding into a rule
  • 2026-11-11 · #119 Add the Guides tab with three guides
  • 2026-11-11 · #118 Add the Introduction, a how-it-fits diagram and dark diagrams
  • 2026-11-11 · #114 Add the Get started tab and the Quickstart
  • 2026-11-11 · #113 Docs site takes the Komputa brand and the name Komputa Practice
  • 2026-11-11 · #112 Add the plan for rebuilding the documentation
  • 2026-11-11 · #111 The watcher hands a session over to a fresh one when its context passes 250k
  • 2026-11-11 · #110 check.sh checks that each skill a skill names is installed
  • 2026-11-11 · #109 One watcher keeps a long session going while nobody watches it
  • 2026-11-11 · #108 Worker hooks: ask hc whether the session is a worker
  • 2026-11-11 · #107 Docs pass: say where things live after the consolidation
  • 2026-11-11 · #106 Step 10: mirror docs/ to the wiki

v1.1.0 (2026-11-11)

  • 2026-11-11 · #105 Step 8: the template asks which forge; one script per forge

v1.0.0 (2026-11-11)

  • 2026-11-11 · #104 The project template moves here, with its history
  • 2026-11-11 · #103 How it fits: the three places the practice lives, and how a rule changes
  • 2026-11-11 · #102 Bring in the secret and credential hooks, and check the live copies
  • 2026-11-11 · #101 Bring in the house skills and standards-feedback
  • 2026-11-11 · #100 Rename to komputa-practice
  • 2026-11-11 · #99 herdr skill: say what is true since the reset
  • 2026-11-10 · #98 Evidence: the product’s test prune, one row for each slice
  • 2026-11-10 · #97 Rules: what success is, lead-only rules in their own file, and the measures on the scorecard
  • 2026-11-10 · #96 Evidence page: a first one-session reading, with its limits
  • 2026-11-10 · #95 Rules: the one test of a fix is outside the line budget
  • 2026-11-10 · #94 Hook test: limit the long command by CPU time, not wall time
  • 2026-11-10 · #93 Site and model-selection page say what the practice is today
  • 2026-11-10 · #92 README: one session first; evidence page maps each rule to practice outside
  • 2026-11-10 · #91 Framework evidence: what the practice caught and cost, and how the next period is measured
  • 2026-11-10 · #89 Archive the herdr scripts; tier 3 is tier 2 plus one review
  • 2026-11-10 · #87 Tests follow risk: one budget replaces the test plan form, the method cap and the regression check
  • 2026-11-10 · #85 check-tools-only and the stall rule for a tools-only PR (#84, step 1)
  • 2026-11-10 · #83 wait-event ends when a worker finishes idle (#82)
  • 2026-11-10 · #81 Test plan from intent, method cap, regression-test check, test-weakening hook (#77)
  • 2026-11-10 · #80 stall-watch is started, sees a stale head and a red main, and one global watcher covers every lead (#78)
  • 2026-11-09 · #79 Working rules: the stall-watch row says what is true until #78 merges
  • 2026-11-09 · #76 A brief carries a test plan by layer and a suite budget (#75)
  • 2026-11-09 · #72 Docs site for the practice, built with Blume (#39)
  • 2026-11-09 · #74 safe-send: an empty input box is blank, not held (#73)
  • 2026-11-09 · #71 safe-send: a worker’s report waits while a person has a half-typed message (#11)
  • 2026-11-09 · #70 Keep a worker’s browser off the operator’s screen (#69)
  • 2026-11-09 · #68 block-destructive-delete: judge long target lists fast, refuse past 5000 (#21)
  • 2026-11-09 · #67 stall-watch: an idle old lead tells its child lead to run retire-lead (#32)
  • 2026-11-09 · #66 budget-watch, stall-watch: watch the lead’s workers, not a fresh lead (#30)
  • 2026-11-09 · #65 lead-workers: a worker that outlives its lead is still a worker (#64)
  • 2026-11-09 · #63 finish-worker: match the worker’s own report, no guess from the brief (#62)
  • 2026-11-09 · #61 verify-yes: check that a relayed yes was the operator’s own message
  • 2026-11-09 · #60 start-worker starts the lead’s stack-watch; it ends with its lead (#59)
  • 2026-11-09 · #58 finish-worker, stall-watch: match the worker’s own report (#57)
  • 2026-11-09 · #56 wait-event: one wait for each lead, and –workers-only (#54)
  • 2026-11-09 · #55 finish-worker: close a finished worker’s pane (#53)
  • 2026-11-09 · #52 start-lead: the resume prompt does not repeat the first task (#51)
  • 2026-11-09 · #50 start-lead: a lead for another repo starts with no parent
  • 2026-11-09 · #48 resume-check: a waits-on-operator stop writes no stopped
  • 2026-11-09 · #47 Rules: the waits-on-operator rule for leads
  • 2026-11-09 · #45 Resume on by default (auto-resume PR 3)
  • 2026-11-09 · #44 Add resume-check: the decision core for auto-resume
  • 2026-11-09 · #43 start-worker: add a verifier role
  • 2026-11-09 · #42 resume-program: stop after 3 starts with no heartbeat
  • 2026-11-09 · #38 start-worker: one home for a worker’s model
  • 2026-11-09 · #37 Start every lead in its repo’s space with start-lead
  • 2026-11-09 · #36 Never label a terminal herdr.space=null (pane-labels)
  • 2026-11-09 · #33 Give a squeezed pane a tab of its own (give-room)
  • 2026-11-08 · #29 Keep a fresh lead’s pane through a hand-over (#28)
  • 2026-11-08 · #27 Add stall-watch
  • 2026-11-08 · #26 wait-event: –deadline, hourly notice, –check-now
  • 2026-11-06 · #23 Size a brief at about two deliverables, and say how to judge that
  • 2026-11-06 · #22 Make agent support a criterion when choosing a stack
  • 2026-11-06 · #19 Close the hook bypasses in issue 17
  • 2026-11-06 · #13 Run every check in one command and in CI
  • 2026-11-06 · #12 Add the quality funnel: picture and rule
  • 2026-11-03 · #8 rules: an operator’s question is not scope
  • 2026-11-03 · #7 Size the process to the work: three tiers by risk
  • 2026-11-03 · #6 herdr: retire-lead, and the handover rule for a fresh lead
  • 2026-11-03 · #5 Context budget: brief size, a lead cap, and wait-event
  • 2026-11-03 · #4 herdr: text in a worker’s input box is not the operator’s answer
  • 2026-11-02 · #3 Add a delete gate for actions that cannot be undone
  • 2026-11-02 · #2 Move the diagram rule to John’s personal rules
  • 2026-11-02 · #1 Draw every diagram with the diagram-design skill

Was this page helpful?