Studio-First Agent Doctrine
HoloScript's long-term agent strategy is Studio-first, Brittney-led, and spatial-native.
Core Position
- Brittney is the primary user-facing intelligence layer.
- Studio is the primary environment for serious creation.
- HoloScript is the native medium for generation, manipulation, and execution.
- Traditional IDE agents are transition tooling, not the strategic center.
What This Means For Agents
The agent ecosystem should not evolve toward equal intelligence split across generic editor assistants and Brittney. Instead:
- Brittney owns the end-to-end creation loop.
- Spatial understanding, scene context, and project memory should accumulate around Brittney.
- Standard IDE agents should focus on repo maintenance, code authoring, testing, and compatibility flows.
- Absorb should bridge text-era codebases into spatially understandable structures.
Agent Role Split
Brittney
- Scene planning
- Asset direction and refinement
- HoloScript generation in context
- Project memory and taste
- Optimization and deployment guidance
IDE Agents
- Package development
- Compiler/tooling work
- Tests, docs, refactors
- Legacy developer onboarding into HoloScript
Absorb
- Codebase ingestion
- Spatial mapping of legacy systems
- Structural understanding for migration into Studio-native workflows
Roadmap Implication
Every major AI feature should be evaluated against one question:
Does this make Studio more inevitable as the best place to build?
If a feature mostly improves a legacy text-first workflow without strengthening Studio adoption or Brittney's moat, it should be deprioritized.