Tasks and execution history

Current status: partial Workstream identity and Run/journal storage. Project-owned identity, owner-authored handoff notes, and immutable attempt records have local tests. The source-backed offline Run path fails closed without Wall protection proof; checkpoints, cross-agent handoff, and the complete durable workflow remain unavailable.

A Workstream is one intended repository change. Its immutable identities link Runs, Candidates, Checkpoints, Decisions, Approvals, Capabilities, budgets, Capsules, and final disposition. Organization/repository ownership, issue key, title, branch, and base are attributes; renaming an issue does not change identity.

A Run is one bounded execution attempt under an exact generation, adapter or job, policy, inputs, budget, and result lineage. It is not a Workstream, shell command, CLI invocation, or Run Target. Retry, resume, handoff, and fork create a child Run while preserving the parent. Actor-scoped idempotency covers create, resume, checkpoint, approval, and export. A policy-first logical Cell may exist before source, a generation, Run, process, or protected state exists.

Deliberate and quick entry

The intended deliberate flow creates a policy-first logical Cell, imports named repositories, then starts a Run in a revalidated compatible generation or admits a new generation when required. The quick agent/path flow atomically creates the same records and crosses the same gates. A matching host path never silently implies continuation. Creating a logical Cell alone creates no process, protected runtime, or source import.

Reusable environments and focused tasks

An Agent Cell is a general-purpose environment that can retain workspace files, scripts, permitted workspace-local tools/dependencies, agent conversation/context state, and task state across explicitly selected Runs. The agent can create and execute scripts there within the admitted limits. Completing a Run or detaching does not by itself delete a retained Cell's state; runtime suspension need not erase that state either.

A user may create another Cell for narrower inputs, context, tools, permissions, or resources. General and focused describe scope, not roles or lifetime: either can be retained or explicitly ephemeral. New Cells receive only selected admitted inputs/context and their own authority. A separate Service Cell is recommended for long-running services needing independent lifecycle or availability.

Ordinary permitted workspace edits, script creation, and workspace-local dependency changes are workload state. Changing admitted sources, policy, runtime/tool profile, adapter, or other security-relevant configuration requires a new generation. Reuse never restores expired or revoked grants. See the Cell lifecycle contract.

Ephemeral and retained work

Low-risk ephemeral work uses one Run under the full authority contract. Default completion destroys runtime and private workspace. Explicit retention seals an eligible checkpoint and converts the Workstream to retained continuity. Workspace, continuity, and evidence retention are separate decisions. GitHub remains the backlog, discussion, code-review, and merge surface.

Example: a paused password-reset task retains its identity when another adapter continues from an authorized checkpoint in a new Run.

See entry flow and Cell identity.