zigrix-task-create

name	zigrix-task-create
version	0.4.0
description	Create a revision-0 Zigrix Task and bind its spawned orchestrator through the bootstrap composition flow.
metadata	{"openclaw":{"requires":{"bins":["zigrix"]},"cliHelp":"zigrix task create-task --help"}}

zigrix task create-task

CREATE_TASK is the lifecycle entrypoint. It publishes an authoritative revision-0 OPEN metadata snapshot, immutable audit record, and index projection through the same recoverable pending-commit protocol used by later commands.

Use the stable command name:

zigrix task create-task

Transport-specific flags are intentionally not assumed here. Supply the typed command payload required by the active integration and prefer its JSON result for downstream automation. Resolved paths returned by the integration (specPath, metaPath, projectDir) must be reused rather than reconstructed from config keys.

Bootstrap and orchestrator binding

Creation alone grants no caller authority over later Task transitions.

1. Create with CREATE_TASK.
2. Spawn the selected orchestrator and capture its actual agentId, sessionKey, and sessionId.
3. Bind that exact principal with zigrix task bind-orchestrator / BIND_ORCHESTRATOR.
4. Use the resulting bindingEpoch as part of the stored orchestrator identity.
5. Have that stored orchestrator issue START and every later top-level transition.

After binding, caller role strings and local agent configuration do not confer authority. Only an exact match to the current stored orchestrator agent/session/sessionId/binding epoch may start, block, resume, finalize, report, prepare/register workers, decide submissions, expire assignments, or reassign work.

Safety

• Every create/bind mutation uses a deterministic command id, payload digest, schema version, and expected revision where applicable.
• Retry an in-doubt operation only with the same command id and identical payload.
• Do not use a raw status setter, generic metadata setter, direct metadata edit, or audit/index rewrite to create, bind, or advance a Task.
• Do not collapse CREATE, BIND, and START into an unbound generic start.