uhhm.no rebuilt from a trainer plan: trials, and the redoal custodians
Lint and reload / lint (push) Skipped
Lint and reload / lint (push) Skipped
Built by portal-trainer from plans/uhhm.yaml (uhhm/portal-trainer, runs/uhhm-2026-09-23): the five live buckets keep their state and event names, so every record on the owners' desk stays. New: `trials`, a business trying the trainer on its own workflow, approved by an owner before anything is built (the n8n preview workflow comes later, noted as attended_by); `custody_requests`, what reaches UHHM as the custodian of the redoal network, on a custodians' desk owners can watch. Owners invite into both desks. needs.yaml holds the site to its needs from here on; the lint reads it. Gone from the live site: the starred-repos card, the proposal editor with its file picker and /review/[record], and the /applied, /project and /subscribed followups (now /received/<need>; the unsubscribe move is /decide/subscribe). The pins move to v0.3.42: `invite:` and `attended_by` need a portal newer than the v0.3.36 this site runs. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5.1
parent
58225386b0
commit
5b657828e1
+173
@@ -0,0 +1,173 @@
|
||||
needs:
|
||||
- done_when:
|
||||
- accepted
|
||||
- declined
|
||||
enters: /
|
||||
handled_by: owners
|
||||
id: commission
|
||||
lands_in: projects
|
||||
max_fields: 4
|
||||
max_steps: 2
|
||||
stages:
|
||||
- open
|
||||
- accepted
|
||||
- declined
|
||||
success:
|
||||
- accepted
|
||||
via: You run an organization that needs software built
|
||||
wants: a considered reply to a brief, from people who read the whole thing
|
||||
who: an organization with a problem it wants software to solve
|
||||
- done_when:
|
||||
- previewed
|
||||
- declined
|
||||
enters: /
|
||||
handled_by: owners
|
||||
id: trial
|
||||
lands_in: trials
|
||||
max_fields: 6
|
||||
max_steps: 2
|
||||
stages:
|
||||
- open
|
||||
- approved
|
||||
- previewed
|
||||
- declined
|
||||
success:
|
||||
- previewed
|
||||
via: You run an organization that needs software built
|
||||
wants: a first draft of a site for their own roles, built from their own words and approved by a person first
|
||||
who: someone who runs a business where requests, approvals and handovers get lost, and wants to see it as a site before committing to anything
|
||||
- done_when:
|
||||
- departed
|
||||
- declined
|
||||
enters: /
|
||||
handled_by: owners
|
||||
id: collaborate
|
||||
lands_in: applicants
|
||||
max_fields: 3
|
||||
max_steps: 2
|
||||
stages:
|
||||
- open
|
||||
- invited
|
||||
- active
|
||||
- departed
|
||||
- declined
|
||||
success:
|
||||
- departed
|
||||
via: You want to join us, follow us, or fix a page on this site
|
||||
wants: to be read as a person, and invited in if there is a fit
|
||||
who: someone who wants to work with us on what we build
|
||||
- done_when:
|
||||
- unsubscribed
|
||||
enters: /
|
||||
handled_by: owners
|
||||
id: subscribe
|
||||
lands_in: subscribers
|
||||
max_fields: 2
|
||||
max_steps: 2
|
||||
stages:
|
||||
- open
|
||||
- unsubscribed
|
||||
success: []
|
||||
via: You want to join us, follow us, or fix a page on this site
|
||||
wants: a note now and then, and an easy way out
|
||||
who: someone who wants to hear from us when there is something to say
|
||||
- done_when:
|
||||
- approved
|
||||
- rejected
|
||||
enters: /
|
||||
handled_by: owners
|
||||
id: propose
|
||||
lands_in: development_proposals
|
||||
max_fields: 3
|
||||
max_steps: 2
|
||||
stages:
|
||||
- open
|
||||
- approved
|
||||
- rejected
|
||||
success:
|
||||
- approved
|
||||
via: You want to join us, follow us, or fix a page on this site
|
||||
wants: the change read by a person and, if approved, made
|
||||
who: a visitor who sees how a page on this site should change
|
||||
- done_when:
|
||||
- resolved
|
||||
- declined
|
||||
enters: /
|
||||
handled_by: custodians
|
||||
id: custody
|
||||
lands_in: custody_requests
|
||||
max_fields: 4
|
||||
max_steps: 1
|
||||
stages:
|
||||
- open
|
||||
- in_dialogue
|
||||
- resolved
|
||||
- declined
|
||||
success:
|
||||
- resolved
|
||||
via: 'You are on the redoal network: a node, an app, or a recording that concerns you'
|
||||
wants: an answer from a custodian, and action where the network keeps something it should not
|
||||
who: someone who runs, builds on, or is affected by the redoal network and needs the people who keep its first node
|
||||
- done_when:
|
||||
- past_client
|
||||
enters: /owners/prospect
|
||||
enters_as: owners
|
||||
handled_by: owners
|
||||
id: prospect
|
||||
lands_in: organizations
|
||||
max_fields: 2
|
||||
max_steps: 1
|
||||
stages:
|
||||
- prospect
|
||||
- client
|
||||
- past_client
|
||||
success: []
|
||||
via: Keep an organization on your radar
|
||||
wants: it written down and walked through its states from the desk
|
||||
who: an owner who has met an organization worth following up
|
||||
personas:
|
||||
- id: architecture-firm
|
||||
need: commission
|
||||
text: We run a small architecture firm and our project files are scattered across three cloud drives. We want to pay someone to set up proper storage and backups we control ourselves.
|
||||
- id: climbing-gym-founder
|
||||
need: commission
|
||||
text: I have an idea for a booking app for climbing gyms and I'm looking for a team that can build the first version with me.
|
||||
- id: municipality-buyer
|
||||
need: commission
|
||||
text: Our municipality needs an internal tool for tracking building permits. We are looking for a vendor who can scope it and deliver it.
|
||||
- id: exhibition-visitor
|
||||
need: subscribe
|
||||
text: I saw your drawing network at an exhibition and liked it. I don't want to get involved, I'd just like to know when there is news.
|
||||
- id: tech-journalist
|
||||
need: subscribe
|
||||
text: I write about Nordic technology. Keep me posted on what you release so I can cover it.
|
||||
- id: rust-developer
|
||||
need: collaborate
|
||||
text: I'm a Rust developer between jobs and I like that you build in the open. I would love to contribute, and maybe join you.
|
||||
- id: interaction-designer
|
||||
need: collaborate
|
||||
text: I'm an interaction designer. I want to work with you on the drawing interface.
|
||||
- id: student-intern
|
||||
need: collaborate
|
||||
text: I'm a computer science student looking for a summer internship doing infrastructure work.
|
||||
- id: plumber-owner
|
||||
need: trial
|
||||
text: I run a plumbing company with four vans. Jobs come in by phone and text and some get lost. I'd like to see how this would look for us before I spend any money.
|
||||
- id: dance-school
|
||||
need: trial
|
||||
text: We are a dance school. Enrolments, cancellations and invoices all go through one email inbox that only I understand. Can you show me a version made for us?
|
||||
- id: node-runner
|
||||
need: custody
|
||||
text: I run a small server in Berlin and want to host a redoal node that peers with yours. Who do I talk to?
|
||||
- id: recorded-name
|
||||
need: custody
|
||||
text: Someone left a recording on redoal that says my full name and where I live. I want it gone, and I want to know who is responsible for that network.
|
||||
- id: app-builder
|
||||
need: custody
|
||||
text: I'm building a music app and would like to use redoal's gesture addresses in it. Is that possible, and who decides?
|
||||
- id: wording-fix
|
||||
need: propose
|
||||
text: The subscribe page should say how often you actually write. I'd like to suggest that exact change to the page.
|
||||
- id: rewrite
|
||||
need: propose
|
||||
text: One page on this site reads wrong to me and I know exactly how I'd rewrite it. Where do I send the new text?
|
||||
Reference in New Issue
Block a user