diff --git a/docs.html b/docs.html index 643454b..a1306d0 100644 --- a/docs.html +++ b/docs.html @@ -66,7 +66,8 @@
+ The synthesis pipeline runs through Pi or MCP. It combines a product vision with reusable, + versioned reimplementation specs, pauses for explicit human selection, preserves conflicts, + and produces work packages with a decision-level provenance ledger. +
+ +/codecarto-init synthesis
+# Fill .codecarto/inputs/vision.md
+/codecarto-next --auto
+ The first run creates a ranked proposal, completes that phase, and then intentionally stops at the confirmation preflight.
+# In proposal.md:
+| [x] | event-router | v2 | ... |
+
+/codecarto-next --auto
+ Merge and finalization read only the checked, version-pinned specs. An unknown entry or version is rejected before any LLM phase starts.
+
This site is plain HTML, CSS, and JavaScript. Drop it into public_html on your
@@ -236,7 +272,7 @@
CodeCartographer reads your source code multiple times across phases and produces thousands of diff --git a/features.html b/features.html index 2a1e59e..4bd1948 100644 --- a/features.html +++ b/features.html @@ -45,10 +45,10 @@
- Every pipeline starts with architecture. From there, you choose how far to go. The default is - a 7-phase full analysis with a split defect scan. Scale back when you only need orientation. + Six analysis variants scale from quick orientation to a deep audit. The forward synthesis + pipeline combines a vision with confirmed reusable specs to create a traceable project plan.
Phases form a DAG. Contracts and protocols can run in parallel after architecture. Porting waits for both. Reimplementation spec is last.
+Two directions: analysis distills source code into reusable specifications; synthesis combines human-confirmed specifications with a product vision and preserves decision-level provenance in the resulting plan.
- CodeCartographer turns "explain this repo" into a staged investigation. Architecture, defect - scan, behavioral contracts, protocol notes, porting synthesis, and a reimplementation spec. - Each finding is evidence-tagged so confidence stays visible. + CodeCartographer turns “explain this repo” into a staged, evidence-backed investigation—then + combines explicitly confirmed specifications with a new product vision to create a traceable + implementation plan.
The filesystem—not the conversation—is durable memory. A fresh LLM session reads the status and findings, then resumes without depending on compacted chat history.
Versioned library entries are proposed against a vision, explicitly confirmed by a human, merged with conflicts intact, and transformed into work packages with a decision-level provenance ledger.
+Language-agnostic build plan with modules, acceptance scenarios, and known unknowns.
+Confirmed specifications become architecture, work packages, acceptance gates, conflict dispositions, and a decision-level provenance ledger.
+THREAD_LOG\.md<\/code><\/h3>\s*(.*?)<\/p>/s)?.[1] ?? "";