Early build · concept art and texel editing in one workspace
Concept in.
Editable asset out.
Texel Fab is a workshop where a concept image becomes a grid-native 3D asset that you, and the agents working with you, can refine, remix and ship. Blocky on purpose, readable as source, compact enough to live on-chain.
Warming up the gate
The loop
Six steps, one document. A manual modeler and someone directing an agent work on the same asset through the same rules.
-
01
Concept
Generate or import an image. Set a base style once so a whole set reads as one family.
-
02
Extract
Lasso a subject and lift it into its own study, traced back to the scene it came from.
-
03
Author
Turn pinned references into a texel model through the Pi authoring pipeline.
-
04
Refine
Edit parts by hand, or hand the same document to an agent. The rules don't change.
-
05
Revise
Every result is an immutable revision. Branch it, make variants, assemble kits.
-
06
Release
Publish a retained release and say what reuse is allowed. Sharing and remixing come later.
The medium
Texel assets are small, deterministic, and legible. What you see in the editor is what's in the file.
-
Grid-native geometry
Cuboids and two-sided planes in integer texel units, placed on an eighth-unit grid, rotated in whole degrees.
-
One texel per unit
Textures are painted onto faces, not projected. A face that measures 8 by 4 holds exactly 32 texels.
-
Palettes of 32
Asset-local RGBA palettes, indexed at the smallest width that fits. Constraint is the style.
-
Legible parts
Generated work stays editable source: named parts, hierarchy, and rigs you can read and change.
-
Same rules everywhere
Web, desktop, automation, and hosted execution share one document kernel. No adapter has its own editing rules.
-
Reconstructable from the file
A complete asset can be stored on-chain and rebuilt without a model, texture, or metadata service.
Provenance, not vibes
Every image and every revision records the exact inputs that made it: prompt, style, mask, model, versions, output hashes.
- A generation job produces a candidate revision. Applying it accounts for the revision it started from, so a finished job never silently replaces what you're looking at.
- History is how you move between states. Edits append revisions; nothing rewrites a parent.
- Reference lineage is recorded, and by itself grants no rights. Economics and licensing stay open until the product assumptions are tested.
The logo is an asset
The mark is a 16-unit cube of the Proving Ground checker, generated by code as a canonical asset file, then rasterized into every icon on this page. Open it in the editor and paint it.
13 colours · 1 primitive · 1536 texels
Loading the asset file…
Where it stands
The first workspace is ready: model and paint editable cuboids, import concept images, and keep private revision checkpoints. Model generation is available to enabled accounts. Concept creation, live agent collaboration, and public sharing are still in development.