What Stage 1 includes
Current released contour
- installable validator CLI
- canonical ASCII output
_hcompatibility identity output- deterministic diagnostics
- conformance and golden execution
- thin packaging and install / usage framing
AI Verification Engine / Tobi Validator
A validator-first CLI for canonical reasoning verification
Tobi Validator is the first released Organetic product. It is designed to canonicalize, identify, and validate reasoning artifacts in a deterministic workflow-friendly way.
What Stage 1 does not include
Still intentionally narrow
- not a mature runtime or backend platform
- not a broad orchestration suite
- not a shipped verification API surface
- not the complete Organetic platform
- not a Stage 2 public product surface
Who should evaluate this now
Tobi Validator fits teams that need a narrow workflow gate
Stage 1 is most useful when a team already has artifacts that should be accepted, rejected, canonicalized, or compared before merge, release, tool action, or expensive downstream computation.
AI / agent teams
Gate agent-produced reasoning artifacts
Use Tobi before an agent output becomes a tool action, configuration change, merge candidate, or preserved reasoning artifact.
Developer tools / CI
Validate before merge
Add a validator-backed gate to GitHub Actions or GitLab CI/CD and treat deterministic diagnostics as part of review evidence.
Scientific workflows
Protect reproducibility-sensitive steps
Use a narrow validator step before downstream computation where unstable artifacts would create expensive or hard-to-debug failures.
Evaluation teams
Separate evaluation from verification
Keep scores and traces, but add a separate artifact validation boundary for canonical
output, _h, diagnostics, and conformance behavior.
Reasoning artifacts
What Tobi is trying to stabilize
A reasoning artifact is not just any smart-looking output. It needs to be explicit, reviewable, repeatable, and meaningful enough to accept, reject, or compare inside a workflow gate.
Tobi matters when a team wants artifacts to become more canonical, reproducible, and validator-checkable instead of remaining trace-like and hard to compare.
Canonical convergence
Equivalent valid forms should not create false drift
A useful validator does more than reject broken input. It also collapses equivalent valid forms into one stable canonical result instead of preserving spelling-level noise as a fake semantic difference.
Agent governance vs artifact verification
Workflow control is not the same as reasoning verification
Some AI-agent systems focus on delivery governance: approval gates, review steps, event logs, evidence packs, and workflow completion rules. That is useful operational control.
Tobi Validator sits at the artifact boundary. It asks whether the reasoning artifact itself can become canonical, reproducible, and validator-checkable before a workflow treats it as trusted output.
Organetic distinction
Process evidence and artifact evidence are different
- Agent workflow governance controls process, approvals, and delivery gates.
- Tobi Validator validates reasoning artifacts through canonical ASCII, compatibility identity, deterministic diagnostics, and pass/fail behavior.
- Hash-chained logs and review packs are operational evidence, not canonical reasoning artifacts.
- Human approval is useful, but it is not deterministic validation.
Public GitHub path
Public repo for docs, examples, and the action wrapper
The public repository at OrganeticSphere/tobi-validator is the customer-facing
surface for the released validator line. It carries docs, examples, workflow guidance, and
the GitHub Action wrapper used as uses: OrganeticSphere/tobi-validator@v1.
Real execution remains controlled and separate from the public repo. The public path is repo plus wrapper guidance, not unrestricted full-binary download.
Trust and openness
Open conformance corpus
Tobi Validator Stage 1 now has a public conformance corpus for .tsubasa
artifacts. The corpus provides public-safe examples and real-run expected outputs,
making validator behavior inspectable without publishing the private engine/core.
The validator implementation remains private, authorized execution is still required to run Tobi Validator, and the corpus is not full Tsubasa language coverage.
Integrations
Current public workflow paths
GitHub Actions
Use OrganeticSphere/tobi-validator@v1 as the narrow GitHub workflow wrapper with controlled execution.
GitLab CI/CD
Use the published GitLab CI/CD Catalog component
organetic/tobi-gitlab-component/[email protected] for controlled
canon and golden checks.
Nextflow
Scientific workflow-fit context for reproducibility-sensitive evaluation.
Evaluation contextSnakemake
Rule-level validator fit discussion rather than a current public launch surface.
Evaluation contextDatabricks / MLflow
Secondary workflow context for teams already using managed tooling.
Secondary contextWorkflow fit
Use a controlled wrapper path before broader evaluation
The current public paths are narrow: understand the product, use the released docs, and test GitHub or GitLab workflow fit.