Guide / Repository memory

Evidence you can
follow back.

Engineering Board keeps engineering findings, proposed root causes, and recorded outcomes in repository-owned Markdown.

Explore the example

Open the investigation, select a finding, and follow its source record. H001 is a proposed explanation. The alternative and falsifier keep uncertainty visible; no outcome is recorded.

Begin with Codex

Follow the installation instructions. Initialization creates a board; capturing saves a finding to the inbox. Ask Codex to preview promotion before creating a durable board entry. Ask for relevant repository memory before choosing a fix, and record the observed result afterward.

Other clients

Claude Code installation commands are available in the installation section. For other MCP clients, obtain the Engineering Board repository and use its documented Python server configuration. Every bundled-plugin tool call targets an absolute repository path.

The authoritative setup guide is the repository README. Read the upstream README (requires internet).

What the example shows

The synthetic example illustrates how to inspect a proposed explanation and its source records. B001–B003 come from the bundled pattern-intelligence fixtures. H001 is illustrative. These records do not describe current product defects or demonstrate improved diagnosis.

The project board shows the repository’s actual published work. Its source links open the corresponding Markdown records on GitHub. The website is read-only; changes happen through your agent in your repository.

Keep claims tied to evidence