AI Pilot Experience · Conceptual 3D

Conceptual 3D Asset or Interaction

Generate or assemble one visibly conceptual object or environment for a reviewed presentation, interaction, or workflow demonstration with deterministic structural checks and human release.

Start Free Workflow Assessment Review Bounded AI Agent Pilot

Operating brief

Starting point: One approved concept brief, source assets, rights, intended interaction, visible conceptual label, technical checks, and reviewer.
Pilot output: A reviewed conceptual asset or interaction with source, model, scene, script, validation, capture, correction, and release records.
Authority: People approve the concept, rights, structure, behavior, disclosure, and release; the output creates no measured, design, construction, logistics, or safety authority.

Pilot experience

See what the user does, what the system prepares, and what the pilot must prove.

A conceptual object or environment can support presentations and workflow demonstrations where plausible appearance and interaction are useful but measured project geometry is not required.

Hunyuan3D, TRELLIS, Rodin, Blender, Three.js, Godot, or controlled Unreal import can prepare or assemble assets. The workflow retains source identity, licences, units, hierarchy, transforms, materials, scripts, exports, tests, captures, and corrections.

Reviewers confirm conceptual status, rights, visual fit, structure, behavior, performance, and prohibited implications before release. The result remains separate from BIM, survey, fabrication, simulation, and approved project records.

Visual walkthrough

Follow the workflow, review interface, evidence, and decision states.

Each view shows how source records, system outputs, exceptions, corrections, and human decisions remain connected during the pilot.

Conceptual 3D workflow. — Conceptual 3D workflow
Approved inputs remain connected to preparation, deterministic checks, human review, acceptance, and release.

Asset and scene register. — Asset and scene register
Stable source, run, output, version, evidence, correction, and review records remain visible.

Geometry and interaction review. — Geometry and interaction review
Reviewers inspect claims, actions, files, dependencies, geometry, behavior, and prohibited implications before acceptance.

3D exception queue. — 3D exception queue
Uncertainty, failure, permission, security, rights, validation, and stop conditions receive named owners and states.

Approved concept package. — Approved concept package
Only accepted outputs move to the approved audience or next controlled environment.

User journey

Move from approved collection to source-linked review through explicit stages.

The interface can feel simple while the pilot preserves document identity, revision, permission, retrieval, uncertainty, and review evidence behind every result.

Approve concept brief

Define audience, purpose, object or environment, interaction, source references, rights, exclusions, conceptual label, and release owner.

Register source assets

Record identity, origin, licence, permission, scale status, coordinate status, people, brands, products, and permitted influence.

Select build route

Choose generative asset, procedural Blender, Three.js, Godot, or controlled Unreal import by output, control, editability, tests, cost, and exit.

Generate or assemble

Record model, tool, version, settings, prompts, scripts, assets, units, hierarchy, transforms, materials, animations, collisions, and interactions.

Validate structure

Check files, parse, scene load, expected objects, naming, hierarchy, scale assumptions, transforms, materials, textures, animation, collision, and export.

Validate behavior

Run bounded input, state, navigation, interaction, reset, performance, log, frame, and nonblank-render checks.

Human review

Inspect conceptual label, rights, visible fit, inferred geometry, behavior, unsafe implications, limitations, and release purpose.

Approve release

Freeze source, manifest, build scripts, assets, exports, tests, captures, corrections, reviewers, version, audience, expiry, and withdrawal.

Technology options

Choose each component for a defined task and accepted output.

The final selection records exact versions, licences, data handling, cost, limitations, replacement options, and the evidence required before use.

Component	Examples	Pilot role	Boundary
Hunyuan3D	Verified Hunyuan3D model, service, checkpoint, dependencies, and licence	Prepare plausible conceptual mesh and texture candidates.	Generated geometry, hidden surfaces, scale, topology, materials, and identity are inferred rather than measured.
TRELLIS	Verified TRELLIS model, checkpoint, dependencies, licence, and environment	Prepare image-to-3D concept assets where plausible completion is acceptable.	A visually complete asset does not establish geometry, dimensions, products, BIM semantics, or construction truth.
Rodin	Current verified official Rodin route and terms	Remain an eligible conceptual asset candidate after identity, API, rights, privacy, cost, and evaluation review.	A demo or hosted output is not sufficient evidence for approved project use.
Blender and Three.js	Versioned Blender scripts, glTF export, Three.js scene, controls, tests, and captures	Assemble, edit, validate, export, and present conceptual assets with reproducible structure.	Deterministic assembly cannot make unmeasured source geometry accurate.
Godot or Unreal Engine	Controlled import, scene assembly, scripts or Blueprints, packaged interaction, logs, and captures	Create bounded interaction or presentation environments after validated import.	A running scene is not validated simulation, logistics approval, method approval, or safety evidence.

