Start · chosen once, from the situation a request begins in

router

about 2,300 tokens

router as it installs, every line written by greenline, with no upstream source.

Written by greenline100%

3 files
0 edits
0 sentences left out
0 sources
last changed 2026-10-21

Replaces project-router (retired 2026-10-08).

The text

SKILL.md

about 980 tokens

greenline

---

name: "router"

description: "Find where a request stands on the line when the next step is unclear: resume an open or stopped change at the step its \"next\" line names, choose the start the request's situation calls for, or send a new change to its proposal. Use for continuity (\"what were we doing?\"), for a request no start fits, and for doubt about the next step."

---

greenlineOpens the router: it finds where a request stands on the line

# Router

AGENTS.md owns the request loop, the modes and the roster by kind. This start finds where a request stands: an open or stopped change to resume, a start to choose, or a new change to propose. The ledger guide owns the change record's format.

greenlinePoints at the skill's references page for paths and commands

Greenline's paths and commands for this skill stand on its references page, [references/greenline.md](references/greenline.md): read it when the work lands in the workspace.

greenlineResumes a change on its branch at its next line, set open

## Resume a change

Read the open and stopped change records in the ledger, the exact references in the request and the relevant files; the workspace's status lists each change with its state and its "next" line. A change stopped on another branch, local or remote-tracking, is found by its record's commit, which every stop makes, and read from that branch. Read the candidates before deciding which change the owner means: recency alone is not ownership. A record's "next" line names the step reached and the action that resumes it. Resume there on the change's branch, the one its record's commit sits on, switching to it first when the session sits on another, and making a local branch from a remote-tracking one; go on under the record's mode, with no new proposal, and set the record's state `open` as your first write in it. Ask only when several changes remain plausible, and say what each would produce.

greenlineStops an unrelated change, then loads only the start its row names

## Choose the start

When this session holds a change and the request asks for another change, stop that change first, as the ledger guide says. A session that resumes, or is asked "what were we doing?", with no open or stopped change on any branch says there is nothing to resume, proposes nothing and asks the owner for the request. When no open or stopped change is the request's, load the one start whose row in AGENTS.md names the situation the request begins in, or at an orientation the start AGENTS.md names for it, and no other; a start the owner names runs. `architecture-survey` loads at an orientation, a repository with documents and no change record on any branch, local or remote-tracking, or when the request asks for a survey or the owner names it; where a change record exists, it is never an orientation. A start that did not run is never named in the record. A request that asks for a change and fits no start goes straight to its proposal: the mode, then the line from `frame`. A step asked for by name runs alone. ROUTING.md, the map of the line, separates two methods that could produce different work.

greenlineLoads a habit only on its row's situation; unasked files wait

## Watch the habits

While any step runs, watch for the situations the habits' rows in AGENTS.md name. Load a habit only when the situation its row in AGENTS.md names arises in the work at hand, never ahead of it or beside another habit in case it might. `secrets` loads only where a secret is in reach: a key, a token, a credential or a `.env` file that the work reads, writes, stages in a commit or builds into an image, or a credential that may have leaked; a commit or an image with none in reach loads nothing. `ponytail` loads only in its own rows: before writing code the request leaves open, a refactor or a simplification of code that works, a new internal API replacing an old one that still has callers, or a question about what was deferred; writing code the request plainly asks for is none of them. A habit whose output is a durable file the owner did not ask for is offered in one line and made on the owner's yes.

greenlineWrites only a record's state; next a step, start, frame or question

## Handoff

Consumes: the request and the open or stopped change records under .greenline/ledger/ Produces: the record's state in .greenline/ledger/<id>.md, open for the change resumed and stopped, with its "next" line and committed, for the change set aside; otherwise nothing durable: the start loaded, the proposal made, or, with nothing to resume, the owner asked for the request, in the reply Next: the step the resumed change's "next" line names, the start the situation calls for, or frame under the mode the owner approves

SKILL.md as installed, byte for byte SHA-256 7ce11f0c5c5d48f0538a1be0d6920be2dc30f6676dbf8279099fcf382b23172e

ROUTING.md

about 1,100 tokens

greenline

greenlineOpens the map: read it when two methods could produce different work

# The map of the line

Read this when two methods could produce different work. It describes the corpus's methods, not a promise that all are installed: the roster in AGENTS.md lists what is installed, and an absent skill is unavailable even when named here. The request's authority carries through the line; ask about an unresolved product decision or a scope boundary, never for permission to read a skill.

greenlineLists the steps in order and what each writes in the record

