risk-graph-indexer Resources

These are the trusted sources for teaching this codebase. The repo's own docs are the

highest-trust resource — they're written by the team that built it and kept current.

Knowledge

In-repo (highest trust — primary source)

• risk-graph-indexer/README.md

Top-level overview, service table, mermaid architecture + sequence diagrams, quick start. Use for: the 30-second pitch and the docker service map.

• risk-graph-indexer/docs/architecture.md

The canonical architecture doc: 3 services, the monitored set, node lifecycle, what creates nodes/edges. Use for: the authoritative data-flow model. Best single doc to teach from.

• risk-graph-indexer/CLAUDE.md

Hard requirements + invariants + anti-hallucination notes (e.g. "Memgraph has no APOC", "no full-graph scans"). Use for: how the team actually works, and gotchas.

• risk-graph-indexer/pkg/types/schema.go

The EdgeType / NodeType constants — the literal vocabulary of the graph (HOLDS, APPROVES, ADMIN_CTRL, …). Use for: the ground-truth edge/node list.

• risk-graph-indexer/pkg/decoder/

The 20 event decoders (decoder.go, decoder_protocol.go, topics.go). Use for: how raw logs become typed events.

• risk-graph-indexer/cmd/indexer/main.go

The indexer's bootstrap + run loops. Use for: the actual consume→decode→write entrypoint.

• risk-graph-indexer/docs/enrichment-pipeline.md

The authoritative 15-stage enrichment pipeline + periodic maintenance tasks (oracle bridger, LP/receipt refreshers, parity monitor). Use for: anything about node classification, discovery, or the enrichment worker. Best doc for Lesson 5's subsystem.

• risk-graph-indexer/docs/single-writer.md

The single-writer / graph-writer architecture behind pkg/graphwrite. Use for: when a ticket sends you into the lane/recorder/consumer write internals (beyond the "one atomic tx" model taught in Lesson 4).

• risk-graph-indexer/docs/ (runbooks, pricing-model.md, graphstore-migration.md, parity-matrix.md)

Other topic-specific deep dives. Use for: targeted reading when a lesson goes deep on a subsystem.

External (for bridging the gaps)

• A Tour of Go — official, interactive. Use for: just-enough Go syntax (goroutines, interfaces, channels).
• Memgraph Cypher docs — Use for: reading/writing the Cypher this codebase runs.
• Redis Streams intro — Use for: understanding the block queue + consumer groups.

Wisdom (Communities)

• The team itself / PR reviews — this is a proprietary work codebase; the highest-signal

"community" is the user's own team and their reviewers. Use for: real feedback on changes.

• (Public communities deferred — proprietary internal codebase, so general Go/Cypher/Redis

communities are the relevant fallback for stack questions, not the domain itself.)

Gaps

• No identified beginner-friendly internal "onboarding" doc beyond architecture.md — these

lessons are partly filling that gap. Confirm with the user whether a team onboarding doc exists.