Domain Kits v0.1
Status: normative high-level prelude contract layer for AI-authored workflows.
Purpose
Define deterministic, reusable contract schemas for common workload families so agents can compose workflows from stable kits instead of ad-hoc effect chains.
Prelude Modules
prelude/modules/30_service_orchestration.gcprelude/modules/31_data_pipeline.gcprelude/modules/32_network_workflow.gcprelude/modules/33_game_loop.gcprelude/modules/34_xr_workflow.gcprelude/modules/35_media_pipeline.gcprelude/modules/37_multi_agent_orchestration.gcprelude/modules/38_realtime_collaboration.gcprelude/modules/39_ml_pipeline.gcprelude/modules/40_backend_topology.gc
Contract Schemas
Service orchestration: - :core/kit/service-dependency.v1 - :core/kit/service-manifest.v1 - :core/kit/service-step.v1 - :core/kit/service-workflow.v1 - :core/kit/service-status.v1
Data pipeline: - :core/kit/pipeline-stage.v1 - :core/kit/pipeline-spec.v1
Network workflow: - :core/kit/network-http-step.v1 - :core/kit/network-process-step.v1 - :core/kit/network-workflow.v1 - :core/kit/network-workflow-result.v1
Game loop: - :core/kit/game-fixed-loop.v1 - :core/kit/game-loop-result.v1
XR workflow: - :core/kit/xr-session.v1 - :core/kit/xr-frame-cycle-result.v1
Media pipeline: - :core/kit/media-asset.v1 - :core/kit/media-build-spec.v1 - :core/kit/media-asset-result.v1 - :core/kit/media-build-result.v1
Multi-agent orchestration: - :core/kit/multi-agent-role.v1 - :core/kit/multi-agent-spec.v1 - :core/kit/multi-agent-assignment.v1 - :core/kit/multi-agent-run-result.v1
Realtime collaboration: - :core/kit/realtime-op.v1 - :core/kit/realtime-session.v1 - :core/kit/realtime-merge-result.v1
ML pipeline variants: - :core/kit/ml-stage.v1 - :core/kit/ml-pipeline.v1 - :core/kit/ml-run-result.v1
Backend topology: - :core/kit/backend-node.v1 - :core/kit/backend-edge.v1 - :core/kit/backend-topology.v1 - :core/kit/backend-plan-result.v1
Determinism Rules
- Kits define only data contracts + deterministic orchestration helpers.
- All side effects remain capability-routed through
core/effect::perform. - No hidden time/network/process behavior is introduced outside explicit effect calls.
Reference Workflow Adoption
Reference workflow entrypoints now use kit APIs:
examples/agent_compute_workflow/workflow_run.gc-> pipeline kitexamples/agent_gpu_compute_workflow/workflow_run.gc-> pipeline kitexamples/agent_network_process_workflow/workflow_run.gc-> network kitexamples/agent_long_running_gfx_loop_workflow/workflow_run.gc-> game-loop kitexamples/agent_xr_runtime_workflow/workflow_run.gc-> deterministic XR runtime lane (gfx/xr::*); XR kit contracts are validated incrates/gc_prelude/tests/prelude_xr_wrappers.rsexamples/agent_media_asset_workflow/workflow_run.gc-> deterministic media import/build lane (image/audio transcode + asset hashing viacore/media::*)examples/agent_service_workflow/workflow.shgenerated check program -> service kitexamples/agent_multi_agent_orchestration_workflow/workflow_run.gc-> multi-agent role/spec orchestration kitexamples/agent_realtime_collaboration_workflow/workflow_run.gc-> deterministic realtime collaboration merge kitexamples/agent_ml_pipeline_variant_workflow/workflow_run.gc-> ML pipeline variant kit over pipeline runnerexamples/agent_backend_topology_workflow/workflow_run.gc-> backend topology planning kit
Drift Guard
Migration and module presence are enforced by:
scripts/check_domain_kit_workflows.sh