lair/tireless
3
0
Fork 1
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: stage 0 complete — agent login done, all three units active
All checks were successful
deploy / deploy (push) Successful in 5m35s
Details

Browse Source 
The interactive login is the one step in stage 0 that cannot be automated, and
it is now done. preflight reports a present subscription login; tireless-runner
is active alongside the api and poller.

Recording it because the previous text said the runner was in `failed`, which
was true for about an hour and is now exactly the kind of stale status this
repo keeps trying not to leave lying around.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013TxK1CWPkFXqdcXMJ4hVe6
This commit is contained in:
rob thijssen
2026-08-07 17:59:51 +03:00
parent bd658392ab
commit ae285f5597
2 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
doc/plan/design.md
View File

@@ -611,15 +611,15 @@ There is no invariant here that is merely written down.
loads at `tireless.internal`, all three units are active, `tireless preflight`
reports the expected billing mode, and the deploy workflow is green end to end.
**Deployed and verified, 2026-08-07.** The workflow runs green end to end;
`tireless-api` and `tireless-poller` are active on bob; `https://tireless.internal`
serves the dashboard and proxies `/v1`; the served certificate matches disk.
**Complete, deployed and verified, 2026-08-07.** The workflow runs green end to
end; all three units are active on bob; `https://tireless.internal` serves the
dashboard and proxies `/v1`; the served certificate matches disk; and
`tireless preflight` reports a present subscription login with the OpenCode lane
asserted non-Anthropic.
*Outstanding, and deliberately so:* `tireless-runner` is in `failed`, because the
interactive agent login has not been done as the service account on bob
(`script/infra-setup.sh` step 1). That is the invariant working — a runner with
no credentials refuses to start rather than pretending — and it is the one thing
in stage 0 that cannot be automated.
The interactive agent login (`script/infra-setup.sh` step 1) is done. Until it
was, `tireless-runner` sat in `failed` — which was the invariant working, not a
defect: a runner with no credentials refuses to start rather than pretending.
Seven faults were found getting the first deploy green, and they are worth
knowing because most were invisible rather than loud:

6
readme.md
View File

@@ -32,11 +32,11 @@ Full design, constraints and the staged implementation plan:
Working: the domain model, routing, budgets, plan validation, the policy guards,
configuration loading and validation, the four system prompts, and preflight.
The API and poller run on bob, the dashboard is served at
All three units run on bob, the dashboard is served at
`https://tireless.internal`, and the deploy workflow is green end to end.
`tireless-runner` deliberately refuses to start until the interactive agent
login has been completed as the service account — see `script/infra-setup.sh`.
Nothing is polled or claimed yet — that is stage 1. The runner is up but has no
job store to claim from.
Not built: Postgres persistence, the forge clients, the poll loop, and every
agent executor. Stages 1–8 in §7 of the design document say what lands when.