BLENDER EXTENSION 0.7.1 · ALPHA
Alepou gives a project-bound AI session an inspectable way into Blender: real source research, native scene authoring, exact geometry queries, deterministic visual evidence, focused repairs, and accepted .blend artifacts.
Not text-to-mesh. Not a one-prompt asset generator. The retained source scene stays editable in Blender.
What actually happens
The bridge is not a hidden generator. It connects a durable Alepou task to a visible Blender session, records what ran, and gives the worker enough exact and visual evidence to judge what it made.
Find strong sources, freeze the exact variant and date, record dimensions, construction clues, and honest unknowns.
Split a complex object into meaningful component tasks. Assembly comes after accepted parts, not before them.
Alepou can launch or connect to the project’s Blender instance and establish a fresh, session-owned authoring contract.
The worker chooses Blender Python, BMesh, modifiers, curves, materials, collections, empties, or other native techniques appropriate to the asset.
Bounds, mesh statistics, distances, alignment and intersections sit beside clay, silhouette, wireframe and studio views.
Concrete defects are revised until the evidence holds up. The accepted source artifact is saved for later project tasks and Unity assembly.
A real rejection, not a victory lap
The first direction was overexposed, too modern, and did not establish the exact model. It was rejected. Research then locked the December 1998 Casio HR-170LB GYB, including its published 162 × 271 × 61 mm dimensions, before the asset was rebuilt and checked again.
The same frame moves from a rejected generic direction to inspected native geometry and the accepted reconstruction.
Rejected — wrong direction.Exact identity unproven · form too modern · lighting hid the surfaces.
The acceptance record keeps the limitations too: this is an exterior production reconstruction, not a claim that undocumented internal mechanisms were invented correctly.
The difference is focused attention
A broad task produced a recognisable but generic computer. The later workflow researched the mouse, keyboard, display and tower as separate subjects, accepted each component, then assembled the workstation.
BROAD TASK
FOCUSED COMPONENTS
This is production evidence, not a controlled benchmark. Prompts, research, iteration and presentation evolved too. Both scenes were authored natively in Blender; the stronger result came from sources, task decomposition, exact and visual review, and protected assembly.
The Unity scene, rebuilt as a web exhibit
This is the actual researched production geometry, reassembled from the Unity scene contract and exported from the accepted Blender source. It is not a generated mesh, a lower LOD, or a flattened turntable.
Front-facing hero by default. Orbit for the sides and rear; switch to wireframe to inspect the same geometry.
The freestanding organiser visible in the wider Unity room remains preserved in the source project, but it is excluded from this desk exhibit because it is not part of the workstation composition. The rear image is evidence, not the default hero angle.
One project, many accepted components
The reconstruction targeted the 2011 assembly-complete station. NASA sources fixed the configuration and real scale. Component tasks covered the truss, arrays, radiators, nodes, laboratories, international modules, Russian segment, mobile servicing system, game hierarchy and LODs.
Visual and exact review found real problems: truss proportions, weak array span, radiator attachment, docking interfaces, overlapping modules, an upside-down Cupola, Russian-segment collisions, and an undersized Canadarm. Those defects were repaired before the master artifact was accepted.
Reference lock + scale basis
DONEIntegrated truss structure
ACCEPTEDSolar array wings + masts
ACCEPTEDModules, nodes, robotics + interfaces
ACCEPTEDMaster assembly + exact checks
12 / 12Final lighting, materials + evidence
DONEWhen one Blender session closed before the scene was saved, the recorded component scripts made recovery possible. The scene was rebuilt from the audited authoring record rather than guessed back into existence.
Retained 90s Office production evidence
These viewers use retained acceptance captures from a project built across hundreds of commit-linked tasks. Switch the evidence, zoom in, then drag or use the arrow keys. The original .blend files remain the source artifacts handed forward to Unity.
Accepted hero against the silhouette used to review the complete plant envelope.
Accepted overall form and a closer mechanism view for the yoke, cap, shade and pivots.
The calculator sequence above uses a retained wireframe capture that reads clearly at web size. The plant silhouette and lamp mechanism view are different inspection evidence, labelled as such rather than dressed up as topology proof.
Local, inspectable architecture
A project carries a compact file contract under plan/blender/. Observations are bounded and mutations are recorded. Blender executes authoring work from its main-thread timer, while Alepou tracks the originating session, terminal result, recovery state, and evidence.
Local Trusted Development is powerful delegated authority, not a security sandbox. It belongs on trusted projects with version control, explicit session ownership, and acceptance based on evidence rather than a successful command alone.
Read the bridge architecture
bridge-health.jsonfreshness + ownershipscene-summary.jsoncompact scene statequeries/pending/bounded observationcommands/pending/recorded mutationapplied · failed · rejectedterminal outcomeAlepou Blender Bridge
Blender remains Blender. Alepou adds durable project context, controlled access, recorded execution, and a review loop that can survive long-running work.