Skip to main content

Auditable research automation

Move from a scientific question to a reviewable analysis contract.

This release links deterministic drafting, qualification gates, model-run lineage, receipt closure and review artifacts while preserving the current evidence ceiling.

01

Controlled task drafting

Turn a research question into an explicit draft contract. Missing dose, time, unit and split fields stay unresolved until a researcher confirms them.

02

Anomaly and leakage gate

Check public-field leakage, dataset/task qualification, model provenance and claim ceilings before a workflow can be promoted.

03

Model-run lineage and diff

Trace every registered run to its comparison baseline and inspect changes in context, split, decision state and evidence ceiling.

04

Reproducible analysis kit

Use the zero-dependency Python client and five clean notebooks for discovery, contracts, baseline review, qualification and report reproduction.

05

Idempotent execution plan

Compile a reviewed draft into a six-stage dependency graph with stable task hashes, retry limits, cancellation rules and required receipts.

06

Receipt verification

Validate task identity, provenance hashes, attempt limits, terminal state and timestamp order without uploading scientific result payloads.

07

Run closure

Verify plan identity, retained retries, dependency order and six-task completion without inspecting the scientific outputs behind their hashes.

08

Run evidence bundle

Bind ModelRun identifiers, run closure and report artifacts into one content-addressed review package while keeping result values and private paths outside the validator.

Natural-language interface

Create a bounded TaskContract draft

Review every unresolved field before using the contract in a registered analysis.

111 / 12,000 characters

Execution contract

Make every transition reviewable before a worker starts.

Stable identity

The TaskContract, runner profile and plan schema produce one content-derived idempotency key.

Dependency gate

Qualification precedes baseline and candidate runs; matched comparison waits for both.

Retained outcomes

Retries keep the same inputs. Scientific changes create a new plan, while failures and cancellations remain visible.

No silent launch

The public endpoint compiles a plan and never creates a queue item or reserves compute capacity.

Receipt verification

Verify provenance structure without exposing result payloads.

The validator accepts one bounded receipt, rejects unknown or private fields and never stores the submitted object.

616 / 32,768 bytes

Run closure

Prove that the dependency graph closed without hiding failed attempts.

The validator binds receipts to one plan identity, preserves identical retries and reports the next eligible, blocked or completed tasks.

4,250 / 65,536 bytes

Review package

Bind run closure to a hash-only evidence manifest.

A complete run becomes review-ready only when its bounded report matches the passing J06 output hash and a manifest artifact is retained.

5,449 / 98,304 bytes

Portable workflow

One kit, governed entry points

Python SDK

Query versioned public objects with Python standard-library networking and explicit error handling.

Download SDK source
Five clean notebooks

Start from public objects, retain denominators and write reports without embedded private paths or outputs.

Inspect file identities
Machine-readable gates

Consume the current anomaly gate, lineage registry and run-diff registry from stable JSON endpoints.

Open the gate result