## The steps

A change's mode runs the steps in this order, each at the depth the mode table in AGENTS.md gives it, and you never choose among them. Each step's skill writes its section of the change record when the step ends.

| Step | Its section of the record holds |

| --- | --- |

| `frame` | the intent restated, what is out of scope, the settled terms and the open questions |

| `plan` | acceptance that can fail and the work in ordered tasks; when the work splits, the plan directory's spec and its tickets file, a mode beside each ticket |

| `anticipate` | the claims the build rests on, attacked before the build; it is careful's premise review |

| `build` | what was built, the deviations from the plan and the approaches dropped; the commits carry the change's trailer and the checks are recorded |

| `review` | each reviewer's findings and what was done with each |

| `verify` | each acceptance item verified, not verified or inconclusive, with its evidence |

| `close` | the decisions and terms the change settled, the state, the "next" line and the cost |

A step asked for by name runs alone: "grill me" is `frame`, a spec or tickets is `plan`, a stress test of a plan is `anticipate`, "review this branch" is `review`, "verify this" is `verify`, and a decision or a term to write down is `close`. It needs no mode and no record while it changes no file. Once it edits a file, a write into the knowledge homes (the decisions book, the ADR home and the glossary) included, it opens a change and its proposal like any other edit, and `close` opens a quick record first.

greenlineResumes on its branch; a ticket shares the planning change's branch

## Resuming

An open or stopped change resumes at the step its "next" line names, on the branch its record's commit sits on, under the record's mode, and the session that resumes it sets it `open`. Its earlier sections record what was done, and the builder's sections are the builder's claims, not evidence. A ticket of a plan directory opens its own change record under the mode beside it in the tickets file, on the planning change's branch, and the record omits the steps its plan's record holds.

greenlineSeparates look-alike situations: which start or step each needs, and why

## Two methods that look alike

| The situation | Choose | Not |

| --- | --- | --- |

| Observed behavior is wrong and its cause is unknown | `diagnose`, a start: a reproducer and the cause, then the repair as a change | `verify`, which proves a claimed outcome |

| A design question inside one change | `frame`, at its depth | `wayfinder`, a start that maps a decision space spanning sessions |

| Which product idea to build next | `what-to-build`, a start that proposes in the reply | `frame`, which shapes a request already chosen |

| The structure of the code as a whole | `architecture-survey`, a start that surveys and reports | `review`, which judges one change's commits |

| A brittle or slow test suite | `sweep-tests`, a start with its mutation proof | `review`'s excess lens, which reads one change |

| The repository lacks its baseline | `groundwork`, a start that sets up only what the purpose needs | `build`, which works inside a baseline |

| An idea the owner brings is still vague | `idea-refine` (trial), a start that varies it, stress-tests it and states its assumptions before any change | `what-to-build`, which proposes ideas from the repository's own evidence |

| The repository's quality bar is unwritten, or a check was loosened to reach green | `constraint-driven-development` (trial), a start that writes the bar down and guards it | `groundwork`, which sets up the baseline a bar measures |

Use evidence available locally before asking the owner a factual question. When two plausible tasks remain, explain the difference in the intended result. Routine implementation choices stay with the agent inside the settled scope.

greenlinegreenline tidy removes working files; relied-on evidence stays cited

## The records

Working files are removed when the change is done, never a cited file. What a claim relies on goes into the change's folder, and the record cites it. A repository's existing home for a kind of memory is that home: lasting choices go to its decision home and settled terms to its glossary, or `GLOSSARY.md` when it has none.

references/greenline.md

about 180 tokens

greenline

greenlineOpens the skill's mechanics page, read with SKILL.md

# Router: the practice's mechanics

This page holds where router's work lands in the workspace and the commands it runs, which `SKILL.md` names by their nouns. Read it with `SKILL.md` when the work lands in the workspace.

greenlineThe ledger, the status listing and the working files

## Where its work lands

The ledger is `.greenline/ledger/`, its guide `.greenline/ledger/README.md`, which owns the change record's format and the stop; each change's record is `.greenline/ledger/<id>.md` and its folder `.greenline/ledger/<id>/`. `greenline status` lists each change with its state and its "next" line. A change's checks run through `greenline check`. Working files live under `.greenline/tmp/<id>/`, and `greenline tidy` removes them when the change is done, never a cited file.

What greenline wrote

The full reason for every passage greenline wrote, in the order of the text.

