Cline rules

1# NSForge: Project Rules
2 
3Rules for Cline (and other agents) in the Neurosymbolic Forge repository.
4 
5## Goals
6- Build an MCP server that reifies concepts into verifiable, traceable entities
7  (symbols → derivations → algorithms). The AI orchestrates; tools reify.
8- Prefer correctness and reproducibility: deterministic outputs, clear error
9  paths, and regression tests.
10 
11## Repo Layout (DDD)
12- `src/nsforge/domain/`: pure domain models/value objects (no I/O)
13- `src/nsforge/application/`: use-cases / orchestration
14- `src/nsforge/infrastructure/`: adapters (sympy engine, formula sources, file I/O)
15- `src/nsforge_mcp/`: MCP tool layer + server wiring (`server.py`, `tools/`)
16 
17## Canonical Commands
18- One-shot verification: `python scripts/check.py`
19  (gates: lint / format / type / import / manifest / test / bench / generic / provenance / harness / diff)
20- Individual gates: `uv run ruff check .`, `uv run mypy src --ignore-missing-imports`, `uv run pytest`
21- Regenerate tool manifest: `python scripts/gen_capabilities.py`
22 
23## Safety / Hygiene
24- Avoid editing or committing generated/ignored outputs: `dist/`, `data/`, `.venv/`.
25- Never print or commit secrets from `.env` or key files.
26- Avoid destructive git operations (`reset --hard`, `clean -fdx`) unless explicitly asked.
27 
28## Prefer Existing Patterns
29- Keep MCP tool outputs backward-compatible when possible.
30- Add focused tests with fixes; keep changes minimal and scoped.
31- Do not weaken mypy strict or skip gates to make checks pass.
32- For product/architecture context, start with `memory-bank/activeContext.md`,
33  `docs/reification-ladder-direction.md`, and `ARCHITECTURE.md`.
34 
35## Repo Defaults
36- Default branch: `master`.
37