Skip to content

JSON pipeline #10

Description

@duck-lint

Step 1 — LLM produces structured plan in JSON:

{
"task_type": "code_modification",
"constraint_class": "syntactic_preservation",
"edit_scope": "minimal_diff",
"risk_flags": [],
"proposed_patch": "..."
}

Step 2 — Codex consumes only the proposed_patch.

Step 3 — Diff checker validates token preservation.

Step 4 — Unit tests enforce correctness.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

  • Status
    Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions