Ayven, by Alknoma · long work held for weeks, not forgotten

Ayven keeps multi-week work moving in a mission

Week one everyone is 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: waits with named owners and give-up dates, the acts she takes about each one, and a next check she schedules herself.

Start free Step through a four-week mission ↓

01 · The shape

How Ayven holds work that outlives attention

Names the person a wait is on

Ayven writes down who owes the answer and a give-up date.

Gives up waiting on schedule

When the give-up date passes she moves the work to someone who can answer, rather than asking again.

Wakes the mission herself

A real weekly rhythm on the mission, so nobody has to remember to look on Monday.

02 · One mission, four weeks

Ayven moves stalled waits and warns before a date slips

— week 1 · the quiet starts —

blocker

Dana has gone quiet

— two days, no word on the rebuild

action

Ask Dana in her morning

— one message

action

Read the ticket on the board

— the board may already hold the answer

blocker

Legal review — the wait itself

— Tom holds the sign-off

action

Reroute to M. Chen with the context

— the wait expired; she moved it

action

Email Sarah while there is still time

— the launch projects late, so she says so

blocker · Dana has gone quiet
state resolved — the ticket moved at 16:41, week 3
closed bythe ticket changing, not by anyone declaring it
Ayven records a wait on a person with their name and a give-up date.
action · Ask Dana in her morning
state answered and logged — week 3
reply“shipping Thursday” — landed in your thread the minute it arrived
action · Read the ticket on the board
state verified against the tracker — week 3
ruleshe counts work done when the board shows Done
blocker · Legal review — the wait itself
state resolved — M. Chen signed on Friday
the waitTom held it → expired → rerouted to M. Chen with the context attached
Tom's wait expired, M. Chen took it over, and it closed.
action · Reroute to M. Chen with the context
state answered — signed Friday
whythe give-up date passed, so she moved it to M. Chen
action · Email Sarah while there is still time
state answered — Sarah moved the scope
outcomeshe cut one item rather than move the date — the 14th held
she emailed Sarah on the day the projection slipped past the 14th

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

03 · What reaches you

How Ayven tells you only what needs you

Never acts for you without a yes

Direct message · to you
AyvenAPPThu 09:00

Approval Required

Assign
Legal sign-off on the new copy
Assign to
Priya Raman
Comment
Tom is away until the 18th — thread attached

Progress: 1/4 completed · next operation requires approval

Asks only what she cannot find out

Direct message · to you
AyvenAPPThu 09:00

Ayven needs info

Is the 14th still the date we are holding, or has it moved with the legal delay? It is not on the board and it decides what I do next.

Lets you hand a decision to someone else

Direct message · to you
AyvenAPPThu 09:02

Approval Required

Update
The launch checklist
Change
legal sign-off → with Priya, due the 15th

⏱ Expires Thu at 14:00 — assign to keep

04 · Still true

How Ayven keeps a mission’s facts current

Holds the facts a mission depends on

Who owns what, who is away and when they are back, kept with the mission rather than in a thread nobody re-reads.

Catches one going out of date

The facts are checked against how things actually stand, so a stale one is caught before it is acted on.

Redraws everything premised on it

Every wait and every next act that assumed the old value is reconciled first, so one change reaches all of them at once.

A mission keeps moving in the weeks when nobody checks it.

Start free

free plan · ticket changes need your approval · every action logged