Organetic emblem Organetic Verification layer for AI reasoning
Menu

Docs / Quickstart

First 10 minutes with the released validator line

Use this page to understand the narrow Stage 1 surface, run the shipped CLI, and confirm the expected --help, canon, and golden outcomes.

The examples below assume the current Windows release bundle layout and the shipped sample paths: examples/sample.tsubasa and examples/golden/fixtures.json.

Install and usage Read diagnostics
What Stage 1 is

Installable validator CLI for canonical ASCII output, current _h hash output, deterministic diagnostics, and golden/conformance execution.

What Stage 1 is not

Not a runtime, not a backend, not a verification API, and not a broad Organetic platform surface.

What success means

canon produces CANON: and HASH:. golden reports OK (<n> fixtures).

First run path

Use the shipped bundle before trying partner-owned material

  1. Open PowerShell in the extracted bundle directory Keep the bundle intact so the shipped sample and fixtures stay available.
  2. Run .\tobi.exe --help Confirm the narrow released command set: product banner, canon, and golden.
  3. Run canon on the shipped sample Start with .\tobi.exe canon .\examples\sample.tsubasa.
  4. Run golden on the shipped fixtures Then run .\tobi.exe golden .\examples\golden\fixtures.json.

PowerShell

Release-accurate command shapes

.\tobi.exe --help

.\tobi.exe canon .\examples\sample.tsubasa
CANON:
atomic{ let x = 1 in x }
HASH:
7f13d4e2

.\tobi.exe golden .\examples\golden\fixtures.json
OK (45 fixtures)

The exact canonical body and current hash depend on the accepted artifact, but the output shape should remain stable under the current validator contract.

Help surface

Check the CLI before anything else

The first healthy signal is that .\tobi.exe --help resolves cleanly and identifies the released product line as AI Verification Engine / Tobi Validator.

Canon output

Read accepted input correctly

CANON: is the stable canonical ASCII body. HASH: is the current user-visible _h surface for that accepted canonical artifact.

Golden output

Read conformance correctly

OK (45 fixtures) means the shipped fixture corpus matched current validator behavior. A mismatch is a conformance failure, not automatically a platform failure.

If the first run fails

Check the narrow operator path before escalating

  • if tobi.exe is not found, run commands from the extracted bundle directory
  • if shipped examples are missing, unpack the full archive again and keep its layout intact
  • if checksum verification fails, stop and re-download the bundle
  • if golden mismatches, confirm you used the shipped fixtures first

After quickstart

Move from first run into diagnostics, workflow fit, or deferred evaluation details

Once the shipped sample succeeds, the next useful moves are narrow: understand the install assumptions, read diagnostics correctly, and review the GitHub-first workflow path around the released validator line.

Install and usage Diagnostics reference GitHub workflow fit