| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 1 | 7 | 6 | 7% |
| Commands | 2 | 4 | 3 | 22% |
| Section tags | 3 | 2 | 2 | 43% |
What each file covers
Sections
1 shared · 7 only in A · 6 only in B- − NSForge Agent Harness
- − Goal
- − North Star
- − Working Style
- − Ground Truth: one command
- − Guardrails
- − Related Files
- + NSForge: Project Rules
- + Goals
- + Canonical Commands
- + Safety / Hygiene
- + Prefer Existing Patterns
- + Repo Defaults
- Repo Layout (DDD)
Commands
2 shared · 4 only in A · 3 only in B- − python scripts/check.py --json
- − python scripts/check.py --gates lint,type,test
- − mypy
- − uv run ...
- + uv run ruff check .
- + uv run mypy src --ignore-missing-imports
- + uv run pytest
- python scripts/check.py
- python scripts/gen_capabilities.py
Section tags
3 shared · 2 only in A · 2 only in B- − security
- − agent-behaviour
- + test
- + lint-format
- code-style
- architecture
- do-not
Line diff
u9401066/nsforge-mcp · AGENTS.md
@@ −1 @@
1# NSForge Agent Harness
2
3Workspace instructions for autonomous agents (Copilot, Cline, Codex, OpenHands,
4Hermes, …) working in the **Neurosymbolic Forge (NSForge)** repository.
5
6## Goal
7
8Help build and operate NSForge — an MCP server that turns *concepts* into
9verifiable, traceable *entities* (symbols → derivations → algorithms). The AI
10orchestrates; deterministic tools reify. See
11`docs/reification-ladder-direction.md` for the north star.
12
13## North Star
14
15> Every symbol / equation / value / line of code in a final result must have a
16> tool call as its "birth certificate" (provenance). The AI must not hand-derive
17> any of them.
18
19Success = the amount the AI computes by hand approaches zero.
20
21## Working Style
22
23- Use Traditional Chinese unless the user asks otherwise.
24- Prefer exact file paths, command output summaries, and verification results.
25- Offload mechanical/deterministic steps (symbolic calculation, simplification,
26 code generation) to tools — do not hand-derive formulas.
27- When changing behavior, add a focused regression test under `tests/`.
28
29## Ground Truth: one command
30
31Before and after changes, verify against the green baseline:
32
33```bash
34python scripts/check.py # all gates
35python scripts/check.py --json # machine-readable summary (for agents)
36python scripts/check.py --gates lint,type,test # subset
37```
38
39Gates: lint, format, type, import, manifest, test, bench, generic, provenance, harness, diff. Exit code 0 = green.
40(bench = derivation-correctness of `benchmarks/*.json` through the L3 orchestrator;
41generic = arbitrary unseen compositions derive correctly, proving NSForge is a
42derivation *calculus*, not a hand-built formula library; provenance = every
43benchmark derivation carries a complete tool-provenance ledger, no hand-derived leaks;
44harness = the harness self-checks its own invariants — version single-source,
45self-describing tools, and gate/doc parity — so agents can trust the signal.)
46
47## Repo Layout (DDD)
48
49- `src/nsforge/domain/`: pure domain models/value objects (no I/O)
50- `src/nsforge/application/`: use-cases / orchestration
51- `src/nsforge/infrastructure/`: adapters (sympy engine, formula sources, file I/O)
52- `src/nsforge_mcp/`: MCP tool layer + server wiring (`server.py`, `tools/`)
53- `docs/agent/capabilities.json`: machine-readable tool manifest (self-describing)
54
55## Guardrails
56
57- Keep `src/nsforge/domain` free of I/O and infrastructure imports.
58- Do not weaken `mypy` strict or skip gates just to make checks pass.
59- Prefer `uv run ...` so tools use the project venv.
60- Avoid destructive git ops (`reset --hard`, `clean -fdx`) unless asked.
61- Never commit secrets or generated outputs (`dist/`, `.venv/`, `data/`).
62- After adding/removing an `@mcp.tool`, regenerate the manifest:
63 `python scripts/gen_capabilities.py`.
64
65## Related Files
66
67- `docs/reification-ladder-direction.md` — architecture direction
68- `scripts/check.py` — verification harness (ground truth)
69- `scripts/gen_capabilities.py` — capability manifest generator
70- `.github/copilot-instructions.md` — Copilot rules
71- `memory-bank/activeContext.md` — current focus
72
u9401066/nsforge-mcp · .clinerules/00-project.md
@@ +1 @@
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
@@ −1 +1 @@
1−# NSForge Agent Harness
1+# NSForge: Project Rules
22
3−Workspace instructions for autonomous agents (Copilot, Cline, Codex, OpenHands,
4−Hermes, …) working in the **Neurosymbolic Forge (NSForge)** repository.
3+Rules for Cline (and other agents) in the Neurosymbolic Forge repository.
54
6−## Goal
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.
710
8−Help build and operate NSForge — an MCP server that turns *concepts* into
9−verifiable, traceable *entities* (symbols → derivations → algorithms). The AI
10−orchestrates; deterministic tools reify. See
11−`docs/reification-ladder-direction.md` for the north star.
12−
13−## North Star
14−
15−> Every symbol / equation / value / line of code in a final result must have a
16−> tool call as its "birth certificate" (provenance). The AI must not hand-derive
17−> any of them.
18−
19−Success = the amount the AI computes by hand approaches zero.
20−
21−## Working Style
22−
23−- Use Traditional Chinese unless the user asks otherwise.
24−- Prefer exact file paths, command output summaries, and verification results.
25−- Offload mechanical/deterministic steps (symbolic calculation, simplification,
26− code generation) to tools — do not hand-derive formulas.
27−- When changing behavior, add a focused regression test under `tests/`.
28−
29−## Ground Truth: one command
30−
31−Before and after changes, verify against the green baseline:
32−
33−```bash
34−python scripts/check.py # all gates
35−python scripts/check.py --json # machine-readable summary (for agents)
36−python scripts/check.py --gates lint,type,test # subset
37−```
38−
39−Gates: lint, format, type, import, manifest, test, bench, generic, provenance, harness, diff. Exit code 0 = green.
40−(bench = derivation-correctness of `benchmarks/*.json` through the L3 orchestrator;
41−generic = arbitrary unseen compositions derive correctly, proving NSForge is a
42−derivation *calculus*, not a hand-built formula library; provenance = every
43−benchmark derivation carries a complete tool-provenance ledger, no hand-derived leaks;
44−harness = the harness self-checks its own invariants — version single-source,
45−self-describing tools, and gate/doc parity — so agents can trust the signal.)
46−
4711 ## Repo Layout (DDD)
48−
4912 - `src/nsforge/domain/`: pure domain models/value objects (no I/O)
5013 - `src/nsforge/application/`: use-cases / orchestration
5114 - `src/nsforge/infrastructure/`: adapters (sympy engine, formula sources, file I/O)
5215 - `src/nsforge_mcp/`: MCP tool layer + server wiring (`server.py`, `tools/`)
53−- `docs/agent/capabilities.json`: machine-readable tool manifest (self-describing)
5416
55−## Guardrails
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`
5622
57−- Keep `src/nsforge/domain` free of I/O and infrastructure imports.
58−- Do not weaken `mypy` strict or skip gates just to make checks pass.
59−- Prefer `uv run ...` so tools use the project venv.
60−- Avoid destructive git ops (`reset --hard`, `clean -fdx`) unless asked.
61−- Never commit secrets or generated outputs (`dist/`, `.venv/`, `data/`).
62−- After adding/removing an `@mcp.tool`, regenerate the manifest:
63− `python scripts/gen_capabilities.py`.
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.
6427
65−## Related Files
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`.
6634
67−- `docs/reification-ladder-direction.md` — architecture direction
68−- `scripts/check.py` — verification harness (ground truth)
69−- `scripts/gen_capabilities.py` — capability manifest generator
70−- `.github/copilot-instructions.md` — Copilot rules
71−- `memory-bank/activeContext.md` — current focus
35+## Repo Defaults
36+- Default branch: `master`.
7237
