Summary
Implement the write-back indexer pattern described in PLAN.md Section 9 (Pattern 2): an indexer with scoped write permissions that populates curated views directly in DWN records.
Context
The current indexer (Pattern 1) is read-only — it crawls DWN records and maintains in-memory materialized views. Pattern 2 would allow the indexer to write aggregated data (star counts, trending scores, search indices) back into the DWN as records, making them queryable by any DWN client without depending on a centralized indexer API.
Scope
- Grant the indexer a scoped role with write access to specific protocol paths (e.g.,
repo/stats)
- Write star count, trending score, and language/topic indices as DWN records
- Enable direct DWN queries for discovery (no indexer API needed)
- Consider incremental updates vs full recomputation
Notes
- Pattern 3 (compute modules running on the DWN itself) depends on future DWN capabilities and is out of scope for now
- The in-memory indexer with REST API (Pattern 1) remains the primary approach for the MVP
Summary
Implement the write-back indexer pattern described in PLAN.md Section 9 (Pattern 2): an indexer with scoped write permissions that populates curated views directly in DWN records.
Context
The current indexer (Pattern 1) is read-only — it crawls DWN records and maintains in-memory materialized views. Pattern 2 would allow the indexer to write aggregated data (star counts, trending scores, search indices) back into the DWN as records, making them queryable by any DWN client without depending on a centralized indexer API.
Scope
repo/stats)Notes