An original Starlight field lesson

Turn judgment
into a method.

Choose one recurring piece of work.
Make its boundaries clear enough to use again.

Preserve your first attempt, build an operating contract, inspect a failure and keep the revision. The practice produces a portable record for your own review.

One interactive mission · eight supporting reading practices · no account required

Case brief / Harbor DeskFictional

A product decision
needs a clear explanation.

The job
Prepare a weekly customer field note.
The input
A decision memo and two versions of an onboarding form.
The open question
What may an agent prepare, and where must it stop?

A synthetic teaching case, not customer evidence. First sketch the boundary for a workflow of your own.

01 / Make the work inspectable

Start with your
first judgment.

Bring one recurring workflow using public, synthetic or redacted material. Name its input, owner and useful output. Preserve your initial boundary before opening the starter or authored comparison.

This opens the Academy’s existing Bound one agentic workflow mission. The Studio keeps its canonical contract, practice history and export format. Other mission choices remain available inside it.

Agentic Systems · Preview mission 0.1.0

Bound one agentic workflow

Turn one recurring workflow into a small, inspectable operating contract.

Your artifactAGENT_SYSTEM_CONSTITUTION.md

Mission, owner, inputs, allowed preparation, prohibited actions, evidence gate, escalation, and rollback.

Page memory · No cloud save

Switch freely between four drafts in this page. Download to keep one, then import to continue later. Use public, synthetic, or redacted material. Files are read here; no work is submitted to a server.

Stage 1 of 7 · Orient

Name the recurring work

Choose one workflow with a real owner, input, review moment, and reversible first test.

Keep as evidenceA one-sentence workflow and one accountable human owner.

Who is doing this practice?

Keep the reasoning you choose to share. An entry records your account; it does not assess its quality.

Assistance used in this stage

The mission calls for an independent response. Declare what you actually used, even when it differs.

Access accommodations (optional)

For example, dictation or text enlargement. Access accommodations are distinct from assistance that supplies the thinking. No medical explanation is needed.

Keep the work moving

Continue this mission with your agent.

Download your practice first. Then install the toolkit and give your agent that file with the mission starter. Your first attempt and review history belong together.

Install toolkit in a new tab ↗

Nothing is sent automatically. Keep this tab open until you have saved your work. To return, import a compatible practice file into Mission Studio.

An inspectable practice trail

What this record holds

Presence and format only. No correctness, learning, chronology, sponsorship or authorship is verified.

  • Context namedPending
  • First attempt preservedPending
  • Source notes recordedPending
  • Artifact draftedPending
  • Critique snapshot preservedPending
  • Artifact changed since critiquePending
  • Reflection recordedPending
  • Second context and response recordedPending

Transfer is still pending. Keep this draft and return when you have another context to try.

A guide for a real review

The mission's criteria

  • Bounded purpose25% weight

    One owner, input, output, and stop condition are unambiguous.

  • Human authority30% weight

    External and irreversible actions require named human approval.

  • Evidence quality25% weight

    Sources, checks, exceptions, and uncertainty remain inspectable.

  • Recovery20% weight

    A stop, escalation, and rollback path exist before operation.

These are review criteria, not an automatic score. Downloading a record issues no Capability Receipt and grants no authority.

Mission boundaries and portable record details
Human decision
A named human approves every external send, spend, permission, and irreversible change.
Agent limit
An agent may prepare the packet; it may not appoint its own sponsor or enlarge its authority.
Material to use
Use public, synthetic, or explicitly redacted material in this preview mission.
Pinned mission digest
daeec1e37a8c9d6fdf1e56a04bbdf3812175c560444c3437eb2876e179f42c89
Practice size
1.3 KiB of the 96 KiB export limit

The mission ID, version, digest, declarations, snapshots and unfinished work travel together in the JSON practice file. Keep the original export when moving between tools. A file digest pins the mission content; it does not authenticate your practice.

02 / Compare after an attempt

Keep the claim
inside the evidence.

In the fictional Harbor Desk case, a team reduces an onboarding form from six fields to three. Its packet contains the two form drafts, a decision memo and one fictional support complaint.

That is enough to explain the design choice. It does not establish an increase in completion or sales. The method must preserve that distinction when preparing the customer note.

Before revealing the comparison: write one permitted preparation, one human decision and one condition that stops the work. Use your own workflow in the Studio, and declare any assistance you use.

Reveal the authored operating contract
PURPOSE
Prepare a weekly customer field note from an approved product decision.

INPUT
The decision memo, before/after form and permitted customer context.

ALLOWED PREPARATION
Draft the explanation and a checklist. Retain source references.

HUMAN DECISION
An editor accepts the claims. Sending requires separate approval.

STOP
A required source is missing, withdrawn or inconsistent.

RECOVERY
Keep the draft. Name the missing evidence. Restore it, revise and review.

CLAIM LIMIT
Explain the design choice. Do not claim a conversion increase.

Try to break it.

Remove the before/after form. The corresponding claim should remain blocked. Restore the source and review a new draft. A prepared export still does not prove publication.

Then change the case.

Replace the form change with a pricing-page clarification. Identify which evidence and review boundaries need to change.

03 / Carry the method further

Eight practices.
One connected method.

These original reading practices extend the operating contract into teaching, delivery and ownership. They are supporting exercises, not eight separately implemented interactive missions. Keep one primary artifact in scope.

01Choose the work.Workflow charter

A useful system starts with a repeated job and a person who needs its output.

