Startup commands: how office, project-reset and board decide the machine and the session
Host resolution order, the local-machine check, the address table, when the host is remembered, why --host appears twice when starting from scratch, the three rebuild levels, and the six traps that produced every startup fault so far.
This commit is contained in:
@@ -87,6 +87,10 @@ Do not start the Go program until that passes.
|
||||
|
||||
## Operating rules
|
||||
|
||||
`docs/STARTUP-COMMANDS.md` explains how a project is opened: how the machine, the session and
|
||||
the screens are chosen, why `--host` is sometimes stated twice, and the traps (ssh to
|
||||
yourself, colour codes in names, workspace numbers, pages with no permanent pane).
|
||||
|
||||
`docs/OPERATING-RULES.md` is not optional reading. It has nine rules: the project folder
|
||||
convention, how a task is judged finished (a command agreed beforehand), approvals being
|
||||
content-bound, untrusted text being data, how secrets are handled, `ocr` review and
|
||||
|
||||
Reference in New Issue
Block a user