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

I0814

Give the worker a bounded slice of knowledge, not the knowledge base

Where it stands

Readiness: complete completion is recorded and every required evidence token is present
Status: DONE
Can start: not now
Milestone: M003
Milestone status: ACTIVE
Wave: 5
Waiting on: none
Holds back: I0815
Behind it in all: 2
Evidence: 1 of 1

Objective: Add a knowledge section to `majordomus context`, selected deterministically from what the active task and issue already reference, capped by a profile toggle and an item limit, dropped before any immutable fact when the budget is short, and named under EXCLUDED whenever it is dropped or switched off.
Why: A context builder that dumps an index has replaced a selection problem with a bigger one. The value is in choosing the few pointers a worker needs, from relationships that are already explicit, and in saying out loud what was left out.
Now: context assembles nine sections in authority order with a fixed drop order and names every exclusion. Its profile toggles decide what is asked for.
Wanted: The profile carries a knowledge toggle and a maximum item count, both in the profile allowlist. The section lists pointers — id, kind, title and source path — for the current issue, its dependencies, the claims it names and the documents it references. It sits below every immutable fact in the drop order and above nothing that outranks it.
Done when: unknown: the record declares no `completion`
Risk: The budget is already close to full on a rich task. If the knowledge section is added without measuring, it will be the section that always gets dropped, which is a feature nobody receives.

The section appears only when the profile asks for it, and its absence is named under EXCLUDED with the toggle that caused it
It is dropped before git, the task, the profile and open blockers under a tight budget, and the drop is named
Selection comes from explicit references only, and a case proves an unrelated document is not selected
A stale index makes the section report staleness rather than silently omit itself
The existing context case still passes unchanged

Validation: bash test/run.sh 3073_context_knowledge_slicebash test/run.sh 23_context
Evidence required: context_bounded
Evidence present: context_bounded

Touches: lib/context.shshare/skeletonshare/allow/profile.txt.majordomus/profilesdocstest/cases
Not: Any similarity-based selectionRebuilding the index from contextRaising the existing line budget
Depends on: I0811
Priority: p1
Profile: implementation
Parallel safe: false
Owner: unknown: the record declares no `owner`

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

Nothing is wrong with these records.