FIELD / 01THRAIZE / 7HR4IZ3

Ink / Blueprint

Turn the work into a field.

A full evidence atlas for software that crosses boundaries. Six real builds, drawn together without flattening the difference between them.

06approved platesone connected practice
THE FIELD

Screens are coordinates.

Move across the paper to inspect the registration point. Select any plate to open its complete build record.

THRAIZECommon groundwhere incompatible systems become useful
Kaizen Code mobile workspace selection screen
KaizenMOBILE / AI / NATIVE / TOOLING
Snapshot terminal preflight and parallel workspace capture
SnapshotAI / TOOLING
VRMac world-anchored desktop architecture capture
VRMacSPATIAL / NATIVE / MOBILE
Motion Cues Android release screen showing the overlay controls and dots
MotionNATIVE / MOBILE
OpenCode Annotate browser comment routed from a selected interface
AnnotateWEB / AI / TOOLING
Stackjet URL-to-cloud-storage product interface capture
StackjetWEB / CLOUD / TOOLING
HOW TO READ IT

The drawing is a translation layer.

It gives the portfolio a visual grammar without turning a screenshot into a promise it cannot prove.

01

Evidence

Every plate is an approved capture from a real build. The field never invents a product surface to make the story look finished.

02

Translation

Ink lines connect the systems crossed by each build: mobile to native, browser to agent, source URL to cloud storage.

03

Inspection

Every plate is a doorway. Open one and the full build record gives you the problem, constraint, intervention, proof, and links.

THE REGISTER

Six plates. Six different crossings.

Start with the image, then inspect the claim. The register keeps contribution, maturity, and current proof visible at a glance.

  1. 01Kaizen CodeCreatorAndroid runtime proven; iOS bridge remains intentionally fail-closed

    Android app-UID guest runtime executed a real command successfully.

  2. 02SnapshotCreatorWorking CLI with multiple workspace backends

    Supports worktree, APFS copy-on-write, overlay, and automatic backend selection.

  3. 03VRMacCreatorBoth device targets build; live end-to-end validation needs physical hardware

    Swift host builds as a standalone package.

  4. 04Motion CuesCreatorRelease build and store assets produced

    Native sensor overlay, foreground service, notification controls, and Quick Settings tile are implemented.

  5. 05OpenCode AnnotateCreatorPublished browser and agent-session workflow

    One local relay coordinates several OpenCode processes.

  6. 06StackjetCreatorGoogle Drive upload workflow implemented

    Google sign-in and a separate Drive consent flow are implemented.

THE POINT OF VIEW

A screenshot is a proof point. The line tells you why it matters.

The field is how I want to show the work: materially, with context, and with enough room for the uncomfortable parts between a good idea and a dependable system.