Skip to content

Execution roads

The roads part beneath different banners.

One bounded answer, a sovereign task, and an iterative coding workspace place different work with their receivers. Spellweaver first selects that labor boundary within an immutable Scroll, then admits the cognition and disclosure needed inside it. Price may rank roads that are already eligible; it cannot decide their authority or custody.

Current work uses fixed source-defined Patterns, local capabilities, and the effect-free delegated reference adapter. The bounded outbound public-text A2A profile and opt-in native peer lab have separate evidence. Portal egress remains quarantined and an effectful Coffin does not ship. Workflow owns the policy, Context the material branch, and Security each disclosure.

Choose by the work

Road Choose it when What the remote or lower-trust side owns Canonical return
Local deterministic/tool work parsing, retrieval, classification, transformation, validation, or an exact tool can settle the station no remote custody; the local tool still receives only its authorized projection validated value or owner-settled effect receipt
Local Soulstone Agent one bounded cognitive step needs raw/private semantics or local availability is sufficient local model inference only; AgentSpec, Sigil, truth, and effects remain outside the model typed Agent result, still subject to factual/domain validation
Portal capability / Portal-backed Agent LychD retains decomposition and needs one bounded remote inference or service operation provider receives one exact admitted payload; no workspace, Sigil, tool authority, or application judgment immediate ModelGrant/CallGrant return or durable JobGrant/ServiceJobAttempt result, always quarantined before adoption
A2A / Intercom an enrolled sovereign peer should own one public task schema on its own iron peer chooses its private Scroll, models, tools, and refusal under its policy authenticated typed terminal, refusal, failure, expiry, revocation, cancellation, or loss
Delegated coding agent repository exploration, iterative tool use, tests, patch generation, or verification needs its own runtime loop one read, candidate, or verify Coffin over an immutable projection or disposable worktree quarantined analysis, candidate patch, ArtifactRefs, or verification receipts
Interactive coding seat a human is actively operating a provider-supported Codex, Claude Code, Copilot, or similar client the human client and its account session; not a LychD service an external artifact that later enters ordinary admission and provenance

Use a native local or Portal-backed Agent when one model request can do the work and LychD keeps the plan. Use A2A when the receiver must own a durable public task. Use a delegated coding agent when the worker needs a workspace and iterative tools under LychD containment. Sanitizing a payload does not turn a consumer subscription into an automated road.

The roads are layered

Portal, A2A, and coding agents answer different questions. Portal is a cognition/service boundary. A2A is sovereign task delegation. A coding agent is a contained iterative runtime. They are not three values in one provider dropdown.

From Leads to
Admitted Intent Pinned Scroll and road policy
Pinned Scroll and road policy Native LychD station; A2A peer task; Delegated coding runtime
Native LychD station Deterministic tool; Local Soulstone Agent; Portal capability or Portal-backed Agent
Delegated coding runtime Local/offline cognition; Job-scoped Provider Gate
Job-scoped Provider Gate Separate Portal attempts
A2A peer task Receiver-owned workflow and models

An A2A peer chooses its own internal model; that model is not the sender's Portal. A coding CLI, meanwhile, remains a delegated runtime even when its planner uses an API. The child API call adds an exact disclosure edge under the parent job.

A native Agent loop follows the same rule. Validation repair, tool-result follow-up, changed history, or another model round creates another exact Portal payload and decision; the first grant or disclosure never preauthorizes the loop.

Decide in this order

  1. Name the application owner and purpose. The Composition judges the result and the Scroll pins the exact semantic station. A model, peer, or coding runtime does not choose its own job.
  2. Classify and minimize. Join source influence, select the smallest typed projection, and remove fields not needed for the declared output. Raw history, an entire checkout, or a database row is not the default request shape.
  3. Eliminate forbidden roads. Unknown lineage, local_only, missing identity, prohibited category, unavailable containment, absent task schema, opaque egress, incompatible retention, or insufficient authority closes that branch before price or speed is considered.
  4. Choose the labor owner. Keep the station native, give one sovereign task to a peer, or create one contained coding AgentJob. This decides decomposition, workspace, wait, and result law.
  5. Choose cognition inside that boundary. Native and delegated work may be deterministic, local-model, or Portal-backed. An A2A receiver chooses privately; the sender does not route its provider.
  6. Seal every crossing. Form a consumer-specific Privacy Cut when required, verify it, obtain a fresh tagged-target EgressDecision, reserve budgets, and commit the road decision. Reach, asynchronous, paid, autonomously retriable, or post-submit-reconcilable work also persists its road-owned attempt before transmission; a bounded immediate Portal call retains its grant plus decision and dispatch/security events.
  7. Quarantine and adopt. Remote success supplies candidate material. The Composition's local validators and effect owners decide whether it enters application truth.

Local work supplies the refusal-safe baseline without guaranteeing the best quality. Declared policy may prefer an eligible Portal or peer for latency, specialization, or cost. Economics can rank those choices only after privacy, authority, custody, durability, and terms gates have passed.

One disclosure plan per boundary

Anonymization is receiver-specific. The same sanitized text is not automatically reusable across a provider, a sovereign peer, and a coding runtime.

