README.md

Backend Docs

Canonical documentation home for overlord-be.

Current repo surfaces:

• ../overlord-be-coordinator/ is the only formal Node package in this repo.
• ../overlord-be-db/ is a backend-owned Windows helper for local PostgreSQL bootstrap and runtime control.
• Architecture docs still describe the broader target-state service lineup, but only current packages are present in the tree today.

Read First

• Architecture
• Coordinator
• Indexers
• Frontend

Interfaces And Operations

• Configuration
• Containerization
• p2p-overlord RC1 Parity Execution Plan
• p2p-overlord Release Policy
• Roadmap
• ID Index

eMuleBB Product-Family Notes

• The canonical eMuleBB-compatible REST contract is repos/emulebb-tooling/docs/rest/REST-API-OPENAPI.yaml.
• Deterministic ED2K server scenarios should use the eMuleBB goed2k-server fork, not the obsolete emulebb-ed2k-server fork or p2p-overlord ED2K server lineage.

Backlog

• Active Backlog
• Backlog Archive

Repo Guards

• In the eMuleBB workspace, shared workspace policy lives in ../emulebb-tooling/docs/WORKSPACE-POLICY.md. In the standalone p2p-overlord workspace, shared workspace quality and opportunistic-refactoring policy lives in ../../p2p-overlord-tooling/docs/WORKSPACE_POLICY.md. This section keeps the backend-specific guard notes.
• From ../p2p-overlord-tooling, run python -m overlord_tooling guard-tracked-files --repo-root ../p2p-overlord-be to validate tracked files for local path leaks and configured personal-name filename leaks.