Skip to content

orient: 'findings mentioning <target>' section is unfiltered when a _kos graph is present #88

Description

@arcaven

Symptom

kos orient <unknown-target> (e.g. a string matching no repo) prints a section headed "## kos findings mentioning " that lists EVERY finding in the nearest graph — none of which mention the target. Verified: kos orient usher listed 19 findings; grep -ril usher _kos/findings/ returned zero files. The frontier-questions section is likewise unfiltered.

Cause

When a nearest _kos/ graph exists, gather() loads findings via load_findings_unfiltered() (src/orient.rs:337) — no target filtering on this path — but print_human labels the section "mentioning {target}" (src/orient.rs:1132). Target filtering only exists in the legacy fallback path (load_findings, src/orient.rs:875).

Expected

Either filter the graph-path findings/questions by target mention (matching the legacy path and the header), or relabel the sections honestly ("## Findings (nearest graph)") when unfiltered. Filtering seems right for named targets; unfiltered is right for the bare/standalone form.

Observed 2026-07-12 from aae-orc while probing a candidate new-project name — the misleading header suggested prior art existed when it didn't.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions