A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I1007
The site renders the same graph, generated once
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- Objective
- Produce the static projection of the graph through the existing generation and site pipeline, so that the published site renders the same model the server does without a backend and without a second generator.
- Why
- A separate generation script for the site is the second universe this repository has already refused once. The generation target set exists and owns this.
- Now
- The site is generated from the registry and several derived datasets by scripts that each know their own output.
- Wanted
- The static projection is a target of the canonical generation, and the site consumes it like its other derived data.
- Done when
- unknown: the record declares no `completion`
- Risk
- Rendering yesterday's health as though it were current is the failure mode this issue exists to prevent, and it is a labelling problem, not a data problem.
Acceptance
- The static projection is produced by the canonical generation target set, with any shell involved being a thin adapter
- The published pages render the capabilities, the kinds, the relations and the coverage without any request to a backend
- Build-time and runtime data are distinguishable on the page, and a captured measurement is labelled as captured rather than shown as current
- The drift check covers the static projection
- Validation
majordomus generate --checkbash test/run.sh- Evidence required
static_projectionno_backend_required- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
apps/majordomus-cli/src/site.rssite- Not
A standalone cockpit generation scriptThe static build requiring any runtime API to render- Depends on
- Priority
- p0
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-06
- Updated
- 2026-09-06
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.