Skip to content

Present the Low-first workflow and invite early-check recipes - #1

Draft
onoderakosen89 wants to merge 5 commits into
mainfrom
docs/low-first-check-recipes
Draft

onoderakosen89 wants to merge 5 commits into
mainfrom
docs/low-first-check-recipes

Conversation

@onoderakosen89

Copy link
Copy Markdown
Owner

Summary

  • Lead with a Low-first workflow for small implementation steps and repairs, backed by the earliest check that can give a conclusive result.
  • Show the same example at two levels: what a person can verify and where a machine can check it first.
  • Add a no-code recipe issue form, separate from runner adapter proposals. Node.js and pytest remain bundled defaults; other existing tools can be used in recipes.

Scope

Documentation and an issue form only. No changes to runtime behavior, effort policy, or benchmark claims. The example describes how to place a check; the current runner does not choose or schedule these checkpoints for the user. The issue form becomes available after merging to the default branch.

Verification

Reviewed the content against the current README, check adapters, and repair loop. Runtime tests not run (no runtime changes).

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