Client-owned pilot outputs

The pilot closes with evidence and a decision, not just a demonstration.

Concept, audience, purpose, object or environment, interaction, source, rights, exclusions, disclosure, and release definition
Source identity, origin, licence, permission, scale, coordinates, people, brand, product, and permitted-influence register
Exact model, checkpoint, tool, engine, version, dependency, settings, prompt, script, asset, output, retry, and cost record
Units, hierarchy, naming, transform, material, texture, animation, collision, interaction, export, and manifest workflow
Structural checks, behavioral tests, logs, performance measures, fixed-camera captures, and nonblank-render validation
Missing asset, bad scale, broken material, export loss, script error, interaction failure, rights issue, and false-implication queue
Simple, multi-part, transparent, animated, interactive, import, reset, performance, and failure cases
Correction, rejection, accepted concept, release, expiry, withdrawal, provider replacement, and rebuild states
Quality, structural and behavioral failure, reviewer effort, build time, render cost, and complete cost evidence
Source, scripts, manifests, assets, exports, tests, captures, limitations, runbook, and client-owned handover

Evaluation evidence

Measure retrieval, citations, review effort, latency, and complete cost together.

A fluent answer is not the acceptance unit. The pilot tests whether a reviewer can reach the controlling evidence efficiently and detect important failure.

Source support

Trace outputs to approved sources, actions, files, references, versions, and evidence.

Task completion

Measure completion against frozen cases and acceptance criteria, including difficult and stop cases.

Critical failure

Record unauthorized action, false claim, security event, dependency issue, missing evidence, or prohibited use.

Reviewer effort

Measure inspection, correction, rerun, exception resolution, testing, and approval time.

Accepted output

Count outputs accepted by accountable reviewers, not processing completion or model agreement.

Complete cost

Include models, tools, compute, storage, preparation, testing, review, correction, monitoring, support, and replacement.

Cost drivers

Cost follows document condition, usage, controls, and accepted outcomes.

Source and output volume, formats, revisions, media duration, portals, repositories, assets, scenes, and update frequency
Model, API, browser, compute, GPU, rendering, storage, transfer, build, test, retry, and provider-plan cost
Permissions, rights, identity, environments, schemas, prompts, scripts, fixtures, validation, manifests, and acceptance preparation
Security, privacy, confidentiality, secrets, network, region, retention, training use, dependency, licence, and incident review
Process, technical, security, subject, communications, accessibility, legal, and release review
Corrections, reruns, exceptions, monitoring, support, provider changes, expiry, withdrawal, portability, and handover

Scaling factors

Scale one accepted pattern without flattening project and industry differences.

Volume

Use durable source, run, work-item, output, review, correction, acceptance, release, expiry, and withdrawal IDs with queues and checkpoints.

Permissions

Constrain source, identity, credential, tool, repository, file, network, provider, destination, audience, and action scope.

Environment

Version models, APIs, browsers, tools, packages, dependencies, engines, operating systems, hardware, settings, tests, and policies.

Provider replacement

Keep approved sources, prompts, scripts, records, assets, tests, evidence, corrections, and accepted outputs client-owned.

Concurrency

Measure queues, sessions, rate limits, rendering, build time, timeouts, retries, reviewer capacity, and cost.

Production promotion

Require separate security, integration, monitoring, recovery, service, rights, ownership, training, and deployment approval.

Cross-industry reuse

Reuse the retrieval pattern while changing documents, authority, and review.

The reusable capability is permission-aware multilingual retrieval across versioned documents with citations. Each industry keeps its own source authority, terminology, consequence, retention, and qualified review.