Build/infrastructure engineer for the OBT toolchain and staging environments — obt.dep. dep builds, staging folders (/.staging-), venv layout (binpub→venv manual copy), cross-staging env hygiene, obtnet node environment setup, CMake/toolchain issues. Use for "why won't this dep/staging/toolchain build or resolve"…
C++/pyext implementation agent for the orkid engine. Use to implement ONE precisely-scoped slice of engine work from a written spec (a JUL/plan doc section, a milestone, a fix with named seams). Give it the spec section, the trouble points that name it, and the definition of done. It edits code and gets it…
Verification agent for orkid engine work. Use after an implementation slice to run a named battery — builds (with lying-rc defense), pyext tests, canaries, bounded scene runs, fleet jobs via obtnet, artifact byte-identity/idiff/histogram comparisons — and return a verdict-first report. Give it an explicit list of…
Read-only reconnaissance agent for the orkid engine. Use for lookups that feed coordination — "where is X / who uses Y", verifying spec file:line anchors before briefing, locating seams for a plan doc, summarizing a subsystem's current shape, researching a failed lane's artifacts/diff. Returns file:line-cited…
High-effort planning/curation aide to any coordinator (hub or sub) — digests long specs/ledgers/tasksets, produces decompositions, seat briefs, disposition tables, and plan docs. Use when planning work needs deep reading or judgment but NOT engine implementation (engine-implementer), verification (gate-runner), or…
SUB coordinator — a seat-scoped coordinator on its own machine, working under a HUB coordinator on another machine. Runs its seat's lane with the full subagent discipline (engine-implementer/gate-runner/vet/scout), works from hub briefs delivered to /coordination/inbox plus direct owner instruction. Never loads a…
Procedural look-dev agent for orkid — authors DSL content (terrain graphs, hypermesh recipes, ptex3d materials, scatter, scene composition) to hit a NAMED visual target, thinking in industry technique (Houdini/World Machine/Blender geometry nodes/games VFX) and compiling it onto orkid primitives. Renders regular…
Perceptual-quality analyst for orkid output artifacts — images, movies, meshes (OBJ), heightmaps. Use for open-ended quality work (why does this look wrong, review N renders, compare silhouettes across seeds, corpus sweeps, triage) AND for improving the vet instruments themselves. Instruments-first discipline; never…
Become the HUB coordinator (formerly "master") — the integration seat for multi-agent orkid engine work. Load when the owner says "start up as a hub-coord", names this session the hub/master/integration coordinator, or says "coordinator" with NO hub address to work under. If the sentence names a hub to work UNDER…
How to author procedural content in orkid using HyperSyn (Reality Synthesizer) — a Python-as-DSL system for composing particle systems, 2D/3D procedural textures, mesh/SDF operations, and (eventually) audio/sequencer graphs into compact runtime experiences. Use when the user asks about HyperSyn, ptex2d, ptex3d…
Answer questions about OBT (Orkid Build Tools), dependency management (obt.dep..py commands), pydefaults, ork.build.py, CMake structure, ork.python environment, staging directories, pyext builds, environment variables, and the ork.build git repo. Use when the user asks about building, compiling, dependencies, pip…
Operate THIS machine as an obtnet fleet node — launching the node daemon correctly, what the controller may do to this machine (jobs, builds into the staging, checkout gitsync/sync), node-side etiquette and troubleshooting. Use when setting up, running, or debugging the node side of the fleet (the controller-side…
Drive the obtnet fleet (distributed build/run/sync across machines) via obt.net.py — node routing, async jobs, artifact fetch, git-free tree sync. Use whenever work should run on another machine or files must move between machines without git.
Answer questions about orkid's application framework, AppInitData, ComponentizedApplication, application lifecycle, path expanders, environment setup, and the Python app pattern. Use when the user asks about app init, components, lifecycle callbacks, or environment variables.
Answer questions about orkid's asset catalog system, manifests, asset entries, config spaces, chunked downloads/uploads, encryption codecs, import pipeline, and the catalogimport.py tool. Use when the user asks about asset packaging, manifests, CDN, encryption, or the import/export workflow.
Answer questions about orkid's dataflow graph system, modules, plugs, connections, topological sorting, register allocation, particle system integration, and Python dataflow bindings. Use when the user asks about dataflow graphs, plug connections, particle modules, or graph execution.
Answer questions about orkid's filesystem abstraction, file paths, URI protocols, path expanders, FileEnv, file devices, DataBlock, and file I/O. Use when the user asks about file paths, URI schemes, path expansion, or data loading.
Answer questions about orkid's hierarchical finite state machine (HFSM), states, transitions, predicated guards, FsmData/FsmInstance, FsmGroup, lambda callbacks, DOT visualization, and Python FSM bindings. Use when the user asks about state machines, FSM, HFSM, or state transitions.
Answer questions about orkid's logging system, log channels, backends (stdout/file/HTML/HTTP), performance metrics, and Python logging integration. Use when the user asks about logging, log channels, or debug output.
Answer questions about orkid's math types including fvec2/3/4, fmtx3/4, fquat, DecompTransform, TransformNode, MultiCurve1D, color utilities, and Klein geometric algebra integration. Use when the user asks about vectors, matrices, quaternions, transforms, or math operations.
Answer questions about orkid's Python binding system, pybind11 integration, type codec, VarMap bindings, gilsafepyobj, factory patterns (wfactory/uifactory), and module initialization. Use when the user asks about Python bindings, pybind11 patterns, GIL safety, or type conversion.
Answer questions about orkid's C++ reflection system, RTTI, property registration, serialization, Object class hierarchy, signals/slots, and object factories. Use when the user asks about class registration, property types, serialize/deserialize, or the reflect namespace.