IntentLang: OpenThunder proves the repo matches your intent

Start with the downloadable refund walkthrough.

IntentLang lets you declare what software must do, why it matters, what must never happen, and how it must be verified. In the Skills Tech stack, each product proves one thing:

OpenThunder does not compile IntentLang

OpenThunder is not the compiler. It does not parse .intent files or build the Intent AST. It consumes the SkillsTech Compiler's JSON artifacts and compares the declared intent against the observed implementation it already derives from your code (routes, events, tables, security signals). The compiler is the source of IntentLang syntax truth.

If a repo has .intent files but no compiler artifacts, OpenThunder tells you to run the compiler (intent build) rather than guessing.

What OpenThunder gives you

Enable it

The integration is off by default. Turn it on with an environment variable:

OPENTHUNDER_INTENTLANG=1

Then the endpoints GET /api/intent/inventory and GET /api/intent/pack (both take ?projectPath=) return the inventory and the safe pack. Everything is deterministic and local; no source code leaves your machine, and nothing is included in the pack except summaries and artifact references.

Test a contract against your application

In builds containing intent test-app, bind a ThunderLang decision to a reviewed Node adapter in .openthunder/application-tests.json. Preview the cases first, then execute them locally:

openthunder intent test-app
openthunder intent test-app --trust-application
openthunder intent test-app --base origin/main --trust-application --json

The contract supplies inputs and expectations; the adapter calls your existing application. Results show expected and actual values, the tested commit, and hashes of the listed files. This tests the declared cases, not all application behavior. intent prove continues to test the contract itself.

The refund example in examples/refund-contract/README.md demonstrates an application-only off-by-one error: the $100 case fails even while the contract's own cases pass. It also documents adapter setup, review-base protection, local execution trust, and CI exit codes (0 passed, 1 failed, 2 not checked).