[indexer/verifier] Design future live RPC indexer boundary

[FlowmemoryAI]

Objective

Design the future live RPC indexer boundary without implementing production RPC access yet.

Allowed folders

• services/indexer/
• services/shared/
• services/verifier/ only for downstream contract references
• docs/ only for architecture/security updates
• research/indexer-verifier/ only for RPC boundary research notes

Forbidden folders

• contracts/
• hardware/
• apps/
• crypto implementation
• chain/L1 implementation
• tokenomics
• production RPC deployment
• production database deployment

Acceptance criteria

• Documents provider input/output boundary for future eth_getLogs and receipt reads.
• Defines no-secrets configuration expectations and .env limits if any.
• Defines retry, range, confirmation, and reorg assumptions as design notes only.
• Defines how live RPC observations must map into the existing fixture-based identity model.
• Does not add live RPC keys, production deployment, database, queue, or long-running service process.

Risk level

High

Recommended agent

FlowMemory Indexer / Verifier Agent