working with code in this repository.
## Project Overview
OpenContracts is an MIT-licensed enterprise document analytics platform for PDFs and text-based formats. It features a Django/GraphQL backend with PostgreSQL
ralphex
Autonomous plan execution with Claude Code - Go rewrite of ralph.py.
## LLM Documentation
See @llms.txt for usage instructions and Claude Code integration commands.
## Build Commands
```bash
make build # build binary
reasoning), and injects it into a different tool as a structured markdown handoff document.
## Build & Development Commands
```bash
pnpm install # Install dependencies
pnpm run build # TypeScript compile (tsc) → dist/
pnpm
/code) when working with code in this repository.
> **This file is not user-facing documentation.** It exists for Claude Code to read while working in the repository — it does
related labels are Haft local-practice carriers,
not FPF Core kinds by label alone.
Documents and graph nodes do not act. Name the acting system, role, method,
work, and evidence
/deploy` for deployments.
- **Context7 first**: When working with external libraries, check Context7 for current documentation before relying on training data.
## 2. Operator Model
## 3. Key Architecture Decisions
## 4. Tool Usage
never complete. (3) **Every field name in `INSPECTOR_FIELDS` (`claude-cli.ts`) must exist in a documented per-event schema, and be read by something.** A compile-time assertion against `keyof InspectorEvent
Release workflow (bumps version, tags, pushes) — see "Releases & Changelog" below before running
make release
```
### Documentation
```bash
# Serve docs locally at http://localhost:8000
make docs-serve
# Build documentation site
make
enabled, memory scans on DBVM-protected pages trigger `CLOCK_WATCHDOG_TIMEOUT` BSODs. This is documented as a hard requirement in both `README.md` and `AI_Context/AI_Guide_MCP_Server_Implementation.md`; don't weaken the assumption
date with the latest changes.
- When planning, never write time/calendar estimates into documents.
## Development Workflow
When searching for code, ALWAYS exclude the `.specstory` directory.
Don't just make your
docs`
- `frontend`
- `manager`
- `ml-engineer`
- `prompt-engineer`
- `qa`
- `resolver`
- `retrieval`
- `reviewer`
- `security`
- `visionary`
- `vp`
## Documentation duty
Every PR that adds or changes a feature MUST update docs in the same
claude-plugin/`.
- Hooks live in `hooks/`.
- On Windows, hook commands should use the documented wrapper strategy in
`docs/windows/polyglot-hooks.md`.
- Do not hard-code private machine paths, local session IDs, or personal
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.