Skip to content

[DO NOT MERGE] prototype: reverse template variable extractor - #451

Draft
randlee wants to merge 2 commits into
developfrom
prototype/reverse-extract
Draft

[DO NOT MERGE] prototype: reverse template variable extractor#451
randlee wants to merge 2 commits into
developfrom
prototype/reverse-extract

Conversation

@randlee

@randlee randlee commented Aug 13, 2026

Copy link
Copy Markdown
Owner

⚠️ DO NOT MERGE — exploratory prototype only

This is a spike exploring a reverse template-variable extractor. It is kept open as a draft for visibility and discussion only, not for merging.

Opened so this work isn't left as an untracked dangling branch. A background agent is checking whether this maps to any planned initiative in docs/project-plan.md; if it does, a real sprint/PR will be scoped from scratch off current develop rather than merging this branch directly.

If no one claims this within a reasonable window, close it.

randlee added 2 commits July 20, 2026 22:49
Given a j2 template + rendered XML output, extracts the JSON variable
bindings that produced it — the reverse of sc-compose render.

Key features:
- Attribute, element-text, and block-text variable extraction
- include_vars / exclude_vars filtering
- Confidence score (% static text match) for template identification
- Bulk tested against 500 ATM payloads: 194/197 repo-qa-task extractions pass

Confidence discriminator: wrong template ≈0.005, correct ≈0.08–0.89.
Threshold of 0.05 cleanly separates correct from wrong.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant