Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
156 lines
4.1 KiB
YAML
156 lines
4.1 KiB
YAML
aggregates:
|
|
- bucket: applicants
|
|
initial: open
|
|
states:
|
|
open:
|
|
event: applied
|
|
invited:
|
|
event: invited
|
|
active:
|
|
event: onboarded
|
|
departed:
|
|
event: departed
|
|
declined:
|
|
event: declined
|
|
transitions:
|
|
active:
|
|
- departed
|
|
invited:
|
|
- active
|
|
- declined
|
|
open:
|
|
- invited
|
|
- declined
|
|
- bucket: custody_requests
|
|
initial: open
|
|
states:
|
|
open:
|
|
event: received
|
|
mail:
|
|
to: submitter
|
|
subject: We have your message
|
|
body: Your message reached the custodians of the first node. We read everything that comes in - expect a real reply, not an autoresponder.
|
|
in_dialogue:
|
|
event: in_dialogue
|
|
resolved:
|
|
event: resolved
|
|
mail:
|
|
to: submitter
|
|
subject: Your case is resolved
|
|
body: This is resolved. Here's what we found and what we did about it - write back if it isn't settled from where you sit.
|
|
declined:
|
|
event: declined
|
|
mail:
|
|
to: submitter
|
|
subject: On your message to the custodians
|
|
body: We've read your message and decided this isn't something we can take on as custodians. If you think we've missed something, write back and tell us.
|
|
transitions:
|
|
in_dialogue:
|
|
- resolved
|
|
- declined
|
|
open:
|
|
- in_dialogue
|
|
- declined
|
|
- bucket: development_proposals
|
|
initial: open
|
|
states:
|
|
open:
|
|
event: proposed
|
|
approved:
|
|
event: approved
|
|
rejected:
|
|
event: rejected
|
|
transitions:
|
|
open:
|
|
- approved
|
|
- rejected
|
|
- bucket: organizations
|
|
initial: prospect
|
|
states:
|
|
prospect:
|
|
event: identified
|
|
client:
|
|
event: became_client
|
|
past_client:
|
|
event: churned
|
|
transitions:
|
|
client:
|
|
- past_client
|
|
prospect:
|
|
- client
|
|
- past_client
|
|
- bucket: projects
|
|
initial: open
|
|
states:
|
|
open:
|
|
event: submitted
|
|
mail:
|
|
to: submitter
|
|
subject: We have your brief
|
|
body: |-
|
|
Your brief is in front of us. We read the whole thing before we reply, so it may take a few days - you'll hear from us either way.
|
|
|
|
What you can do next: {site}/decide/commission?chain={chain}&email={email}
|
|
accepted:
|
|
event: accepted
|
|
mail:
|
|
to: submitter
|
|
subject: We'd like to take this on
|
|
body: We want to take this on. Next we'll be in touch to talk through scope, timing and how we'll work together.
|
|
declined:
|
|
event: declined
|
|
mail:
|
|
to: submitter
|
|
subject: On your brief
|
|
body: We've read your brief and this isn't one we're taking on. It isn't a judgment on the problem - just not a fit for us right now.
|
|
transitions:
|
|
open:
|
|
- accepted
|
|
- declined
|
|
- bucket: subscribers
|
|
initial: open
|
|
states:
|
|
open:
|
|
event: subscribed
|
|
unsubscribed:
|
|
event: unsubscribed
|
|
transitions:
|
|
open:
|
|
- unsubscribed
|
|
- bucket: trials
|
|
initial: open
|
|
states:
|
|
open:
|
|
event: received
|
|
mail:
|
|
to: submitter
|
|
subject: We're looking at your draft
|
|
body: We have what you sent. A person will read it and build your draft, or tell you why not - you'll hear from us either way.
|
|
approved:
|
|
event: approved
|
|
mail:
|
|
to: submitter
|
|
subject: Your draft is approved
|
|
body: Your draft is approved and on its way. We built it from your own words - have a look when it's ready and tell us what to change.
|
|
previewed:
|
|
event: previewed
|
|
mail:
|
|
to: submitter
|
|
subject: Your draft is ready to view
|
|
body: Your draft is ready to look at. It's built from your own words - the link below takes you straight to it.
|
|
declined:
|
|
event: declined
|
|
mail:
|
|
to: submitter
|
|
subject: On your draft
|
|
body: We've decided not to build this draft. If the situation changes, get back in touch and we'll take another look.
|
|
transitions:
|
|
approved:
|
|
- previewed
|
|
- declined
|
|
open:
|
|
- approved
|
|
- declined
|
|
attended_by: |
|
|
approved -> previewed: the n8n workflow that builds the draft site from an approved intake (docker, rauthy, portal content) and sends the preview link. Until it exists, owners run portal-trainer by hand and press the button.
|