XO3D ONE: the studio in one workspace. From planning to production.

Leadership uses a different view from the production team. Management organises the day around Run the day, Money and demand, Delivery and people, System, Agents and Jupiter.

The purpose is to bring priorities, commercial context, delivery exceptions and operating checks into one place. The nine-agent team provides a named route into the responsibility behind a recommendation, rather than leaving leadership with a single dashboard score.

Production combines project boards, planning timelines and a detailed project workspace. Users filter by person and project type, follow the current stage, and open the exact project from a card or their own dashboard.

Project detail brings together the owner, assigned team, final delivery, health, next action and blocker. The seven client stages are Briefing, Greys, Materials, Render, Post, Review and Delivery. In-house work has its own stage sequence.

Stage dates and delivery parts are separate. A part has its own owner, start, due date, confirmed or estimated dates and completion state. One part can represent the final delivery, so a project deadline does not have to stand in for every handoff.

My Dashboard brings Overview, Needs attention, My projects, Agents, Time blocking, Coming up, Email triage and Waiting on others into a person-specific workspace.

Project cards open the exact assigned project. Agent suggestions and upcoming work sit alongside the dependencies that prevent progress, so a person can move from a summary into the record behind it.

Time blocking proposes a plan rather than silently changing a calendar. Email and personal-calendar cards report missing access honestly. A production-lead email assistant has a verified draft-only projection; that does not mean every staff mailbox is connected.

Production includes a Files and review workspace for browsing project files, versions, folder policy and connection state. Internal review and client feedback have different lanes.

The implemented review workflow supports still-image and paused-frame video markup, threaded replies, blocking notes, resolution and reopening against an exact version. Opening an older version for inspection does not change which version is selected.

Client feedback belongs to a deliberately published file version. Private team notes are not part of that client view. The separate Review product remains in development, with live client activation and production acceptance still to prove.

The shared Calendar shows recorded leave and public holidays in a month view, with filters for person and entry type. Multi-day leave appears as a continuous bar across the relevant dates.

Request time off collects the first and last day, leave type and an optional note. Staff see their own requests; authorised reviewers see the review queue. Pending, approved, rejected and cancelled states remain distinct, and a person cannot approve their own request.

Approved Studio requests feed Who's out and the production leave projection. That makes an approved absence visible beside delivery planning. The absence view is not a full Outlook replacement, and an empty result does not establish that everyone is available.

Jupiter is the conversational entry point into permitted company context. Saved chats, pinned conversations and visible history let users return to an ongoing question rather than starting again from a dashboard screenshot.

A weekly-delivery question can use the current production schedule directly: dated milestones, final deliveries, assigned people, blockers and conflicting dates. The deterministic schedule answer is separate from a general model response.

Jupiter can prepare a holiday-request card, find an Artist Tool and show the button that opens it, or guide authorised founders through new-project intake and explicit approval. Preparing a card is a different step from submitting a request or creating a job.

The interface also supports editable email-draft cards, account-dependent staging, answer receipts and feedback. Chat access and tool access remain tied to the user's permitted role; Jupiter is a controlled pilot rather than an unrestricted assistant for every account.

Artist Tools combines searchable categories, favourites and an Internal apps lane. The current catalogue defines 41 Labs utilities and guides, covering image preparation, textures, lighting, modelling, colour, planning, delivery and viewers.

Examples include Image Compressor, Image Resizer, Normal Map Creator, Texture Resolution Calculator, PBR Material Checklist, Depth of Field Calculator and GLB Viewer. Guides and calculators are distinct from tools that process files.

Eight internal entries describe more specialised production work. Their cards explain what they do, how to open them, what they require and what remains unfinished. The following tools deliberately have different maturity levels.

Video Processing uses a source monitor, trim track, grouped output settings, latest-export panel and persistent processing bar. It provides three fixed MP4 presets: 1080p landscape, square and vertical.

Preflight explains aspect-ratio padding before processing. Optional start and end values are checked against the source duration. Progress, cancellation and output reveal belong to the installed local workflow.

Local processing can be enabled or disabled per device. A real encode has been verified in the installed application; cloud and office targets remain unavailable until their services are connected.

The local Whitebox Rendering beta accepts common mesh formats, automatically frames the model, applies neutral white material and controlled studio lighting, then renders a transparent PNG.

Users choose a fixed hero, front or left camera and a 1920-square preview or 4096-square output. The local renderer is installed and enabled deliberately on each device; output checks cover PNG format, dimensions and alpha.

This is the working neutral-rendering path. Reference-photo material assignment, final-material rendering, CAD conversion and remote processing are separate unfinished capabilities.

The current tool is a calibration and annotation workspace for Grey Card, Material / Lighting and Post images. Reviewers pin issues to the render and choose from 36 fixed defect codes.

Severity produces Pass, Minor notes, Revise or Reject outcomes. Clean and cannot-assess examples can be recorded, and image-free annotation records can be exported for later scoring.

The active calibration build keeps image pixels in the browser. Automated vision analysis stays locked until approval, labelled evidence and measured quality justify enabling it. Composition and final release judgement remain with a senior reviewer.

The material workbench combines colour generation or local image import with map preparation, border trimming, rotation and repeat previews.

Its generation development has produced seeded 1024px colour images. Height and normal maps are derived from a shared smoothed field, with artist-set roughness and metalness. The export includes five PNG maps, provenance, hashes and loading notes.

Those maps approximate material behaviour. Repeat previews expose seams; they do not certify seamlessness or measured physical properties. Production deployment, installed verification and artist quality acceptance remain pending.

The testing interface accepts a written brief, a reference image or both. Its intended bounded workflow plans geometry and materials, builds an editable scene, inspects rendered previews and attempts corrections.

The output contract includes a Blender scene, a GLB model, two rendered views and a quality report, with up to three build-and-review attempts.

The tool remains in testing. End-to-end installation and live acceptance are pending, and complex shapes need artist review. A model produced in a separate authored commission is not evidence of unattended generation in this tool.

The director pilot describes typed Photoshop edits with an immutable source, an editable PSD and a separate export.

The interface exposes proposed-edit review, job progress, preview and output download. A working licensed Photoshop session and connected worker are required; other Adobe applications need their own verified adapters.

The development entry describes a STEP-to-web-and-AR packaging pipeline with geometry checks, bounded repair, mesh optimisation and traceable quality evidence.

Its documented target outputs include GLB, USD and USDZ plus configurator manifests. Restartable job state is part of the design, so interrupted work can be traced and resumed.

The entry remains in development. Early control and ledger work has been locally verified; native topology, tessellation and completed packaging are not yet proved. There is no live distributed tool to claim.

Nine specialists cover the chief-of-staff role, leads, sales, marketing, delivery, finance, people, data trust and operations. Team chat makes standups and handoffs visible; individual conversations show the work in context.

Job explains each responsibility and authority. Routines exposes recurring work and recorded runs. Tasks makes current work inspectable. Reports, next moves and checks sit beside the conversation.

A bot can be working, on job or in need of a fix. A fresh summary is useful only when the underlying result and source remain valid. The design keeps human review and role-specific action permission separate from a chat reply.

Intel is the website-intelligence area of the same application. Findings connect to the page, source evidence, scoring and limitations behind the summary.

Its role is to help a user decide which website issue deserves investigation or action. It keeps evidence and freshness visible rather than presenting a score as proof of a business result.