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
I1112
What touches the root is two small blocks, and they never change again
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- Objective
- Reduce every root-level integration to a small, stable, machine-owned bridge: a managed block in the agent document that points at the layer, and — when direnv is wanted — one line that sources the environment integration.
- Why
- Root files are where an integration becomes visible and where it becomes a nuisance. A bridge that carries no logic never has to change, which means an upgrade touches nothing a person has to re-approve.
- Now
- Root documents carry generated blocks whose content is regenerated as the layer changes, and provider bootstraps are written to the root.
- Wanted
- A bridge names where the truth lives and stops. Upgrading Majordomus does not rewrite it, because there is nothing version-dependent inside it.
- Done when
- unknown: the record declares no `completion`
- Risk
- Every provider that wants a root file argues that its file is special. The answer is the same one: the file is an adapter, and its content is derived.
Acceptance
- Each bridge is bounded by markers, recorded in the ledger, and carries no logic — only a reference to where the canonical material lives
- Upgrading the tool leaves the bridges byte-identical, proved by reconciling with a newer version against an older adoption
- A bridge is created only when the surface genuinely requires a root file; where a tool can be configured programmatically, nothing is written
- The environment bridge is one stable line whose target lives under `.majordomus/`
- Validation
majordomus init --dry-runbash test/run.sh- Evidence required
bridges_minimalstable_across_versions- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
AGENTS.md.envrc- Not
Repository-domain logic in any root fileA bridge whose content depends on the version of the tool that wrote it- 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.