administrator/DocForge2
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions Pages

feat: add deterministic preview rendering

Browse source
This commit is contained in:
Andraxion 2026-07-22 03:32:05 -04:00
parent 8c75f4f44d
commit 411f417670
23 changed files with 1413 additions and 142 deletions
Download patch file Download diff file Expand all files Collapse all files

12
ACTIVE_SLICE.md
View file

@ -1,11 +1,11 @@
# Active slice
```text
Slice: DFG-4 deterministic previews and renderer orchestration
Goal: Produce bounded, reproducible previews and configured derived outputs from validated project data without granting arbitrary execution or canonical write authority.
In scope: Preview contracts, renderer declarations, input and output confinement, deterministic render identity, stale detection, atomic derived output replacement, render status, MCP preview and render-status tools, and tests.
Out of scope: Canonical changeset application, arbitrary commands, project-specific adapters, Git mutation, deployment, accounts, HTTP transport, and a web UI.
Done when: The same validated project and renderer version produce the same preview identity; stale or escaped inputs fail closed; failed renders preserve prior derived output; the MCP surface cannot select an undeclared renderer or command.
Owners: Canonical files retain facts. Changesets retain proposals. Preview and renderer owners produce disposable derived artifacts only.
Slice: DFG-5 Worldforge shadow adapter
Goal: Prove that a project-specific adapter can reproduce Worldforge documentation semantics and generated output without changing the live Worldforge workflow.
In scope: Worldforge source mapping, authority and graph validation, active and phase context profiles, render models, parallel index comparisons, and byte-for-byte shadow output checks.
Out of scope: Canonical changeset application, live workflow replacement, public output changes, deployment, arbitrary commands, Git mutation, accounts, HTTP transport, and a web UI.
Done when: The shadow adapter matches current Worldforge nodes, edges, bounded contexts, validation results, and rendered outputs while existing Worldforge manual tests remain green.
Owners: DocForge core retains generic mechanics. The Worldforge adapter owns Worldforge-specific semantics. Existing Worldforge sources and builders remain authoritative during shadow adoption.
Proof: Pending implementation and verification.
```