SKILL.md:6 method
The title and opening: the router is the start that finds where a request stands on the line, inside the loop and the modes AGENTS.md owns. Since J-93 S2 the front names greenline's homes and commands by their nouns, their paths and commands on the skill's references page. R1
SKILL.md:13 pointer
The front points at the skill's references page, where greenline's paths and commands for it stand since J-93 S2, so the front holds the method alone.
SKILL.md:15 method
Resume a change: read the open and stopped change records, one stopped on another branch, local or remote-tracking, found by its record's commit and read from that branch, resume at the step the record's next line names, on the change's branch, a local one made from a remote-tracking branch, under its mode, and set the record open as the first write. Since J-93 S2 the front names greenline's homes and commands by their nouns, their paths and commands on the skill's references page. R2
SKILL.md:31 method
Choose the start: stop the change this session holds when the request asks for another change, answer that nothing is to resume when no change is open or stopped, then match the request's situation against the starts, or send a new change to its proposal and the line from frame. With nothing to resume the session says so and asks for the request; a start loads only in its row's situation or by the owner's name, architecture-survey never as an orientation where a record exists, since QA runs loaded it so (J-60, the fourth family). Since J-93 S2 the front names greenline's homes and commands by their nouns, their paths and commands on the skill's references page. R3
SKILL.md:49 method
Watch the habits: load a habit only when its row's situation arises in the work, secrets only with a secret in reach and ponytail only in its own rows, since QA runs loaded both ahead of their situations (J-60, the fourth family); a durable file nobody asked for is offered first. R4
SKILL.md:65 method
The handoff a start carries: the record's state when a change resumes or is set aside, otherwise nothing durable, and the step reached, the start chosen or frame under the approved mode next. With nothing to resume, the reply asks the owner for the request. R5
ROUTING.md:1 method
The map's opening: read it when two methods could produce different work; it names corpus methods, and the roster says what is installed. R6
ROUTING.md:10 method
The steps in the line's order with what each step's section of the change record holds, the steps asked for by name, and the close asked for by name, which opens a quick record first even for a write only into the knowledge homes (J-102 S2). Since J-93 S2 the front names greenline's homes and commands by their nouns, their paths and commands on the skill's references page. R7
ROUTING.md:36 method
Resuming: a change resumes on its branch at the step its next line names, and a ticket opens its own record under its mode on the planning change's branch. R8
ROUTING.md:46 method
Two methods that look alike: the start or step each neighbouring situation calls for, and why not the other. The renamed starts take their names, diagnose and architecture-survey (R22), and the two trial starts that look like a kept start gain a row each, as the ingest procedure's wiring rule asks (S17's amendment of 2026-10-08). R9
ROUTING.md:64 method
The records: greenline tidy removes the working files when the change is done and never a cited one, what a claim relies on goes into the change's folder, memory into the repository's own homes. Since J-93 S2 the front names greenline's homes and commands by their nouns, their paths and commands on the skill's references page. R10
references/greenline.md:1 scope
The skill's references page opens: greenline's mechanics for the skill, the paths and commands its front names by their nouns, held apart from the upstream prose since J-93 S2.
references/greenline.md:5 relocate
router's mechanics: the ledger and its guide, the status listing, the record's path, the recorder, the working files and tidy, and the change's folder, held apart since J-93 S2.

The ledger entry

greenline's ledger logs how each skill was made and changed, with a reason for each entry.

2026-10-21 2026-10-21-router-a-record-for-every-write

A close by name opens a quick record before any write

A step asked for by name opens a change once it edits a file, a write into the knowledge homes included, and a close opens a quick record first, so the hooks' hold has no exempt path (J-102 S2).

Authorised by: 2026-10-21 The operator's card of 2026-10-21, "A record for every write (Recommended)" (docs/DECISIONS.md, the rows of 2026-10-21): a close asked for by name that writes only to the decisions book, the ADR home or the glossary, and the orientation's survey writing its result into the knowledge homes, each open a quick record first, so the hooks' hold on a workspace while no change is open is one rule with no list of exempt paths
Pages it touched: ROUTING.md

Rulings, R1 to R22

