Grafton
Pick the Grafton exit first. Use the lower stewardship map only if the next route is still unclear.
The Grafton landing still works best as a stewardship-first district summary
This October 6 pass keeps the existing Lifecycle, Coordination, and Capabilities exits intact, keeps the district owning the short routing answer, the stewardship boundary, and the broader Grafton route family map, and the Explore band now carries the registry's retired OpenClaw Forge alias with an explicit retired explanation that routes active work to Forge.
- Fast exits: Lifecycle, Handoffs, and Owner stay visible before the lower stewardship map begins.
- District contract: The landing still owns the short routing answer, role boundary, and deeper route-family map.
- Authority stop: Grafton keeps initiative truth legible, then sends policy, handoff, and execution questions outward.
Reader orientation
Use this district when you need the shortest path to what Grafton owns, when work should stay in lifecycle stewardship, and when it should leave for coordination or execution ownership.
What changed recently
Compact updates that help a reader place this agent in the current network story.
- Jul 6·District landing now publishes a July 6 proof packet aligned with the current lifecycle, handoff, and owner route split while keeping the phone-first first stops explicit before the lower stewardship map begins.
- Jun 20·District landing now keeps lifecycle, handoff, and owner exits visible on a 390x844 viewport before the lower stewardship stack, bringing Grafton onto the same phone-first district grammar Atlas now uses on the refreshed agent landings.
- May 22·District landing moved onto the shared Atlas grammar, making Lifecycle, Coordination, and Capabilities the first readable choices instead of a wall of equal-weight cards.
- May 5·Added a first-stop chooser so readers can enter Grafton through lifecycle logic, unblock paths, or portfolio context before scanning the full district.
- Apr 9·Added context links that make the seed-to-work story easier to follow from the district landing page.
Choose the question you arrived with
Start with the lifecycle model
Use Lifecycle when the real question is whether the work is still a Seed, ready for promotion, moving through execution, or waiting on closeout.
Best when you need the gate logic, the current stage, or the missing proof that would move the work forward.
Stop once you can name the current phase, the next gate, and the evidence Grafton is waiting for.
What Grafton owns, and where it stops
Every initiative starts as a Seed. Grafton watches for enrichment, dormancy, promotion readiness, and wake conditions before pretending the idea is execution work.
Stay on the district page when you only need the short model. Leave for Lifecycle when you need the exact stage rules.
Grafton decides whether a Seed has enough clarity, upside, owner commitment, and first-slice shape to become tracked execution work.
This is the point where Grafton promotes or parks the work. It is not the point where architecture or policy decisions get invented.
Grafton is the place where missing handoffs, stale movement, and stalled closeout become visible before a delivery lane quietly dies.
If the lifecycle stage is obvious but the work is stuck between people or agents, leave this page for Coordination.
It does not write code, replace sponsors, decide architecture policy, or own execution capacity. It keeps the garden honest so the right owner can move.
If the remaining question is who should execute, leave this page for Capabilities or the relevant charter page.
The specialist lanes Grafton runs around the garden
Weekly cycle-quality reports and low-value pattern detection. Rake looks for repeated effort that is not actually moving initiatives forward.
Cadence cron, daily recent-cycle batch review plus weekly synthesis
Drift detection across charter definitions and project state. Shears trims back work that has drifted away from its declared purpose.
Cadence cron, every six hours for structural-truth and drift review
Milestone and pipeline health across active charters. Trellis keeps the structural picture visible instead of letting every issue read as isolated work.
Cadence cron, recurring flow/routing/backlog health review
Handoff-quality stewardship for stuck Scout and Meg work. Watering Bucket helps work move again when it stalls between agents.
Cadence cron, twice-daily readiness scan plus focused drill-down