The Delegation Practice

Make delegated work trustworthy.

Map the work. Bound the authority. Test the system. Prove what happened. Earn the right to do more.

Map one workflow Examine the evidence
Owner
Accountable operator
Authority
Observe one workflow
Proof
No evidence attached yet
State
draft
Delegated Work Control

Diagnose the system before changing the policy.

The Three-Tier Framework keeps failures local: verify the Database, then the Automation, then the Judgment governing the next move.

01 / Database Is the operating truth available?

Inspect the records, state, policy versions, and proof artifacts the workflow is allowed to use.

02 / Automation Did the execution path succeed?

Trace the tools, stops, approvals, retries, and receipts without assigning judgment to motion alone.

03 / Judgment Was the right policy applied?

Name who owns the decision, what boundary governed it, and when the system must escalate or stop.

Field map

See where work may run, wait, or stop.

This representative Marketplace review queue is a read-only teaching surface. It exposes a real operating shape without claiming production access or client proof.

Map / shared graph contract

The map is the first policy artifact.

Each node names an owner and each edge exposes the handoff that must be governed, tested, and proved.

Map story canvas

Map story for Submitted asset packet

The same Map graph can teach the workflow to a person and preserve the typed contract an agent needs to act safely.

1. Map Submitted asset packet before execution. Marketplace review owner owns the operating path. The canvas makes the workflow, handoffs, and next decision legible before an agent or system acts. 2. Validator and queue sync can run when the rule is clear. Validator and queue sync coordinates with Supplemental reviewer brief; the map keeps AI assistance bounded to the work it can safely support. 3. Reviewer approval decision stays with a person. Human decides approve, reject, request changes, or escalate policy ambiguity. 4. No ungrounded approval is the stop condition. Stop before approval, rejection, security claims, or timeline promises without evidence. 5. Reviewer dashboard receipt shows the receipt. Shows validation evidence, reviewer state, creator-facing notes, and policy flags. 6. Use the map as booking context for a workflow pilot. The map has enough owner, assistive work, system behavior, and decision context for a first run.

Workflow map 7 nodes / 7 edges
Run Wait Stop
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Operator journey 01 / 10

Ten stages. Ten inspectable artifacts.

Progress follows the work produced, not time on page or content consumed.

Stage 01 Delegation Card

Enter

What work am I responsible for?

Name one workflow, owner, stakes, and current pain.

Missing artifact: Operator name or role, Workflow, Accountable owner, Stakes

Internal preview Not certification

Practice Receipt

Generate only after every artifact and governance binding is inspectable.

Source evidence04 records

Claims stay attached to state and limits.

Verified, review, and draft records are deliberately different. Open the owning surface before deciding what the system has earned.

  1. 01 Operating claimSignal → Decision → ProofThe category method stays attached to workflow ownership, policy boundaries, and inspectable evidence. verifiedTHESIS-01Current public method
  2. 02 Workflow modelMarketplace review queueA read-only Map story shows the signal, automated preparation, human review, stop condition, and proof landing zone. verifiedMAP-01Representative local map
  3. 03 Prototype proofMarketplace workflow compilerThe proof route keeps representative fixtures, active-development status, and the absence of production writes visible. reviewCASE-01Public limits intact
  4. 04 Flagship defenseGoverned Agent DeliveryThe repo-owned case follows a Linear signal through bounded implementation to production proof. It remains a proposed defense until the full evidence packet is examined. draftDEFENSE-01Not yet publicly defended
Flagship defense

Governed Agent Delivery: from Linear signal to production proof.

This case follows work from a Linear issue to production. At every step, it must keep the owner, allowed actions, required checks, approval points, and rollback evidence visible.

Unresolved boundary

A proposed case is not a passed defense.

Passing still requires artifact inspection, counterexample review, a rollback check, and an independent verdict with real consequences.

School + skeptical review

Finish with a Practice Receipt, not a certificate.

Practice produces an inspectable workflow map, authority envelope, test plan, proof bundle, and review verdict. Skeptical review may support, revise, hold, or falsify the thesis; completion never grants portable authority.

Rehearse the operator journey Inspect a bounded proof route
Owner
Accountable practitioner
Authority
One named workflow only
Proof
Artifact bundle + review verdict
State
review