Skip to content

P1-X: Ensure P1 hierarchical/dialectical query pipeline meets DESIGN #76

@devlux76

Description

@devlux76

This is a super-task for finishing the remaining P1 work that must be completed to satisfy the DESIGN’s hierarchical + dialectical retrieval contract.\n\nIt is a child of #68 (P1 tracker). Close the subtasks below as they complete — this issue stays open until every subtask is done.\n\n### Subtasks (close the relevant issue when done)\n- [ ] Ensure HierarchyBuilder enforces Williams/fanout quotas and triggers splits when quotas are exceeded. (Related: #23)\n- [ ] Ensure Ranking/Pipeline is wired into as a resident-first hierarchical cascade (shelf → volume → book → page) with warm spill. (Related: #24)\n- [ ] Ensure FastNeighborInsert uses cutoff derived from (Williams-bound logic) rather than hardcoded constants. (Related: #57)\n- [ ] Ensure Query orchestrator enforces a subgraph cost budget (max subgraph size / max hops) and uses Hebbian-weighted edge traversal + provenance metadata. (Related: #60)\n- [ ] Expand integration test coverage to validate hierarchical structure presence + dialectical query behavior (knowledge gap, coherence path, bounded expansion). (Related: #61)\n\n### Completion guidelines\n- Close each source issue (e.g., #23, #24, #57, #60, #61) as soon as the implementation satisfies its acceptance criteria.\n- This issue should remain open until all checkbox items are complete and the system matches the DESIGN described in the P1 issues.\n\n> NOTE: This is a tracking issue, not the implementation itself. Use it to coordinate completion across the individual subtasks.

Metadata

Metadata

Labels

P1: highHigh priority — targets v0.5

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions