missions · the long-horizon structure · in Slack & Microsoft Teams

Multi-week work outlives everyone's attention.
It doesn't outlive a mission.

Week one, everyone's watching. Week three, the launch is still six tasks deep and nobody has looked since Tuesday. A mission is the structure Ayven holds long work in: goals that depend on each other, blockers with named owners and give-up dates, and a next check she schedules herself. The week where nobody's looking always comes — the mission is built for it.

Start free Step through one ↓
mission · Launch the new onboarding
stageopen — she's working it
shape4 goals · 2 blockers · 1 weekly rhythm
deadlinelaunch · Fri the 14th — held on the goal, not in anyone's head
next checkThu 09:00 — hers, not yours

a mission's own header — this is the one you'll step through below

01 · The shape

A longer to-do list isn't a structure. This is.

A mission isn't a thread she remembers — it's a typed graph she executes. Goals are states to reach ("legal signed off") or states to keep true ("we know where signups stall") — with depends-on edges, so downstream work can't start on hope. Blockers are waits with a named owner and a pivot-by date: the moment she stops waiting and re-plans. And every action can be gated on time itself — a calendar date, a weekly rhythm, someone's return from leave, a pending approval.

goal—a state to hold, with observable done-criteria — not an activity
edge—depends-on: gated goals wait for the graph, not for a label
block!a wait with an owner and a pivot-by — she gives up waiting on schedule
clock○her own next check + real RRULE rhythms — the mission wakes itself

02 · One mission, four weeks

Click anything. It knows its own state.

This is "Launch the new onboarding" as the mission holds it — goal nodes, depends-on edges, blockers with owners. Advance the weeks and watch the honest states: a goal isn't "blocked" because someone said so, it's blocked because the graph says so — and ⊕ appears only when the criteria are met where they're checkable.

— week 4 · closeout — except what must keep running —

goal · Onboarding flow rebuilt
state⊕ verified — WEB-214 Done — Jira · week 3
done whenthe ticket shows Done — not when someone says so
ownerDana
historyclaimed week 2 → she checked the ticket → verified week 3
every step sits in the mission's append-only log — written once, not re-summarized
blocker · Dana gone quiet
stateresolved — the ticket moved, week 3
howquiet 2 days → asked Dana once → then checked the ticket, not the person
blockers appear when she detects a wait — they aren't pre-planned pessimism
goal · Legal sign-off on the new copy
state⊕ verified — sign-off recorded · week 3
the waitTom (legal) → out of office → rerouted to M. Chen, context attached
answered byM. Chen · Thu 14:10 — who answered is stored, not assumed
blocker · Legal review — the wait itself
stateresolved — answered · week 3
pivot-bylapsed once → strategy: reroute (logged — she won't repeat it on the next stall)
the ladderreroute → escalate with history → honestly give up
re-planning around people is deliberately slow — pivot-by dates are days, not minutes
goal · Launch announced, checklist closed
state⊕ verified — checklist 9/9 · announcement approved and sent
depends onflow rebuilt + legal sign-off — no actions started here until both held
closeoutproposed to Sarah — closing is her call, and a closed mission can reopen
ongoing goal · We know where signups stall
stateopen — still running on its Monday clock
cadenceFREQ=WEEKLY;BYDAY=MO;BYHOUR=9 — a real RRULE, not a vibe
endswhen Sarah retires it — the goal evaluator can't close an ongoing goal
ongoing goals outlive the event they served — the launch closes out, the question keeps its clock

staged mission with our recurring cast — the states, gates, and pivot mechanics are the product's real ones

03 · The morning digest

Each morning tells you only what needs you.

A mission runs for weeks — you shouldn't have to. The digest reads the graph and sorts it into four honest piles: decisions waiting on you, waits you own that are running out of road, what she did yesterday on your behalf, and what she'll do today. A day with nothing in it sends nothing.

Morning digest — for Sarah · Thu 8:00am
decisions due today
!approve the launch announcement — gated on your hold
at risk on what you own
○legal sign-off — pivot-by Fri, capped by the launch date
yesterday
—rerouted legal review from Tom to M. Chen, context attached
today
—onboarding rebuild: checking WEB-214 before believing "done"
a day with nothing in it sends nothing

04 · Receipts, ours

Missions in the product — states, holdups, honesty included.

The mission board in the Ayven app: a mission in progress, pending human input, next follow-up scheduled
the mission board in the product — a mission waiting on human input, next follow-up already on its clock

the mission board above is from the product · the stepped-through mission is staged with our recurring cast

05 · Starting one

Starting one is a sentence. The structure is her job.

You don't draw the graph. You say what has to happen, the way you'd say it to a person — and Ayven does the mission analysis: pulls out the goals, spots the dependencies, puts owners and give-up dates on the waits, and sets her own first check. When it's done, she proposes closing it — that call stays yours.

SarahSarah · Monday 9:12am @Ayven keep an eye on the onboarding launch — it has to land by the 14th. Dana's building, and legal still needs to sign off on the new copy.
mission opened · Launch the new onboarding
goals3 terminal · 1 ongoing — pulled from what you said
edgeslaunch depends on the build and the sign-off
waitslegal review — owner Tom · pivot-by Wed
first checkThu 09:00 — hers to remember, not yours

thread staged with our recurring cast

Say it once. The mission holds it for weeks.

Start free

just @Ayven in Slack or Teams · approval-gated · receipts on everything