Samwise
Pick the Samwise layer you need first. Use the lower contract sections only if the next move still is not clear.
- Primary job: Samwise turns a shaped request into one bounded delivery loop with a visible handoff, proof trail, and closeout receipt — as a single owner, not a charter family.
- First split: Readers still need the intake, Linear-thread, and execution split; the retired Lantern and Spade charters map onto it as history.
- Best use: Open this page when the missing answer is where delivery starts, where the shared thread stays visible, or who actually executes the task.
Choose the Samwise question you arrived with
Send the work to Samwise, then follow the Linear handoff
Use this lane when work is arriving right now and you need the intake path: Samwise owns intake, umbrella shaping, and queue judgment as parent-identity skills — no separate intake charter runs anymore.
Stop once you can name who shapes the request first and where the work thread becomes visible.
Reader orientation
Use this district to understand how Samwise shapes work on Linear, how priority gets decided, and who carries the task through delivery.
What changed recently
Compact updates that help a reader place this agent in the current network story.
- Oct 1·Charter-model convergence: the district now teaches the registry’s July 24 single-owner refactor — Lantern and Spade retired (verified against the registry and the disabled Lantern Cycle cron), intake and execution as parent skills, live gateway cycle roster pinned.
- Jul 6·District landing now publishes a July 6 proof packet that keeps the Lantern-first closeout contract, the phone-first first stops, and the route-local delivery anchors aligned on the same surface.
- May 10·Reframed Samwise as a Lantern-first intake loop on Linear, with Spade taking the scoped execution handoff.
- May 5·Added a first-move chooser so readers can pick Linear, Lantern, or Spade before scanning the entire district.
- May 1·Kept the Linear Agent Gateway story current, including live Codex streams, button-choice flows, elicitation prompts, and OAuth refresh coverage.
Samwise now teaches one delivery truth
New GitHub issues, Linear-native delegations, comments, and assignment-driven handoffs land with Samwise directly, and intake, priority, and scope judgment happen as parent-identity skills before execution starts.
The old Lantern intake charter was retired on July 24; its queue judgment now lives in the samwise-intake skill. Linear keeps the resulting thread legible.
The umbrella issue, routed handoffs, execution checkpoints, and the final receipt stay on Linear so the task keeps one durable conversation surface.
That is where readers should expect to find the latest proof, the current owner, and the next safe move without reconstructing state from chat fragments.
Normal charter-cycle closeout now uses Linear Project Updates and issue-thread evidence, not blanket success summaries to `#saffron-updates`.
Slack remains a failure-before-Linear and human-needed escalation path. That keeps project truth on the tracked work surface instead of splitting it across two channels.
Once intake has shaped the task, Samwise plans, implements, verifies, and delivers with proof-backed closeouts using its own delivery skills — human review owns the merge — without turning Samwise into a governance or architecture agent.
The old Spade execution charter was retired the same day; its delivery behavior lives in parent skills. If the work needs a policy ruling, route design direction, or lifecycle judgment instead, leave the district for Atticus, Meg, or Grafton.
Lantern, Linear, and Spade each own a distinct part of the loop
Samwise shapes new work first: intake, umbrella clarity on Linear, and the judgment call on how execution proceeds — all parent-identity skills today.
Cadence retired; no independent cycles
Linear is where Samwise keeps the umbrella issue, handoff notes, checkpoints, closeout proof, and project-visible outcome together.
Samwise drives each shaped task through planning, implementation, verification, and reported closeout with its own delivery skills; human review owns the merge.
Cadence retired; no independent cycles