How it works

A wedding like this already runs on approvals. Both families must agree on the program before it is printed. Guests pay for aso ebi before it goes to the tailor. On the day, the coordinator keeps the program moving.

Owambe Desk writes those processes down as Sanity Workflows, stored next to the content they move. An AI agent drafts and proposes; people approve or reject; a payment webhook confirms money. They all go through the same transitions, and the rules about who may do what are part of each workflow, not just the buttons.

Everything below is read from the live dataset: the deployed definitions, then every run with its real history.

Program of events approval

Definition version 2

The agent drafts the running order from the couple’s brief and both families’ non-negotiables. Both families must approve the same version before it is printed. The coordinator locks it; changes after that go through Reopen.

The stages

  1. 1

    Drafting

    The agent drafts or redrafts the program, then submits it to both families.

    • Submit to both familiesAnyone with access
    • Send to both families: Family review

  2. 2

    Family review

    Both families review the same version in parallel. Either can reject with a reason.

    • Approve (Bride's family)People only
    • Reject with reason (Bride's family)People only
    • Approve (Groom's family)People only
    • Reject with reason (Groom's family)People only
    • Rejected: back to drafting: Drafting
    • Both families approved: Ready for print

  3. 3

    Ready for print

    Both families approved this version. The coordinator locks it for printing.

    • Lock for printingPeople only
    • Locked: Locked

  4. 4

    Locked

    This is the printed program. Changing it means reopening it, which sends it back through both families.

    • Reopen with reasonPeople only
    • Reopened: back to drafting: Drafting

What actually happened (1 run)

Program of events, version 7started 2026-09-28 23:24 · now Ready for print · 19 steps
  1. 09-28 23:24The agent: Submit to both familiesVersion 5. This running order places the Igbo kola rite before all food and drink, seats and serves elders before the couple enters, and brings Tolu and Emeka in with uninterrupted talking drums by 16:00. It includes both families’ introductions and dances, three speeches, the Adeyemi family prayer before the cake cutting, an early meal, and a final dance floor lasting more than an hour, with the formal program ending before 19:30.
  2. 09-28 23:24The workflow: Moved to Family review
  3. 09-28 23:34A signed-in person, for adebayo adeyemi: Approve (Bride's family)
  4. 09-29 07:08A signed-in person, for Chief Adebayo Adeyemi: Approve (Groom's family)
  5. 09-29 07:08The workflow: Moved to Ready for print
  6. 09-29 07:21A signed-in person, for Adaeze Nwosu: Lock for printing
  7. 09-29 07:21The workflow: Moved to Locked
  8. 09-29 07:22A signed-in person, for Adaeze Nwosu: Reopen with reasonPalm wine for the elders must be its own line in the program, straight after the kola nut, before any other food or drink. "Elders' hospitality" does not say this, so the Okafor umunna cannot tell it is there. Please name it and keep it directly after the kola.
  9. 09-29 07:22The workflow: Moved to Drafting
  10. 09-29 07:26The agent: Submit to both familiesVersion 6. The former “Elders’ hospitality” segment has been split so “Palm wine for the elders” is now its own named line, directly after the kola nut and before any other food or drink. The remaining elders’ service follows it, with all later timings and the rest of the program unchanged.
  11. 09-29 07:26The workflow: Moved to Family review
  12. 09-29 07:27A signed-in person, for Chief Adebayo Adeyemi: Approve (Bride's family)
  13. 09-29 07:27A signed-in person, for Chief Ikechukwu Okafor: Reject with reason (Groom's family)> Palm wine for the elders must be its own line in the program, straight after the kola nut, before any other food or drink. "Elders' hospitality" does not say this, so the Okafor umunna cannot tell it is there. Please name it and keep it directly after the kola.
  14. 09-29 07:28The workflow: Moved to Drafting
  15. 09-29 07:30The agent: Submit to both familiesVersion 7. The program now explicitly retains “Palm wine for the elders” as its own named line, placed immediately after “Breaking of kola nut (Oji)” and before every other food or drink service. All other timings, running order, responsibilities and cultural requirements remain unchanged, with owner names converted to the required owner keys.
  16. 09-29 07:30The workflow: Moved to Family review
  17. 09-29 07:39A signed-in person, for Chief Adebayo Adeyemi: Approve (Bride's family)
  18. 09-29 07:40A signed-in person, for Chief Ikechukwu Okafor: Approve (Groom's family)
  19. 09-29 07:40The workflow: Moved to Ready for print

Aso ebi order

Definition version 1

A guest orders aso ebi and pays through Bachs. Only the verified payment webhook can mark it paid. The coordinator then hands it to the tailor (or straight to the guest) and records collection.

The stages

  1. 1

    Ordered

    The guest has chosen fabric and quantity. A Bachs checkout has not been opened yet, or the last one failed.

    • Checkout openedServer or agent only
    • Checkout opened: Awaiting payment

  2. 2

    Awaiting payment

    The guest is on the Bachs hosted checkout. Only the verified webhook moves the order from here.

    • Payment confirmed by Bachs (Wait for Bachs to confirm payment)Server or agent only
    • Payment failed or expired (Record a failed or expired payment)Server or agent only
    • Paid: Paid
    • Payment failed: back to ordered: Ordered

  3. 3

    Paid

    Bachs confirmed payment. The coordinator sends the fabric to the event tailor, or hands it to the guest to sew themselves.

    • Send to the event tailorPeople only
    • Guest sews with their own tailorPeople only
    • With the tailor: With tailor
    • Ready for collection: Ready

  4. 4

    With tailor

    The event tailor is sewing it.

    • Ready for collectionPeople only
    • Ready for collection: Ready

  5. 5

    Ready

    Waiting for the guest (or someone they send) to collect it.

    • CollectedPeople only
    • Collected: Collected

  6. 6

    Collected

    The guest has their aso ebi.

What actually happened (1 run)

1 × Wine aso ebistarted 2026-09-28 23:16 · now Paid · 4 steps
  1. 09-28 23:16The website server: Checkout opened
  2. 09-28 23:16The workflow: Moved to Awaiting payment
  3. 09-28 23:16The Bachs payment webhook: Payment confirmed by Bachs (Wait for Bachs to confirm payment)
  4. 09-28 23:16The workflow: Moved to Paid

Live program adjustment

Definition version 1

On the day, when the program runs more than ten minutes late, the coordinator asks the agent to re-time and trim what is left. The agent proposes; only a person can approve or reject. An approved proposal is applied to the remaining segments in one transaction.

The stages

  1. 1

    Agent is proposing

    The agent reads what has run, what is left and both families’ non-negotiables, and writes a proposal.

    • Ask the agent (Agent proposes a re-timing)Anyone with access
    • Withdraw (Withdraw the request)People only
    • Withdrawn: Withdrawn
    • Proposal ready: Waiting for the coordinator
    • Agent could not propose: Not applied

  2. 2

    Waiting for the coordinator

    The proposal is ready. Only a person can approve or reject it; the agent cannot.

    • Approve and applyPeople only
    • Reject with reasonPeople only
    • Rejected: Rejected
    • Approved: Applying

  3. 3

    Applying

    The approved times are being written to the remaining segments.

    • ApplyAnyone with access
    • Applied: Applied
    • Could not apply: Not applied

  4. 4

    Applied

    The remaining segments run on the new times.

  5. 5

    Rejected

    The coordinator turned the proposal down. Nothing was changed.

  6. 6

    Withdrawn

    The coordinator withdrew the request. Nothing was changed.

  7. 7

    Not applied

    The agent could not produce a valid proposal, or the program moved on before it could be applied. Nothing was changed.

What actually happened (0 runs)

No runs of this workflow yet.