Vadik’s project desk

Open a project. Follow the work.

Open-source alpha Developer tools

Synrail

Evidence checks for coding agents.

THE FALSE-GREEN DEMORecorded walkthrough
Claim recorded

“Fixed add();
tests pass.”

Submitted evidencegrep found the fast-path line

A matching line of code doesn’t tell us whether the behavior works.

Verification failed

The test
still fails.

$ synrail verify
Verification unit: FAIL (exit 1)
$ synrail check
Synrail: Status: Verification Failed

Running the check exposes what the text search missed.

Accepted after repair

The repair passes
verification.

$ synrail verify
Verification unit: GREEN
$ synrail check
Synrail: Status: Accepted

The repaired behavior passes verification. The work can now be accepted.

Watch the original 0:08 ↗
Walk through the recorded example above. No commands run in your browser.Try it locally ↗
Latest project noteLooking at what a pull request can change

Research implementation Onchain research

RHOOK

Replay execution after one changed input.

INSIDE A REPLAYConceptual model
Recorded sequence
Recomputed execution
X → X′
One declared intervention

The input changes here. The checkpoint and historical transaction order stay fixed.

3 / 5
This diagram explains the model; it does not run a blockchain replay.Reproduce the 50-block example ↗
Latest project noteA reproducible replay on Robinhood Chain

Production workflow AI filmmaking

Second Unit

An agentic film crew, from brief to final cut.

Production workflowExplore the method
01 / 06 · Prepare

Give the film a direction.

Start with the brief, budget and acceptance criteria. Analyse references for composition, light, colour and rhythm, then turn those observations into a story and a shot plan.

Starts with
Brief, constraints, budget
Leaves behind
Measured refboard and story beats
Review
Does each shot have a purpose, a clear action and a place in the story?
Your decision
Approve the direction and story.
02 / 06 · Establish

Keep a shared picture of the scene.

Approve character and location masters. Record the features that must remain consistent, the action axis, light direction and prop states. Each new shot starts from its master.

Starts with
Approved story and references
Leaves behind
Character masters, canon and scene map
Review
Character features, screen direction, light and prop scale stay consistent.
Your decision
Approve the masters and keyframes.
03 / 06 · Generate

Explore in drafts. Keep the accepted take.

Build keyframes with a declared camera, subject, action and change over time. Explore motion in inexpensive drafts. Keep accepted takes as source files for the final edit and upscale.

Starts with
Approved keyframe and job specification
Leaves behind
Motion drafts and contact sheets
Review
Inspect the usable window, physical contact, faces, hands and movement.
Your decision
Choose the take that belongs in the cut.
04 / 06 · Review

Judge the shot inside the film.

Inspect contact sheets and details, then watch shots inside the cut. Separate reviewer agents check framing and physical contact, continuity and motivation, and colour across the sequence.

Starts with
Draft takes, scene map and director’s notes
Leaves behind
Timecoded findings and a revised cut
Review
A plausible frame can still fail in motion or at the next cut.
Your decision
Accept, redirect or request another pass.
05 / 06 · Finish

Finish the version you approved.

Assemble the edit with versioned scripts. Match colour outliers, apply the look, and add grain at delivery size. Check the exported file and keep a no-music version where required.

Starts with
Approved cut and accepted source takes
Leaves behind
Delivery master and rebuild records
Review
Review the whole sequence, export metadata and delivery format.
Your decision
Sign off on the cut, look and delivery.
06 / 06 · Carry forward

Make the next film start with more context.

Record rejected takes, the reason, the proposed fix and whether it worked. Accepted references and A/B preferences become material for the next review. Proven fixes move into the shared rules.

Starts with
Failures, accepted shots and A/B preferences
Leaves behind
Relevant fixes, review rules and regression references
Review
A correction keeps its outcome and the feedback that caused it.
Your decision
Set the taste through concrete verdicts.
Human approval at the creative decisions.Each film feeds the next ↶
A walkthrough of the production method. No generation runs in your browser.
The learning loopWhat a rejected colour pass changed in the next review

Turing Test 2026 AI & onchain systems

TuringVault

Proposals, checks, and execution records on Mantle.

FOLLOW THE DECISIONWorkflow guide
The TuringVault agent console, captured 29 September 2026.Open full screenshot ↗
An analyst proposes an action.

The proposal becomes part of an inspectable decision trail, before anything executes.

Operator-funded demonstration on Mantle. No public deposits.Open TuringVault ↗
Mantle Turing Test2026Project Deployment Award & Demo Day

Built over time, from Telegram bots to agent tooling and onchain experiments.

Development notes ↗

Synrail / the original recording

A recorded run from the public repository. Read the transcript