Consumer Minimum projection Additional boundary
local deterministic station exact authorized fields; raw values only when its Spell requires them no egress decision, but labels and tool/effect authority remain
Portal provider stable instructions, selected history/query/evidence, schemas/options needed for one operation exact PortalTarget, canonical wire digest, provider/model/custody facts
A2A peer values conforming to an admitted public task schema plus authorized ArtifactRefs; never prompt floor, local Graph, tools, Sigil, or model inventory exact A2ATarget, peer/task authorization, durable Intercom identity
coding runtime bounded task plus immutable source projection or disposable candidate worktree runtime/profile/Coffin identity; every child remote call crosses its own Provider Gate
logs and telemetry digests, safe category counts, revisions, decisions, and failure stages never raw spans, pseudonym maps, credentials, prompts, patches, or private errors

A remote coding runtime that needs the full private checkout is not made safe by redacting a few strings. If imports, identifiers, filenames, diagnostics, relationships, or tests cannot survive the projection, use a local coding runtime or refuse. A black-box CLI that bypasses Provider Gate, selects hidden fallback providers, or requires transparent MITM is ineligible.

What Spellweaver closes

Before admission, check that the placement's ExecutionRoadPolicy@1 pins its allowed branches, exact input/output and non-completion, authority, projections, budgets, effects, and recovery. Spellweaver commits an ExecutionRoadDecision@1 binding the exact crossing before its road-owned submission. The later dispatch event, ServiceJobAttempt, Intercom task/outbox, or AgentJob references that decision. Selection never becomes another status ledger or settles the road owner's truth.

Workflow's execution-road law owns the complete records and transaction ordering. The decision is restricted, deployment-local, and non-exportable; Loom, logs, and external receipts receive only its opaque id or Security's scoped keyed EvidenceDigest@1 projection. Plain canonical hashes are not broadly visible evidence or an anonymization claim.

Every remote edge must pass classification, byte-time egress, budget reservation, quarantine, explicit adoption, and any required Privacy Cut or durable submission. A Scroll that can bypass one of them is rejected. The same applies to A2A without task/peer/durable-return law, coding delegation without containment/workspace/artifact law, and Portal fallback that can silently change provider or payload. Loom may display the declared boundaries; it cannot prove an occurrence crossed them correctly.

Pure serial selection

The source-defined RoadSelectionPolicy and propose_road calculation validate a selection subset of execution-road law. A policy binds an exact Pattern revision/station, a declared semantic contract, typed local/Portal/peer/delegated alternatives, their input-projection references and ceilings, and a finite acyclic transition graph. Predicates use closed failure outcomes and explicit precedence. A peer alternative identifies its task schema and target, never its private model. Canonical policy digests preserve explicit priority while ignoring declaration tuple order.

The owner supplies a bound occurrence snapshot, predecessor disposition, finite eligibility observations, original deadline, consumed quantities and outstanding reservations. The calculation proposes at most one alternative. Unresolved work blocks new local and remote work even after closure or expiry. A terminal label alone never permits replacement. Unknown/stale eligibility blocks lower-precedence matching edges; current ineligibility may exclude a branch. Exhaustion, closure, missing transitions and completed observations produce explicit non-selection outcomes. Initial ineligibility does not invent a failed attempt: the owner must supply the relevant pre-submission observation before a fallback edge can be considered. Deadlines and observation windows compare UTC instants, preserving the supplied deadline value without allowing a repeated local hour to extend its lifetime.

Every proposal still needs fresh owner admission, consumer-specific projection, atomic budget reservation and the full persisted road decision. reconciliation_required is a non-execution disposition, not permission to poll or resend. The planner never debits capacity, authenticates observations, adopts output or changes a running Scroll. JSON round-tripping supplies shape evidence, not durable recovery. A stale or replayed snapshot cannot be detected without its owner.

There is no production caller or configuration surface for this subset. It does not wire Nadir, Bridge, Intercom, Portal or a CLI runtime to fallback. Current Bridge preferences retain their separate admission-only meaning. Use State for source and focused evidence; actual durable integration remains a separate gate.

Failure stays on the score

Observation Required route
local model unavailable before work take only an explicit eligible branch and create its first attempt
Privacy Cut loses task semantics remain local, request narrower input, or refuse
verifier is uncertain deny or enter a declared human-review Gate; confidence is not permission
ordinary cache miss before submission preserve the same road and canonical admitted input; execute without reuse, because the miss alone is neither fallback nor refusal
provider/peer/runtime fails before submission a declared fallback may create a fresh road decision and road-owned attempt
timeout or crash after submission reconcile the same road-owned identity; do not activate another road yet
exact same-envelope transport redelivery retain the road-owned attempt, sealed bytes, target, idempotency identity, road decision, and Cut/namespace only when the adapter proves atomic same-key/same-payload replay or no prior effect; obtain a fresh EgressDecision and consume one bounded disclosure use
target, model, peer, workspace, payload, policy, custody route, or semantic attempt changes create a new road decision and EgressDecision; when transformation is required, create a fresh consumer-specific Cut and, if reversible, a fresh namespace/lease
remote return proposes a tool, patch, publication, or other effect keep it quarantined until the local owner separately authorizes that effect
pseudonym lease is missing or expired no rehydration; settle the declared degraded/refused path without raw reconstruction

INDETERMINATE and LOST are evidence-bearing outcomes, not permission to repeat. A fallback decision points to its parent decision while both road-owned histories remain intact.

Continue with anonymization for the Cut, delegated agents for the Coffin/workspace path, Portal Roads for provider selection, and A2A for sovereign task exchange. State of Work remains the delivery owner.