Indexer Integration

This topic is essential for teams that want to build reliable read infrastructure and derived services on top of PaperProof data.

Indexers turn canonical PaperProof events and object reads into queryable application views. Canonical filtering An indexer should validate: active package IDs; root and registry bindings; series ownership and artifact type; official comments tree ID; official likes book ID; governance config and vault relationships; prompt and memory registry bindings where applicable. Derived views Useful views include: recent artifacts by type; artifact detail and version history; comment trees and like state; proposal lists and voting records; claimable funds; prompt-route resolution; official memory capability status; deployment drift status. Operational requirements A production indexer should persist cursors, deduplicate events, record rejections, expose metrics, and distinguish provider failure from empty state....