Devpost Evidence

The project story should make only evidence-backed statements:

• one local daemon owns the writer lock and serves authenticated loopback MCP;
• supported local agent CLIs can be onboarded through eBrain’s bridge;
• bounded durable memory, workspaces, sessions, user-governed routing, and factual token telemetry are implemented and tested locally;
• the product was developed with authorship and review kept separate, and with written evidence per phase.

The static documentation website may be built and inspected locally as demonstration support. A local build is not evidence of a public deployment, repository visibility, or external submission.

Before submission, use the current test counts and a scrubbed live demonstration. Do not use personal workspaces, credential output, customer material, stale benchmark rankings, subscription prices, or an unreviewed public repository claim as evidence.

Video recording, repository visibility, external links, and form submission are owner actions that require explicit approval.