Skip to content
Cockpit0.29.0
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

I1107

Discovery is deterministic, cached, and its cost is known

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
two-folder-integration
Milestone status
ACTIVE
Wave
3
Waiting on
I1106
Holds back
I1123
Behind it in all
1
Evidence
0 of 3
In the waySubjectDetail
issueI1106I1106 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I1107

majordomus plan verify I1107

majordomus plan done I1107

What it is

Objective
Make one discovery over one tree produce one answer, cache it by what it was derived from, and measure what it costs — because everything downstream now pays that cost.
Why
A model every consumer reads is on the hot path of every command, including the ones that run when a person changes directory. An unmeasured spine becomes the reason the tool is avoided.
Now
The layer's flattening is cached by content hash and the executable's phases are timed. The composed model's own cost has not been measured.
Wanted
The cost is a benchmark with a baseline, the cache is keyed by the inputs, and a stale entry cannot be read for a changed tree.
Done when
unknown: the record declares no `completion`
Risk
A cache is a second thing that can be believed. Keying it by content hash means a wrong key costs time, never correctness.

Acceptance

  • Two discoveries over an unchanged tree produce structurally identical models, with no dependence on directory iteration order
  • The cache is keyed by the content it was derived from, so a stale entry costs a miss and never a wrong answer
  • Cold and warm discovery are benchmarked separately with a recorded baseline
  • A cache hit and a cache miss produce byte-identical output for every read-only command
Validation
majordomus bench --checkcargo test --workspace --all-features
Evidence required
deterministic_modelcache_correctcost_measured
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/index.rs.ai/repo/benchmarks/rust
Not
A cache that can serve a stale answer for a changed inputA persistent cache shared between repositories
Depends on
I1106
Priority
p1
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.