Repository navigation
plan(invert): correct §3/§6 — ci.yml is a dsl serializer fold, not v2 06_translate - #5502
Merged
Merged
Conversation
…), not v2 06_translate The plan's prose said 'the same 06_translate machinery that emits ci.yml'. That is factually wrong: expected_ci_yml = serialize_yaml(project_workflow_to_yaml(ci_workflow)) is a dsl-tree serializer FOLD on the v1 seed, itself self-marked SCAFFOLD/§3-fork-of-v2-yaml. So the faithful ROADMAP analogue is serialize_markdown_source on the seed (row-driven, scaffold, dissolves to a v2 Markdown TargetModel), NOT a v2 Node crossing ci.yml does not do. Grounded by quiet-hawk-47; settles the deep-newt A-vs-B substrate-fork toward B-with-row-discipline. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The inversion plan (
docs/plans/invert-hand-maintained.md) §3 and §6 described ci.yml as emitted by "the same06_translatemachinery that already emits Rust / TypeScript / ci.yml." That is factually wrong and it mis-steered the markdown emit-target decision.The correction (grounded by quiet-hawk-47)
ci.ymlis realized asexpected_ci_yml = serialize_yaml(project_workflow_to_yaml(ci_workflow))— a dsl-tree serializer fold (extdeps.formats.yaml.serialize_yaml) on the v1 seed, itself self-marked SCAFFOLD / §3-fork-of-v2-yaml with a dissolution trigger to the eventual v2 yamlTargetModel. It is not the v206_translateemitter and does not do a dsl→v2Nodecrossing.So the faithful ROADMAP analogue is
serialize_markdown_source(project_roadmap_to_markdown(model))— a dsl serializer fold on the seed, row-driven (construct→spelling pairs in rows = the §6 grammar-inverse, dodging the medium-as-Node leakemission-ingestion-inverse.md§5.1 even as a scaffold), marked SCAFFOLD with dissolution trigger = the eventual v2MarkdownTargetModel. Forcing markdown onto a v2Nodecrossing would make the analogue heavier than its own template.This settles the deep-newt-165 A-vs-B substrate-fork toward B with row-discipline, and unblocks the quiet-hawk-47 roadmap_model + roadmap_gate slice.
Scope
Docs-only (two paragraphs in one plan doc). No
.dag/.rschange.— sent from warm-lark-306
🤖 Generated with Claude Code