Generate and validate a separate local-content index #48

New issue

Open

opened 2026-07-31 01:25:51 -04:00 by JackFrostbyte · 0 comments

JackFrostbyte commented

2026-07-31 01:25:51 -04:00

Owner

Goal

Generate a search index and manifest for the user-local overlay without merging its
files or build provenance into the redistributable core index.

Requirements

Reuse the selected search backend and index-manifest concepts from Issues #20–#22.
Store local index files and manifests only in the local overlay.
Include source/document/chunk identifiers, acquisition record, recipe/version,
tool versions, timestamps, and input checksums needed for local validation.
Detect stale, missing, withdrawn, or corrupt local inputs.
Rebuild or remove only the affected local index data.
Never make local index files inputs to a core release.
Support an installation with only the core index or only locally imported content.

Deliverables

Local index build command.
Local index manifest and validation.
Deterministic fixture-based tests.
Staleness/corruption behavior.
Storage and resource-usage documentation.

Acceptance criteria

Core and local manifests are independently valid.
Local index creation cannot mutate the core index.
Stale and corrupt local content is detected before retrieval.
Withdrawn recipes are visibly represented without silently deleting user data.
Tests use redistributable fixtures and no live third-party downloads.

Out of scope

Federated ranking and result presentation.

## Goal Generate a search index and manifest for the user-local overlay without merging its files or build provenance into the redistributable core index. ## Requirements - Reuse the selected search backend and index-manifest concepts from Issues #20–#22. - Store local index files and manifests only in the local overlay. - Include source/document/chunk identifiers, acquisition record, recipe/version, tool versions, timestamps, and input checksums needed for local validation. - Detect stale, missing, withdrawn, or corrupt local inputs. - Rebuild or remove only the affected local index data. - Never make local index files inputs to a core release. - Support an installation with only the core index or only locally imported content. ## Deliverables - Local index build command. - Local index manifest and validation. - Deterministic fixture-based tests. - Staleness/corruption behavior. - Storage and resource-usage documentation. ## Acceptance criteria - [ ] Core and local manifests are independently valid. - [ ] Local index creation cannot mutate the core index. - [ ] Stale and corrupt local content is detected before retrieval. - [ ] Withdrawn recipes are visibly represented without silently deleting user data. - [ ] Tests use redistributable fixtures and no live third-party downloads. ## Out of scope - Federated ranking and result presentation.

JackFrostbyte added this to the User-Acquired Content Overlay v0.1 milestone

2026-07-31 01:25:51 -04:00

JackFrostbyte added the

type/implementation

area/search

labels

2026-07-31 01:25:51 -04:00

JackFrostbyte added a new dependency

2026-07-31 01:25:54 -04:00

#45 Define the bundled-core and user-local storage/index boundary

JackFrostbyte added a new dependency

2026-07-31 01:25:54 -04:00