Attempt first
Name a task you completed last week. Before choosing tools, write its trigger, input, useful output and the person who accepts it.
Make the artifact
Compare the current manual method with a smaller assisted version. Record observed time separately from estimates. Look for available examples, a bounded failure and a reversible first test. An unfamiliar job with no repeat input needs investigation before automation.
Inspect it
Another person can tell when the work starts, what finished means and which missing input stops it. Unknown baseline data stays unknown.
Try another context
Try the same charter on an invoice draft or a research digest. Identify the changed consequence of error.
Return to your practice
02Capture judgment.Decision source packet

Preserve the reason behind the work, alongside the words used to describe it.

Attempt first
Explain a recent decision in three minutes. Ask someone to restate what changed, why and what would make you reverse it.
Make the artifact
Collect the trigger, evidence, chosen tradeoff, rejected alternative and a counterexample. Label observations, assumptions, predictions and preferences. A recording is a useful input; an editor still needs the sources that support its factual claims.
Inspect it
The packet supports the permitted explanation without inventing experience or results. The reviewer can find the source of each factual claim.
Try another context
Capture a decision you later reversed. Keep the correction visible rather than editing the story into an inevitable success.
Return to your practice
03Design responsibility.Preparation and acceptance map

Assign decisions before assigning agents.

Attempt first
Mark each step as human judgment, deterministic processing, bounded model assistance or external action.
Make the artifact
Name the method owner, production operator and reviewer. Give each an input, output, allowed tools and escalation threshold. Separate preparing a message from sending it. Start with a small on-demand process; persistent workers need a demonstrated recurring job and a recovery owner.
Inspect it
Every consequential decision has an accountable owner. A producer cannot silently accept their own unsupported claim or enlarge their permission.
Try another context
Change an internal research note into supplier outreach. Explain which identity, consent and approval boundaries change.
Return to your practice
04Build and recover.Run and recovery record

The method includes what happens when the happy path ends.

Attempt first
Predict what should happen when a source is absent or an export fails halfway. Write the safe state before running the method.
Make the artifact
Use public, synthetic or redacted inputs. Keep the input revision, output, acceptance decision, elapsed time and intervention. Remove a required input deliberately, observe the stop, then restore it and replay. An uncertain external delivery remains uncertain until actual evidence resolves it.
Inspect it
The failed run preserves the draft and identifies the missing evidence. A repeated export is not reported as another successful delivery.
Try another context
Change the input format. Does the method detect the change, or produce a plausible but unsupported answer?
Return to your practice
05Teach from evidence.Explanation, demonstration and practice

Give each format a distinct job for its reader.

Attempt first
Explain the useful decision in 120 words without naming a model or promising a productivity gain.
Make the artifact
Use one accepted method revision to make a short explanation, a demonstration and a practice question when each is justified. Link them to the same sources. Show a correction and a limitation. Use original or permitted assets, captions and readable text alternatives.
Inspect it
The audience can act on the explanation. Every derivative adds a useful view, and none implies results the source did not establish.
Try another context
Teach the same method to a technical operator and a business owner. Change the explanation while preserving the evidence boundary.
Return to your practice
06Connect demand to delivery.Bounded offer and delivery checklist

Describe the useful change, the work required and the limit of the promise.

Attempt first
Write an offer without listing tools, model names, lesson counts or membership perks.
Make the artifact
Specify the buyer, trigger, current workaround, intended artifact, exclusions and support boundary. Link a useful free resource to its matching next step. Keep prospect communication separate from paid-customer service. Payment, access and accepted value require different evidence.
Inspect it
A buyer can explain what they receive and must supply. Price, capacity and availability remain unclaimed until decided and verified in the actual delivery path.
Try another context
Rework the delivery for a team handling private data. Identify the additional review and support work before changing its price.
Return to your practice
07Transfer ownership.Fresh-operator handoff

Transfer the decisions that keep the work good.

Attempt first
Give another operator the packet without a verbal walkthrough. Record where they stop before helping.
Make the artifact
Add an accepted example, a rejected example, decision thresholds, escalation and recovery steps. Ask for one fresh case. Record every intervention and revise the missing instruction. An agent role pass can probe clarity; a claim about human handoff requires an actual human attempt.
Inspect it
The operator identifies missing evidence, locates the source and knows when to escalate. Unperformed steps stay visible.
Try another context
Use another operator or a materially different case. Compare reliance on prior context.
Return to your practice
08Improve the method.Operating review and one experiment

Choose the next change from the constraint in the work.

Attempt first
Pick the next improvement from the latest run. Write the assumption that makes it worth doing.
Make the artifact
Review accepted outputs, unfinished work, intervention time, direct costs and repeat use. Keep denominators and observation windows visible. Choose one change, an owner, a review date and a stop rule. More attention does not repair a broken delivery step.
Inspect it
The proposed change addresses observed friction. Missing data is explicit, and a marketing metric cannot substitute for useful customer work.
Try another context
Return after a real period of use. Report what remained useful, what was abandoned and the maintenance it required.
Return to your practice

Use the work you have made

Make the method
visible and portable.

Shape an explanation around the decision. Continue in your own tools with the same boundary, source references and recovery plan.

Source and version

Know what this record establishes.

This is an original Starlight teaching adaptation of the founder-operations fieldbook authored on 20 October 2026. The fieldbook’s public-systems research informs the editorial method; no third-party course, template, brand or outcome claim is licensed or reproduced here. Harbor Desk and its supplied observations are fictional.

Field lesson
Edition 1.0.0 · authored 2026-10-21
Practice contract
systems.bound-one-agentic-workflow · 0.1.0
Mission source digest
daeec1e37a8c9d6fdf1e56a04bbdf3812175c560444c3437eb2876e179f42c89

The canonical mission supplies the stages, assistance declarations, rubric and sources. Its learner-authored records remain unsigned and unassessed. This lesson does not add a hosted tutor, external action or enrollment.