Platform
Our experiences draw on one set of systems: story intelligence, real-time worlds, spatial orchestration, and AI agents. Start with one scene, then see the parts behind it and the projects that use them.
One scene
A visitor steps into a room inspired by an ancient observatory. Four parts of the architecture could bring the scene to life.
A projected astronomer answers a question, drawing on the history and mythology of the night sky.
The visitor selects a constellation; the interactive world shifts to follow that choice.
A shared cue could change the projection, audio, and a robot guide together.
A staff member can check the session and intervene when the experience needs it.
This is an architectural illustration, not a filmed installation. It shows how the parts are designed to work together; projects use only what they need.
The platform
Farwhen is the working name for a modular architecture connecting story intelligence, real-time worlds, AI agents, and physical environments.
We reuse these components across projects. Open-source modules can also be adopted individually.
Stories that grow with the audience.
Story intelligence turns film, video, and written material into a graph of scenes, characters, events, and relationships. Characters keep their identity across a whole story, remember what happened, and respond in conversation. Interactive stories and narrative agents read from the same graph.
Games made for the places we play.
Unity and Unreal foundations for XR, mixed reality, procedural worlds, multiplayer, physics, and gameplay. The same base supports a headset game, a room-scale installation, and an interactive application on a screen.
The room becomes part of the experience.
DASP defines how game engines, story services, and room devices can exchange events. Spatial Venue coordinates headset sessions; lighting, projection, and robot control are integration targets.
Tools for people and agents.
Agent Forge exposes application actions to AI tools, with approvals for consequential changes. Atlas and Agent City help operate and observe workflows.
Synthetic data, simulation, digital humans, and development tooling support the groups above rather than belonging to one of them.
Reusable infrastructure for intelligent, interactive experiences across screens, headsets, and physical spaces.
Behind the platform
For developers: the architecture map, reusable libraries, APIs, project integrations, and open-source references.
Architecture
The map shows how our systems are designed to connect. Each project uses the parts it needs. DASP is our open protocol for connecting story software, game engines, and devices. Agent Forge connects applications to AI agents. Select a system to see its role and connections.
Each box is a system of ours. Lines show how the systems are designed to connect.
Systems and connections in the map
Connections
By project
Choose a project to see which systems it uses and what each one contributes. The filters narrow the view to a type of work.
Stories, characters, and games that respond to the people playing them, in a headset or in a room: a story engine decides what happens, a protocol carries it, and a venue runtime keeps every headset in one session.
Projects
Select a project or a system. Every box in the map is also a button.
Each box is a system of ours. Lines show how the systems are designed to connect.
Connections
Story & world intelligence
Our story and world intelligence: it understands film and video, models stories and characters as a graph, and runs narrative agents over that graph.
Characters and worlds that respond to people need two things: an understanding of the story and its media, and a way to decide what happens next. Story Engine does both, and DASP is the path its decisions take to a game engine or a room.
What it does
Spatial systems
Spatial Venue keeps players in a shared session, with a Unity package connecting the game to the server. Our engine foundations support Unity and Unreal projects. DASP provides a common protocol for experience software and devices, including lighting, sound, and projection.
Capabilities
An open protocol that lets the parts of an experience (engines, headsets, story and AI services, show systems) tell each other what happened and what should happen next.
What it does
Projects using this
Spatial runtime
A venue runtime that keeps the headsets in one room in a single shared session and gives floor staff a live status page and a command-line control tool.
What it does
Projects using this
Agent OS
A hub that connects story and AI services, game engines, and room devices into one experience through DASP.
What it does
Projects using this
Spatial runtime
Our Unity starting point for mixed-reality apps that run on Meta Quest 3 and Android XR headsets from one codebase.
What it does
Projects using this
Spatial runtime
An open-source Unreal Engine plugin for Unreal games and installations that take part in DASP experiences.
What it does
Spatial runtime
An open-source Unreal Engine plugin that gives a game a ready-made, multiplayer-safe base: abilities, inventory, equipment, AI enemies, saving, quests, and seeded procedural levels.
What it does
Projects using this
Venue systems
The hardware in the room, discovered and monitored by Spatial Venue: XR headsets, with lighting, audio, displays, and robots addressed as DASP device nodes.
What it does
Web technologies
People use the forms; AI agents use defined tools for the same actions. Actions such as submitting an inquiry are flagged so the agent asks for confirmation first.
Applications
Web apps whose real actions are open to AI agents as typed tools, so an agent can help a visitor without scraping the page.
What it does
Projects using this
Agent systems
Agent Forge is how an app tells agents what it can do. Atlas runs our own operations on the same rules. Agent City shows the work so a person can see and approve it.
Capabilities
An open-source library that lets a web app offer its real actions to AI agents as safe, typed tools, with consequential actions flagged.
const requestCallback = defineCapability({
id: 'request_callback',
description: "Send the user's name and phone number to the business so it can call them back.",
inputSchema: callbackSchema,
effect: 'write',
consequential: true,
execute: (input) => api.requestCallback(input),
});What it does
Projects using this
Agent OS
Our own operations agents: they turn meeting notes and chat threads into decisions and tasks, and wait for a person before anything is sent outside.
Atlas runs our own studio operations. The patterns in it (policy checks, human approval, an audit log, and model budgets) are the ones we design into every agent system we build.
What it does
Agent City
This scripted demo follows a sample rehearsal inquiry for The Rectangle from arrival to payment. Each district shows a stage of the workflow, including the approval needed before sending a deposit invoice.
Synthetic example data. Approvals in the public demo are scripted.
A rehearsal inquiry arrives from the website and lands at the Front Desk.
The Front Desk classifies the lead and hands it to the Booking Concierge, which checks availability.
A note goes into the CRM, and the CRM Tower shows the lead as synced.
Sending a deposit invoice is consequential, so the agent stops and the Approval Hall asks for a decision.
The approval is recorded, the agent resumes, and the invoice is sent.
The payment arrives, the booking is confirmed on the calendar, and a confirmation email goes out.
See what each agent has done, what is waiting for approval, and where a workflow stopped. The activity history helps you review decisions and trace problems afterwards.
Want this view of your own agents? Get in touch
What it does
Engineering
Languages, engines, and techniques we use, with examples from the systems above.
Video split into shots, indexed by what is seen and said, and searchable with time-coded answers.
In Story Engine
Typed story graphs of scenes, beats, arcs, conflicts, and themes, where every AI pass is recorded and reversible.
In Story Engine
Characters recognized across a film, and conversations among several characters driven by the story graph.
In Story Engine
Unreal C++ gameplay systems, verified with three players in multiplayer.
A Rust venue server that runs 48 players in 8 sessions with a 1.16 ms p99 tick, inside a 5 ms budget.
Real-time 3D in the browser, and Unity headset packages with shader prewarm and performance probes.
One Unity codebase for Quest 3 and Android XR headsets: hands, controllers, and held tools that survive fast swings.
Content placed on the real floor that stays put across launches, built on the headset’s tracking and anchors.
Venue networking: 30 Hz state sync over UDP, headset discovery, and telemetry.
TypeScript tools that browser agents call over WebMCP, with effect classes and approval flags.
Python agents behind a policy gate: human approval for outbound actions, an audit log, per-agent model budgets, and an MCP server.
In Atlas
Model calls through AI Gateway for inquiry screening, and eval runners that gate automatic actions on a golden set.
Demos and sites deployed on Vercel, and AWS infrastructure as code (CDK).
Postgres for agent memory and a tamper-evident audit log.
In Atlas
Prometheus metrics and a live status feed from the venue server, and metadata-only execution events from Agent Forge.
Multi-camera rendering of digital humans with ground-truth passes, retargeted motion capture, and cloud render farms.
Deterministic synthetic scenarios that play through the real adapters, for demos and tests.
In Agent City
Simulated players that fill venue sessions without headsets.
Get in touch
Describe what it should do. You get a draft brief to review before anything is sent.