The cutover of the block to the modes (S16a of modes-records-recipes), under the operator's rulings R5 and R11 of 2026-10-04, four modes the agent proposes and waits on ("agent doesn't runs any mode at default until users ask him to just implement without asking"), and R16 of 2026-10-07, the roster by kind, a step run by the mode, a start chosen from the situation a request begins in, a habit loaded when its situation arises ("update the agents md created by greenline product to mention the kind with the skill table and also prose about when to use what kind skill"); The operator's cards of 2026-10-14 on part 2 of the-whole-change, each "Rule as proposed": a change is open while a session holds it and stopped when none does, set at every stop with its "next" line, and resuming sets it open; a new request that is not a follow-up stops the open change first; greenline status lists each open and stopped change with its "next" line; and a close asked for by name that writes only into the knowledge homes needs no change record; The operator's words of 2026-10-18 on the redesign (N-56, items 2 and 7), "we need the upstream prose upfront and references hold how to work meaning the artefacts etc" and, on the ingest procedures, "we wanna have there prose .. what we don't wanna have is there artefact system and fit them to use ours": a skill's front is the upstream prose its recipe cuts, and greenline's mechanics, where the step's work lands, its section's form, its commands and its depths at each mode, stand on its references page (J-93 S2)
The cutover of the block to the modes (S16a of modes-records-recipes), under the operator's rulings R5 and R11 of 2026-10-04, four modes the agent proposes and waits on ("agent doesn't runs any mode at default until users ask him to just implement without asking"), and R16 of 2026-10-07, the roster by kind, a step run by the mode, a start chosen from the situation a request begins in, a habit loaded when its situation arises ("update the agents md created by greenline product to mention the kind with the skill table and also prose about when to use what kind skill"); The operator's cards of 2026-10-14 on part 2 of the-whole-change, each "Rule as proposed": a change is open while a session holds it and stopped when none does, set at every stop with its "next" line, and resuming sets it open; a new request that is not a follow-up stops the open change first; greenline status lists each open and stopped change with its "next" line; and a close asked for by name that writes only into the knowledge homes needs no change record; The operator's cards of 2026-10-14 on part 4 of the-whole-change, each "Rule as proposed", under N-49's root card that the owner chooses where the change's checkout lives: the proposal names where the change's commits will go, read from local facts with no network command, the current branch when it is not the default branch or there is no remote and a new branch greenline/<id> otherwise, the owner's answer final; a worktree holds the change's checkout only on the owner's request and only where the harness runs the session in it, and no fresh agent runs in one of its own; the close step offers the landing in one line by the setup, a push and a pull request where the remote is a forge, a local merge where there is no remote, or the branch left, each only on the owner's word, the push and pull-request rule moving into the block and the close step while pr-writing keeps the writing method; and a plan's tickets share the planning change's branch, each ticket's commits carrying its own trailer, and the planning change's close offers the landing for the whole; The operator's cards of 2026-10-14 on part 5 of the-whole-change, the walk's cures: "A branch of its own", a change's commits never going to another change's branch, the new change taking greenline/<id> from the default branch where a remote exists and the default branch itself where there is none; "At the proposal", the change's id chosen when the proposal is written, its branch, working folder and record taking the same id; "Yes, every stop commits", every stop committing the record with the change's trailer, so a stopped change is found from any branch and after a clone and resumes on the branch that commit sits on; "Not counted", an agent a step's method starts named in that step's section and counted nowhere; "The one brief, the method's extras", that agent getting the one brief with the extras the page that starts it names; and "Settle in S6" for the orientation's edges and the setup's, the default branch being origin/HEAD, else init.defaultBranch, else the branch HEAD names, and a remote that is no forge offering the local merge or the branch left, never a pull request; The operator's words of 2026-10-18 on the redesign (N-56, items 2 and 7), "we need the upstream prose upfront and references hold how to work meaning the artefacts etc" and, on the ingest procedures, "we wanna have there prose .. what we don't wanna have is there artefact system and fit them to use ours": a skill's front is the upstream prose its recipe cuts, and greenline's mechanics, where the step's work lands, its section's form, its commands and its depths at each mode, stand on its references page (J-93 S2)
The cutover of the block to the modes (S16a of modes-records-recipes), under the operator's rulings R5 and R11 of 2026-10-04, four modes the agent proposes and waits on ("agent doesn't runs any mode at default until users ask him to just implement without asking"), and R16 of 2026-10-07, the roster by kind, a step run by the mode, a start chosen from the situation a request begins in, a habit loaded when its situation arises ("update the agents md created by greenline product to mention the kind with the skill table and also prose about when to use what kind skill"); The operator's cards of 2026-10-14 on part 2 of the-whole-change, each "Rule as proposed": a change is open while a session holds it and stopped when none does, set at every stop with its "next" line, and resuming sets it open; a new request that is not a follow-up stops the open change first; greenline status lists each open and stopped change with its "next" line; and a close asked for by name that writes only into the knowledge homes needs no change record; The operator's cards of 2026-10-14 on part 5 of the-whole-change, the walk's cures: "A branch of its own", a change's commits never going to another change's branch, the new change taking greenline/<id> from the default branch where a remote exists and the default branch itself where there is none; "At the proposal", the change's id chosen when the proposal is written, its branch, working folder and record taking the same id; "Yes, every stop commits", every stop committing the record with the change's trailer, so a stopped change is found from any branch and after a clone and resumes on the branch that commit sits on; "Not counted", an agent a step's method starts named in that step's section and counted nowhere; "The one brief, the method's extras", that agent getting the one brief with the extras the page that starts it names; and "Settle in S6" for the orientation's edges and the setup's, the default branch being origin/HEAD, else init.defaultBranch, else the branch HEAD names, and a remote that is no forge offering the local merge or the branch left, never a pull request; The operator's card of 2026-10-15 on the QA series, "One fix job after the fifth family", with the delegation of 2026-10-16 whose words finalise the fix job's slices: a start or a habit loads only in the situation its row names, architecture-survey at an orientation and never as one where a change record exists, secrets only with a secret in reach and ponytail before code the request leaves open; a start is named in the record only when it ran; the survey never opens its report; a session with nothing to resume says so and asks for the request; diagnose ranks its hypotheses before the first probe and keeps them ranked; and ponytail builds only on a measured need and reads simplify.md before a refactor; The operator's words of 2026-10-18 on the redesign (N-56, items 2 and 7), "we need the upstream prose upfront and references hold how to work meaning the artefacts etc" and, on the ingest procedures, "we wanna have there prose .. what we don't wanna have is there artefact system and fit them to use ours": a skill's front is the upstream prose its recipe cuts, and greenline's mechanics, where the step's work lands, its section's form, its commands and its depths at each mode, stand on its references page (J-93 S2)
The cutover of the block to the modes (S16a of modes-records-recipes), under the operator's rulings R5 and R11 of 2026-10-04, four modes the agent proposes and waits on ("agent doesn't runs any mode at default until users ask him to just implement without asking"), and R16 of 2026-10-07, the roster by kind, a step run by the mode, a start chosen from the situation a request begins in, a habit loaded when its situation arises ("update the agents md created by greenline product to mention the kind with the skill table and also prose about when to use what kind skill"); The operator's card of 2026-10-15 on the QA series, "One fix job after the fifth family", with the delegation of 2026-10-16 whose words finalise the fix job's slices: a start or a habit loads only in the situation its row names, architecture-survey at an orientation and never as one where a change record exists, secrets only with a secret in reach and ponytail before code the request leaves open; a start is named in the record only when it ran; the survey never opens its report; a session with nothing to resume says so and asks for the request; diagnose ranks its hypotheses before the first probe and keeps them ranked; and ponytail builds only on a measured need and reads simplify.md before a refactor
The cutover of the block to the modes (S16a of modes-records-recipes), under the operator's rulings R5 and R11 of 2026-10-04, four modes the agent proposes and waits on ("agent doesn't runs any mode at default until users ask him to just implement without asking"), and R16 of 2026-10-07, the roster by kind, a step run by the mode, a start chosen from the situation a request begins in, a habit loaded when its situation arises ("update the agents md created by greenline product to mention the kind with the skill table and also prose about when to use what kind skill"); The operator's cards of 2026-10-14 on part 2 of the-whole-change, each "Rule as proposed": a change is open while a session holds it and stopped when none does, set at every stop with its "next" line, and resuming sets it open; a new request that is not a follow-up stops the open change first; greenline status lists each open and stopped change with its "next" line; and a close asked for by name that writes only into the knowledge homes needs no change record; The operator's cards of 2026-10-14 on part 5 of the-whole-change, the walk's cures: "A branch of its own", a change's commits never going to another change's branch, the new change taking greenline/<id> from the default branch where a remote exists and the default branch itself where there is none; "At the proposal", the change's id chosen when the proposal is written, its branch, working folder and record taking the same id; "Yes, every stop commits", every stop committing the record with the change's trailer, so a stopped change is found from any branch and after a clone and resumes on the branch that commit sits on; "Not counted", an agent a step's method starts named in that step's section and counted nowhere; "The one brief, the method's extras", that agent getting the one brief with the extras the page that starts it names; and "Settle in S6" for the orientation's edges and the setup's, the default branch being origin/HEAD, else init.defaultBranch, else the branch HEAD names, and a remote that is no forge offering the local merge or the branch left, never a pull request; The operator's card of 2026-10-15 on the QA series, "One fix job after the fifth family", with the delegation of 2026-10-16 whose words finalise the fix job's slices: a start or a habit loads only in the situation its row names, architecture-survey at an orientation and never as one where a change record exists, secrets only with a secret in reach and ponytail before code the request leaves open; a start is named in the record only when it ran; the survey never opens its report; a session with nothing to resume says so and asks for the request; diagnose ranks its hypotheses before the first probe and keeps them ranked; and ponytail builds only on a measured need and reads simplify.md before a refactor
The cutover of the block to the modes (S16a of modes-records-recipes), under the operator's rulings R5 and R11 of 2026-10-04, four modes the agent proposes and waits on ("agent doesn't runs any mode at default until users ask him to just implement without asking"), and R16 of 2026-10-07, the roster by kind, a step run by the mode, a start chosen from the situation a request begins in, a habit loaded when its situation arises ("update the agents md created by greenline product to mention the kind with the skill table and also prose about when to use what kind skill")
The cutover of the block to the modes (S16a of modes-records-recipes), under the operator's rulings R5 and R11 of 2026-10-04, four modes the agent proposes and waits on ("agent doesn't runs any mode at default until users ask him to just implement without asking"), and R16 of 2026-10-07, the roster by kind, a step run by the mode, a start chosen from the situation a request begins in, a habit loaded when its situation arises ("update the agents md created by greenline product to mention the kind with the skill table and also prose about when to use what kind skill"); The operator's cards of 2026-10-14 on part 2 of the-whole-change, each "Rule as proposed": a change is open while a session holds it and stopped when none does, set at every stop with its "next" line, and resuming sets it open; a new request that is not a follow-up stops the open change first; greenline status lists each open and stopped change with its "next" line; and a close asked for by name that writes only into the knowledge homes needs no change record; the operator's card of 2026-10-19 naming the three modes, "quick, regular, careful (Recommended)": the old names and the trial step in a skill's prose are corrected by the smallest substitution; The operator's words of 2026-10-18 on the redesign (N-56, items 2 and 7), "we need the upstream prose upfront and references hold how to work meaning the artefacts etc" and, on the ingest procedures, "we wanna have there prose .. what we don't wanna have is there artefact system and fit them to use ours": a skill's front is the upstream prose its recipe cuts, and greenline's mechanics, where the step's work lands, its section's form, its commands and its depths at each mode, stand on its references page (J-93 S2); The operator's card of 2026-10-21, "A record for every write (Recommended)" (docs/DECISIONS.md, the rows of 2026-10-21): a close asked for by name that writes only to the decisions book, the ADR home or the glossary, and the orientation's survey writing its result into the knowledge homes, each open a quick record first, so the hooks' hold on a workspace while no change is open is one rule with no list of exempt paths
The cutover of the block to the modes (S16a of modes-records-recipes), under the operator's rulings R5 and R11 of 2026-10-04, four modes the agent proposes and waits on ("agent doesn't runs any mode at default until users ask him to just implement without asking"), and R16 of 2026-10-07, the roster by kind, a step run by the mode, a start chosen from the situation a request begins in, a habit loaded when its situation arises ("update the agents md created by greenline product to mention the kind with the skill table and also prose about when to use what kind skill"); The operator's cards of 2026-10-14 on part 2 of the-whole-change, each "Rule as proposed": a change is open while a session holds it and stopped when none does, set at every stop with its "next" line, and resuming sets it open; a new request that is not a follow-up stops the open change first; greenline status lists each open and stopped change with its "next" line; and a close asked for by name that writes only into the knowledge homes needs no change record; The operator's cards of 2026-10-14 on part 4 of the-whole-change, each "Rule as proposed", under N-49's root card that the owner chooses where the change's checkout lives: the proposal names where the change's commits will go, read from local facts with no network command, the current branch when it is not the default branch or there is no remote and a new branch greenline/<id> otherwise, the owner's answer final; a worktree holds the change's checkout only on the owner's request and only where the harness runs the session in it, and no fresh agent runs in one of its own; the close step offers the landing in one line by the setup, a push and a pull request where the remote is a forge, a local merge where there is no remote, or the branch left, each only on the owner's word, the push and pull-request rule moving into the block and the close step while pr-writing keeps the writing method; and a plan's tickets share the planning change's branch, each ticket's commits carrying its own trailer, and the planning change's close offers the landing for the whole; The operator's cards of 2026-10-14 on part 5 of the-whole-change, the walk's cures: "A branch of its own", a change's commits never going to another change's branch, the new change taking greenline/<id> from the default branch where a remote exists and the default branch itself where there is none; "At the proposal", the change's id chosen when the proposal is written, its branch, working folder and record taking the same id; "Yes, every stop commits", every stop committing the record with the change's trailer, so a stopped change is found from any branch and after a clone and resumes on the branch that commit sits on; "Not counted", an agent a step's method starts named in that step's section and counted nowhere; "The one brief, the method's extras", that agent getting the one brief with the extras the page that starts it names; and "Settle in S6" for the orientation's edges and the setup's, the default branch being origin/HEAD, else init.defaultBranch, else the branch HEAD names, and a remote that is no forge offering the local merge or the branch left, never a pull request
The cutover of the block to the modes (S16a of modes-records-recipes), under the operator's rulings R5 and R11 of 2026-10-04, four modes the agent proposes and waits on ("agent doesn't runs any mode at default until users ask him to just implement without asking"), and R16 of 2026-10-07, the roster by kind, a step run by the mode, a start chosen from the situation a request begins in, a habit loaded when its situation arises ("update the agents md created by greenline product to mention the kind with the skill table and also prose about when to use what kind skill"); and R22 of 2026-10-08, the re-cut brief accepted with the names of the roster table and the trial names ("yes amend, with one change")
The cutover of the block to the modes (S16a of modes-records-recipes), under the operator's rulings R5 and R11 of 2026-10-04, four modes the agent proposes and waits on ("agent doesn't runs any mode at default until users ask him to just implement without asking"), and R16 of 2026-10-07, the roster by kind, a step run by the mode, a start chosen from the situation a request begins in, a habit loaded when its situation arises ("update the agents md created by greenline product to mention the kind with the skill table and also prose about when to use what kind skill"); The operator's cards of 2026-10-14 on parts 1 and 2 of the-whole-change: "Lifetime by reader" (P1.3), a brief, a relay note or a probe being a working file under tmp/<id>/ that the CLI deletes when the change is done and refuses to delete while the record cites it; and P2.11, "Rule as proposed", greenline tidy [--change <id>] removing tmp/<id>/ for done and dropped changes, refusing a path the record cites, and being what the close step runs; The operator's words of 2026-10-18 on the redesign (N-56, items 2 and 7), "we need the upstream prose upfront and references hold how to work meaning the artefacts etc" and, on the ingest procedures, "we wanna have there prose .. what we don't wanna have is there artefact system and fit them to use ours": a skill's front is the upstream prose its recipe cuts, and greenline's mechanics, where the step's work lands, its section's form, its commands and its depths at each mode, stand on its references page (J-93 S2)
The method items carry the cutover of the block to the modes (S16a), under the operator's rulings of 2026-10-04, "cool then lock everything in": a start hands the job to a mode the owner approves, every change has one record with its working files and its folder, and a start that edits no file needs no mode and no record
R16 of 2026-10-07, a start chosen from the situation a request begins in ("update the agents md created by greenline product to mention the kind with the skill table and also prose about when to use what kind skill")
the operator's ruling R22 of 2026-10-08 on the re-cut brief, "yes amend, with one change": the roster table's names stand, router, diagnose and architecture-survey among them, with the trial names idea-refine, constraint-driven-development, correct and improve-instructions
J-59, on the operator's words of 2026-10-09 ('okay then implement all of this'): a gist of at most twelve words on every account whose reason is stated; no text, measure or method changes
The operator's cards of 2026-10-14 on part 2 of the-whole-change, each "Rule as proposed": a change is open while a session holds it and stopped when none does, set at every stop with its "next" line, and resuming sets it open; a new request that is not a follow-up stops the open change first; greenline status lists each open and stopped change with its "next" line; and a close asked for by name that writes only into the knowledge homes needs no change record
The operator's cards of 2026-10-14 on part 4 of the-whole-change, each "Rule as proposed", under N-49's root card that the owner chooses where the change's checkout lives: the proposal names where the change's commits will go, read from local facts with no network command, the current branch when it is not the default branch or there is no remote and a new branch greenline/<id> otherwise, the owner's answer final; a worktree holds the change's checkout only on the owner's request and only where the harness runs the session in it, and no fresh agent runs in one of its own; the close step offers the landing in one line by the setup, a push and a pull request where the remote is a forge, a local merge where there is no remote, or the branch left, each only on the owner's word, the push and pull-request rule moving into the block and the close step while pr-writing keeps the writing method; and a plan's tickets share the planning change's branch, each ticket's commits carrying its own trailer, and the planning change's close offers the landing for the whole
The operator's cards of 2026-10-14 on parts 1 and 2 of the-whole-change: "Lifetime by reader" (P1.3), a brief, a relay note or a probe being a working file under tmp/<id>/ that the CLI deletes when the change is done and refuses to delete while the record cites it; and P2.11, "Rule as proposed", greenline tidy [--change <id>] removing tmp/<id>/ for done and dropped changes, refusing a path the record cites, and being what the close step runs
The operator's cards of 2026-10-14 on part 5 of the-whole-change, the walk's cures: "A branch of its own", a change's commits never going to another change's branch, the new change taking greenline/<id> from the default branch where a remote exists and the default branch itself where there is none; "At the proposal", the change's id chosen when the proposal is written, its branch, working folder and record taking the same id; "Yes, every stop commits", every stop committing the record with the change's trailer, so a stopped change is found from any branch and after a clone and resumes on the branch that commit sits on; "Not counted", an agent a step's method starts named in that step's section and counted nowhere; "The one brief, the method's extras", that agent getting the one brief with the extras the page that starts it names; and "Settle in S6" for the orientation's edges and the setup's, the default branch being origin/HEAD, else init.defaultBranch, else the branch HEAD names, and a remote that is no forge offering the local merge or the branch left, never a pull request
The operator's card of 2026-10-15 on the QA series, "One fix job after the fifth family", with the delegation of 2026-10-16 whose words finalise the fix job's slices: a start or a habit loads only in the situation its row names, architecture-survey at an orientation and never as one where a change record exists, secrets only with a secret in reach and ponytail before code the request leaves open; a start is named in the record only when it ran; the survey never opens its report; a session with nothing to resume says so and asks for the request; diagnose ranks its hypotheses before the first probe and keeps them ranked; and ponytail builds only on a measured need and reads simplify.md before a refactor
The operator's card of 2026-10-19 naming the three modes, "quick, regular, careful (Recommended)": the old names and the trial step in a skill's prose are corrected by the smallest substitution
The operator's words of 2026-10-18 on the redesign (N-56, items 2 and 7), "we need the upstream prose upfront and references hold how to work meaning the artefacts etc" and, on the ingest procedures, "we wanna have there prose .. what we don't wanna have is there artefact system and fit them to use ours"; and J-93 S2's finalise words of 2026-10-19, "Fast route, merged slices, parallel jobs (Recommended)": a skill's front is the upstream prose its recipe cuts, and its mechanics, where its work lands, its section's form, its depths at each mode and its commands, stand on its references page
The operator's card of 2026-10-21, "A record for every write (Recommended)" (docs/DECISIONS.md, the rows of 2026-10-21): a close asked for by name that writes only to the decisions book, the ADR home or the glossary, and the orientation's survey writing its result into the knowledge homes, each open a quick record first, so the hooks' hold on a workspace while no change is open is one rule with no list of exempt paths

