Skip to main content
Craft
Arc · Early access

One project intelligence.
Every agent aligned.

Arc gives the entire agent team the same understanding of the building, the brief, the brand, the approved decisions and the production plan. Models and tools can change; the project memory does not.

Watch the agents planRun an enterprise pilot
Arc project frame for Tower B Gulf launch
TOWER B · GULF LAUNCH PROJECT MEMORY LIVE
GeometryLOCKEDMaterialsLOCKEDBrandLOADEDInventorySYNCED
Ada, Scout, Bolt, Lex — one shared context. Forge on Arc 2.0.

GATESTwo approval gates. No credits spent before you approve.

A READABLE DECISION SYSTEM

From one outcome to an approval-ready plan.

Arc names the agent responsible for each decision, exposes the production cost and keeps human authority visible before anything executes.

ARC 1.0 · YOUR OUTCOME

“Launch Tower B for a Gulf audience by Thursday.”

ARC PROJECT MEMORY
GeometryLOCKEDMaterialsLOCKEDBrandLOADEDInventorySYNCED
Every decision stays inspectable.PLAN / MH-TB-042
STEP 01Scout
Map the project inputs

brief · plans · inventory · approved render

4 sources structured
STEP 02Bolt
Lock the project identity

façade · materials · camera · visual rules

identity lock ready
STEP 03Lex
Compile production settings

true 4K · bilingual · regional formats

274 credits scoped
STEP 04Ada
Assemble the governed plan

6 outputs · 2 approval gates · Thursday deadline

ready for review
Tower B plan-to-render deliverable preview
GOVERNED OUTPUT 01 / 06AWAITING HUMAN GATE
Tower B · plan-to-render deliverableBolt identity lock applied · Lex production settings · 0 credits spent before approval
OUTPUTS6
CREDITS274
GATES2
DEADLINETHU
CAPABILITY CHECK · FORGENo missing tool required for this plan.

On-demand tool creation arrives with Arc 2.0 and remains sandboxed until a user approves it.

The plan is editable. Execution begins only after approval.
THE ARC AGENT TEAM

One project memory.
Every role aligned.

Ada directs the outcome. Scout, Bolt and Lex plan the current workflow from the same approved context; Forge is shown separately as the Arc 2.0 roadmap role.

HUMAN OUTCOME

“Launch Tower B for a Gulf audience by Thursday.”

MASTER AGENT · ORCHESTRATING

Ada

Owns the outcome

Owns the outcome, coordinates specialists and controls every approval gate.

READS + WRITES
GeometryMaterialsBrandApprovalsCost
  1. ScoutInput & flow planner

    Understands the request, inventories project files and drafts the production sequence.

    OUTPUT4 inputs mapped
  2. BoltVision agent

    Reads geometry, materials and spatial relationships — including what must not change.

    OUTPUTIdentity locked
  3. LexParameters agent

    Sets references, influence, resolution, model selection, cost and quality thresholds.

    OUTPUT274 credits scoped
  4. ForgeCoding agent

    Will build, test and present a scoped tool when an approved workflow needs a capability that does not exist.

    OUTPUTArc 2.0 roadmap
Every step, its cost and its owner, before you approve.
Compiled AEC intelligence

What every agent can draw from

Six shared intelligence modules — so AEC knowledge isn't rebuilt in every prompt.

01 / 06 · Photorealism intelligenceCOMPILED ONCE

What "real" means to a trained eye — material response, texture scale, light behaviour, lens character — compiled once, applied to every generation, never prompted from scratch.

MATERIAL RESPONSELIGHT BEHAVIOURLENS CHARACTER
Forge · Arc 2.0 roadmap

A missing tool shouldn't end the workflow.

Forge is being designed to turn a future requirement into a scoped, tested tool and wait for approval. It is not part of the current Arc 1.0 execution path.

FORGE · TOOL BUILDTESTS 12/12
01specavailability-map from inventory.xlsx
02bindunit_id → floorplate polygon
03guardread project files · write preview only
04test12 passed · 0 geometry mismatches
05awaituser approval before execution
Scoped tool ready
  1. 01Need detected

    Ada finds a missing capability in the approved plan.

  2. 02Tool specified

    Forge scopes inputs, outputs, permissions and tests.

  3. 03Code + tests

    The tool is built inside an isolated project environment.

  4. 04Human approval

    Your team sees what it will do before it can run.

  5. 05Workflow resumes

    The new tool becomes one governed step in the plan.

Roadmap with boundaries

What Arc does now, next and later

Arc 1.0Early access

The agent runtime

Ada coordinates Scout, Bolt and Lex across readable, costed, approval-led plans.

Arc 1.xNext

Research and project ingestion

Arc researches before it generates — location context, brochure ingestion and structured project memory.

Arc 2.0Roadmap

On-demand tool creation

Forge specifies, writes, tests and presents missing tools before they join an approved workflow.

The current boundary. Arc is in early access and enabled in account batches. The current system plans and sequences existing Craft tools; deeper research memory and Forge on-demand tool creation are being introduced behind explicit approval gates. Arc is part of Craft, not a separate product or purchase.

FAQ / DIRECT ANSWERS

What Arc does, and what it does not

Availability, project memory, human control and what belongs to the roadmap.

What is Arc?

Arc is the shared intelligence and agent runtime inside the Craft operating system: one project memory that Ada, Scout, Bolt and Lex use to understand inputs, plan work, configure production and govern every output. Forge on-demand tool creation is planned for Arc 2.0.

How is Arc different from Agentic 1.0?

Arc is the shared project intelligence and agent runtime inside Craft; Agentic 1.0 is the outcome-to-plan experience that runs on it. Arc holds project context and coordinates specialist decisions, while Agentic lets a user state an outcome, inspect the resulting plan and approve execution.

Which Arc agents are available in Arc 1.0?

Arc 1.0 uses Ada to own the outcome, Scout to map inputs and sequence work, Bolt to interpret visual project information, and Lex to configure production parameters. Forge on-demand tool creation is an Arc 2.0 roadmap capability, not part of the current Arc 1.0 execution path.

Can Arc use credits or execute a plan without approval?

Arc does not use production credits before the user approves the plan. The user can inspect the steps, inputs, settings, credit cost and approval gates, then edit, reorder or reject the plan before execution begins.

What does Arc remember between steps?

Arc maintains the approved project identity: geometry, materials, camera rules, brand kit, source files, previous outputs, quality decisions and workflow cost. That context moves with the project rather than resetting when the next tool starts.

Are Forge and native AEC integrations available now?

Forge on-demand tool creation and native integrations for Revit, 3ds Max, AutoCAD, Unreal Engine and SketchUp are roadmap capabilities. Integration pilots will begin with Revit and 3ds Max, while current enterprise work can be scoped around the Craft API.

Give the agent team one real outcome

Run a pilot with your project files, current production cost and deadline. Inspect the plan before anything executes.

Book a demo