i run product and pipelines at vivacity with aditya on systems and tanish on research. we are building a runtime where an agent can keep a world alive long enough to inspect it, change it, fork a few futures, and choose one after the checks pass.
the interface is a small set of verbs: create, observe, act, simulate, fork, verify, commit, rollback, render, route. underneath that sits persistent state and a domain schema. an agent can ask for pixels, arrays, telemetry, or whatever observation the task needs while the world keeps its own source of truth.
routing is where this becomes useful. an orbit can stay in exact physics, contact can move to a robotics simulator, a materials problem can call a domain solver, and visual uncertainty can reach a learned world model. the shared contract keeps the trace readable across those backends.
my side is the path from an action to a replayable trace. i work on the product surface, pipeline boundaries, and the boring details that stop units or state from quietly changing halfway through a run. the longer architecture and a small two-body world live on the project page.