10 earlier entries

2026-10-19 2026-10-19-router-front-and-references

router's paths and commands move to a references page

Pages it touched: ROUTING.md, SKILL.md, references/greenline.md
2026-10-19 2026-10-19-router-premise-review

The router's line names anticipate careful's premise review

Pages it touched: ROUTING.md
2026-10-17 2026-10-17-router-starts-and-habits-in-their-situation

Starts and habits load only in their rows' situations

Pages it touched: SKILL.md
2026-10-14 2026-10-14-router-finds-a-change-by-its-commit

The router finds a stopped change by its record's commit

Pages it touched: ROUTING.md, SKILL.md
2026-10-14 2026-10-14-router-resumes-open-or-stopped

The router resumes an open or a stopped change

Pages it touched: SKILL.md
2026-10-14 2026-10-14-router-names-tidy

The routing map names greenline tidy for the working files

Pages it touched: ROUTING.md
2026-10-14 2026-10-14-router-resumes-on-the-branch

The router resumes a change on its branch

Pages it touched: ROUTING.md, SKILL.md
2026-10-14 2026-10-14-router-stop-and-resume

A resumed change is set open; an unrelated request stops it first

Pages it touched: ROUTING.md, SKILL.md
2026-10-09 2026-10-09-router-gists

Every account gets a short gist for the website
2026-10-08 2026-10-08-router-recipe

Project-router renamed router, its map naming the renamed starts

Pages it touched: ROUTING.md, SKILL.md