PROOF / FIELDCODE VERIFICATION NOTES

Interactive tool / local only

A verification plan
for your next change.

Choose a stack and a risk level. Get a checklist and an editable CI starting point. Your selections stay in this browser.

Commands assume the project conventions shown in the output.

Higher risk adds review and specification requirements.

Scale changes the test selection strategy, not the definition of correctness.

No account, code input or source upload. Review the generated commands before using them.

Your verification plan

Default example: JavaScript / TypeScript, ordinary application behavior, single package. JavaScript updates this plan when you change the controls.

JavaScript / TypeScriptOrdinary application behaviorSingle package / service

# Verification plan

Stack: JavaScript / TypeScript
Risk: Ordinary application behavior
Scope: Single package / service

## Assumptions
Use Node.js 22, a committed package-lock.json, and npm scripts named lint, typecheck and test. Adjust scripts for a JavaScript-only project.

## Review checklist
[ ] State expected behavior and rejection cases in the pull request.
[ ] Read changed code, callers, configuration and relevant schemas.
[ ] Add a regression test that fails for a plausible wrong implementation.
[ ] Exercise boundary values and the failure path.
[ ] Run deterministic checks and save commands, versions and results.
[ ] Review dependencies, secrets and external input handling.
[ ] Run the complete package test suite before merge.
[ ] Reproduce candidate AI-review findings before accepting them.
[ ] Document uncovered risks, an owner and a follow-up date.
[ ] Have a person approve the evidence before merging.

## Starting commands
```sh
npm ci
npm run lint
npm run typecheck
npm test
```

## GitHub Actions starting point
# STARTER ONLY: configure project scripts and dependencies before use.
# The checklist's security, integration and human-review steps are not automated here.
# Review action releases and pin approved commit SHAs in your production workflow.
name: Verification starter
on:
  pull_request:
  workflow_dispatch:
permissions:
  contents: read
jobs:
  checks:
    runs-on: ubuntu-latest
    timeout-minutes: 20
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '22'
          cache: npm
      - run: npm ci
      - run: npm run lint
      - run: npm run typecheck
      - run: npm test

## Limits
This plan was generated locally. No code was inspected and no checks ran.
The CI job only runs the commands above; configure additional checks from the checklist.
Review untrusted code in an appropriate isolated environment. Never expose secrets to it.

References:
https://ailargescalecodeverification.sbs/guide/
https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions

What this output means: the plan is editorial guidance. The CI file runs a starter set of tests for the selected stack. You must configure dependencies, project scripts and additional security or integration jobs. No test has run on this website.

Download the default example

These fixed files use JavaScript / TypeScript, ordinary application behavior and a single package. They do not change with the controls above. For your current selections, use Download .md or Download CI .yml beside the plan.

Download default example .mdDownload default example CI .yml

Choose the assumptions, then wire up CI

The JavaScript / TypeScript plan assumes Node.js 22, a committed package-lock.json and npm scripts named lint, typecheck and test. If your project uses plain JavaScript, adapt the type-checking step. Python assumes Python 3.12, requirements.txt and pytest. Go reads its version from go.mod; the race detector needs a supported runner and CGO.

Choose ordinary application behavior for a routine feature change. Select authentication or sensitive data when the change crosses an access or privacy boundary. Money movement or critical logic adds invariants, concurrency and recovery checks. These labels express review needs; they do not calculate a risk score or prove that the checklist is complete.

Run the listed commands in your repository before adding the CI file. Adjust dependency installation, scripts and package paths until the checks match your project. Put the reviewed YAML file in .github/workflows/verification.yml and test it through a pull request. The starter also includes a manual trigger. Follow GitHub’s workflow documentation and Actions security guidance; review action versions and pin approved commit SHAs for production.

The YAML automates only its listed commands. Add the integration, security and human-review steps your change needs, then retain the run results with the pull request.