1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions Pages
Successor repository for the DocForge project-scoped documentation graph.
Find a file
2026-07-22 02:58:51 -04:00
docs feat: add isolated proposal changesets 2026-07-22 02:58:51 -04:00
schemas feat: add isolated proposal changesets 2026-07-22 02:58:51 -04:00
src/docforge feat: add isolated proposal changesets 2026-07-22 02:58:51 -04:00
tests feat: add isolated proposal changesets 2026-07-22 02:58:51 -04:00
.gitignore feat: establish read-only DocForge MCP foundation 2026-07-22 01:29:32 -04:00
ACTIVE_SLICE.md feat: add isolated proposal changesets 2026-07-22 02:58:51 -04:00
AGENTS.md feat: establish read-only DocForge MCP foundation 2026-07-22 01:29:32 -04:00
pyproject.toml feat: add isolated proposal changesets 2026-07-22 02:58:51 -04:00
README.md feat: add isolated proposal changesets 2026-07-22 02:58:51 -04:00
SLICE_HISTORY.md feat: add isolated proposal changesets 2026-07-22 02:58:51 -04:00
uv.lock feat: add isolated proposal changesets 2026-07-22 02:58:51 -04:00

DocForge

DocForge is a project-scoped documentation service for people and AI agents. It loads canonical Markdown and TOML from one repository, validates stable nodes and relationships, builds a disposable search index, and returns bounded context with source provenance.

DocForge does not own project facts. It does not select project work, edit generated output, run project commands, or perform Git and deployment operations.

Current gate

DFG-1 through DFG-3 are complete. DFG-4 is the active gate: deterministic previews and renderer orchestration over validated project data. Canonical application remains external and closed to the normal MCP server.

Development

uv sync
uv run python -m unittest discover -s tests -v
uv run docforge --project-root tests/fixtures/alpha validate
uv run docforge-mcp --project-root tests/fixtures/alpha --proposal-writer alpha-editor

The command prints deterministic JSON. Derived indexes live under each project's configured cache directory and are never canonical input.

Proposal writers are declared by ID in .docforge/project.toml. Each writer receives explicit node families and operation types. The MCP process binds to one writer at startup; tools cannot select or impersonate another writer. Create, update, move, and delete tools write only isolated JSON changesets below the configured changeset root.