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
I0833
knowledge nodes and edges read each source once
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- Objective
- Time the knowledge stages, then remove the per-file subprocesses in discovery and extraction so that nodes and edges take one pass per source.
- Why
- knowledge nodes costs 5.7 s and flattens 146 files on this repository.
- Now
- Discovery hashes and flattens per file with a subprocess each.
- Wanted
- nodes and edges under 1 s on this repository with identical output.
- Done when
- unknown: the record declares no `completion`
- Risk
- Identity is a content hash per file; one sha256 subprocess per file remains unless hashing is batched, which shasum -a 256 with many arguments allows.
Acceptance
- Byte-identical nodes and edges output before and after
- Cases 64, 73, 74 and 75 pass unchanged
- Validation
MJ_TIMING=1 bin/majordomus knowledge nodesbash test/run.sh 73_knowledge_nodes- Evidence required
batch_reads- Evidence present
batch_reads
Scope
- Touches
lib/knowledge.shlib/knowledge.awktest/cases/64_knowledge_discovery.shtest/cases/73_knowledge_nodes.shtest/cases/74_knowledge_edges.sh- Not
Changing node identities or edge semantics- Depends on
- Priority
- p0
- Profile
- implementation
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-05
- Updated
- 2026-09-05
- Started
- 2026-09-05T02:40:00Z
- Verified
- 2026-09-05T03:05:00Z
- Completed
- 2026-09-05T03:05:00Z
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.