Skip to content

I1013 — Search over the graph, generated, with nothing to run

Provide one search over identities, titles, descriptions, tags, categories, commands, routes and documents, from a generated index that works in the static build with no service behind it.

BLOCKED wave 4 · p2 · implementation profile · parallel safe

Part of capability-graph — One capability graph, two projections, and no second inventory of what this repository can do.

Blocked. This issue cannot start until I1007 is done. The status is derived from that, not declared.

Objective

Provide one search over identities, titles, descriptions, tags, categories, commands, routes and documents, from a generated index that works in the static build with no service behind it.

Why

A repository this size does not need a search service, and adding one would put the published site behind an availability dependency it currently does not have.

Current state

No unified search exists over the layer.

Desired state

One generated index serves both projections, its contents derive from the graph, and it costs nothing to operate.

Scope

  • share/cockpit/src

Out of scope

  • An external search service for a graph of this size
  • A hand-maintained index or keyword list

Dependencies

What waits on this

Acceptance criteria

  • The index is generated from the graph and covers identities, titles, descriptions, tags, categories, commands, routes and documents
  • Search works in the static build with no backend
  • A newly registered capability is findable after generation with no further edit
  • The index size is measured and counted against the asset budget

Validation

  • bash test/run.sh
  • majordomus generate --check

Evidence required

  • search_generated
  • static_search_works

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Risk

A client-side index grows with the repository until it dominates the page weight. Measuring it now is what makes the later decision to page or trim it a measurement rather than a surprise.

Timeline

started
—
verified
—
completed
—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I1013.yaml. Read it back with majordomus plan show I1013.