Sonnet writes, qwen3:8b routes: 16 then 19 of 27 with descriptions, 19 then 21 of 27 on headings alone. One card took seven personas until it named redoal; what remains is on the front door and mostly a judgment the plan could make differently, not the words. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
14 KiB
You write the words for one page of a website for this business.
Business: UHHM About: UHHM builds software around a clear argument: infrastructure, tools and products for organizations that can say what problem they have. It also builds and carries the redoal network - the gesture math, the relay, the first node, and the portal this site runs on - and answers for what that network keeps. Contact: Bendik Aagaard Lynghaug bl@uhhm.no Language to write in: en
Everyone the site serves:
- door build: for an organization with a problem software should solve, or a business that wants to see its own workflow as a working site before paying anyone; behind it: commission, trial
- door join: for someone who wants to build with us, hear from us now and then, or change this site; behind it: collaborate, subscribe, propose
- commission: an organization with a problem it wants software to solve - wants: a considered reply to a brief, from people who read the whole thing. Handled by owners. Stages: open -> accepted -> declined.
- trial: someone who runs a business where requests, approvals and handovers get lost, and wants to see it as a site before committing to anything - wants: a first draft of a site for their own roles, built from their own words and approved by a person first. Handled by owners. Stages: open -> approved -> previewed -> declined.
- collaborate: someone who wants to work with us on what we build - wants: to be read as a person, and invited in if there is a fit. Handled by owners. Stages: open -> invited -> active -> departed -> declined.
- subscribe: someone who wants to hear from us when there is something to say - wants: a note now and then, and an easy way out. Handled by owners. Stages: open -> unsubscribed.
- propose: a visitor who sees how a page on this site should change - wants: the change read by a person and, if approved, made. Handled by owners. Stages: open -> approved -> rejected.
- custody: someone who runs, builds on, or is affected by the redoal network and needs the people who keep its first node - wants: an answer from a custodian, and action where the network keeps something it should not. Handled by custodians. Stages: open -> in_dialogue -> resolved -> declined.
- prospect: an owner who has met an organization worth following up - wants: it written down and walked through its states from the desk. Handled by owners. Stages: prospect -> client -> past_client.
The page: questions/join/index.yaml
It is a page one kind of visitor reaches from the front door. question is what this page asks them; under needs, each entry is one alternative they can pick, with the form behind it.
Below is the page as JSON. Every value is a slot that says what to write there. Return the same JSON with every slot replaced by your words. Keep every key exactly as it is. A slot left as it is counts as no answer.
Rules for the words:
questionis a question the reader could ask themselves.- A heading says what the reader gets, in the reader's own words, and must work without its description.
- Lead with what a thing enables. No negations in headings. No trade jargon the reader would not use.
- Descriptions are one or two short sentences. Labels and buttons are a few words.
- The button says what pressing it does; the encouragement says what happens next or how little it takes; the form's guidance line says what to have ready. Placeholders are example answers in the reader's words.
- An icon is one name from this list, chosen for what the reader is doing, or empty: house, building-2, store, school, map-pin, route, footprints, trees, leaf, snowflake, sun, users, user, user-plus, user-check, baby, heart-handshake, hand-helping, handshake, smile, mail, phone, message-circle, megaphone, bell, send, inbox, alert-triangle, siren, shield, construction, hammer, wrench, ruler, package, truck, car, bus, train-front, bike, calendar, clock, file-text, clipboard-list, receipt, wallet, coins, banknote, credit-card, key, lock, search, star, gift, shopping-cart, lightbulb, flag, thumbs-up, check-circle, briefcase, stethoscope, activity, camera, pencil, refresh-cw, list, layers, vote, scale
- Write the way people in this trade and country actually speak.
{
"description": "<WRITE: one or two short sentences>",
"needs": {
"collaborate": {
"button": "<WRITE: a button, one to three words, saying what pressing it does>",
"description": "<WRITE: one or two short sentences>",
"encouragement": "<WRITE: one reassuring sentence: what happens with what they send, or how little it takes; or empty>",
"form_description": "<WRITE: one short line of guidance above the form, or empty>",
"form_title": "<WRITE: a title for the form, two to four words>",
"heading": "<WRITE: a heading, at most eight words, saying what the reader gets>",
"hints": {
"email": "<WRITE: an example answer for the field email, as a placeholder; or empty>",
"interest": "<WRITE: an example answer for the field interest, as a placeholder; or empty>",
"name": "<WRITE: an example answer for the field name, as a placeholder; or empty>",
"note": "<WRITE: an example answer for the field note, as a placeholder; or empty>"
},
"icon": "<WRITE: an icon name from the list at the end, the one that fits this best; or empty>",
"labels": {
"email": "<WRITE: a form label for the field email>",
"interest": "<WRITE: a form label for the field interest>",
"name": "<WRITE: a form label for the field name>",
"note": "<WRITE: a form label for the field note>"
},
"road_description": "<WRITE: one or two sentences walking the reader through the stages this goes through, in order (the stages are listed above), in their words>",
"road_icon": "<WRITE: an icon name from the list at the end that fits this section; or empty>",
"road_title": "<WRITE: a short title, two to four words, for the line that says what happens after sending>",
"who_description": "<WRITE: one sentence: who reads what they send, and how to reach them meanwhile>",
"who_icon": "<WRITE: an icon name from the list at the end that fits this section; or empty>",
"who_title": "<WRITE: a short title, two to four words, for the line that says who reads it>"
},
"propose": {
"button": "<WRITE: a button, one to three words, saying what pressing it does>",
"description": "<WRITE: one or two short sentences>",
"encouragement": "<WRITE: one reassuring sentence: what happens with what they send, or how little it takes; or empty>",
"form_description": "<WRITE: one short line of guidance above the form, or empty>",
"form_title": "<WRITE: a title for the form, two to four words>",
"heading": "<WRITE: a heading, at most eight words, saying what the reader gets>",
"hints": {
"email": "<WRITE: an example answer for the field email, as a placeholder; or empty>",
"page": "<WRITE: an example answer for the field page, as a placeholder; or empty>",
"proposed_yaml": "<WRITE: an example answer for the field proposed_yaml, as a placeholder; or empty>",
"rationale": "<WRITE: an example answer for the field rationale, as a placeholder; or empty>",
"submitted_by": "<WRITE: an example answer for the field submitted_by, as a placeholder; or empty>"
},
"icon": "<WRITE: an icon name from the list at the end, the one that fits this best; or empty>",
"labels": {
"email": "<WRITE: a form label for the field email>",
"page": "<WRITE: a form label for the field page>",
"proposed_yaml": "<WRITE: a form label for the field proposed_yaml>",
"rationale": "<WRITE: a form label for the field rationale>",
"submitted_by": "<WRITE: a form label for the field submitted_by>"
},
"road_description": "<WRITE: one or two sentences walking the reader through the stages this goes through, in order (the stages are listed above), in their words>",
"road_icon": "<WRITE: an icon name from the list at the end that fits this section; or empty>",
"road_title": "<WRITE: a short title, two to four words, for the line that says what happens after sending>",
"who_description": "<WRITE: one sentence: who reads what they send, and how to reach them meanwhile>",
"who_icon": "<WRITE: an icon name from the list at the end that fits this section; or empty>",
"who_title": "<WRITE: a short title, two to four words, for the line that says who reads it>"
},
"subscribe": {
"button": "<WRITE: a button, one to three words, saying what pressing it does>",
"description": "<WRITE: one or two short sentences>",
"encouragement": "<WRITE: one reassuring sentence: what happens with what they send, or how little it takes; or empty>",
"form_description": "<WRITE: one short line of guidance above the form, or empty>",
"form_title": "<WRITE: a title for the form, two to four words>",
"heading": "<WRITE: a heading, at most eight words, saying what the reader gets>",
"hints": {
"email": "<WRITE: an example answer for the field email, as a placeholder; or empty>",
"name": "<WRITE: an example answer for the field name, as a placeholder; or empty>"
},
"icon": "<WRITE: an icon name from the list at the end, the one that fits this best; or empty>",
"labels": {
"email": "<WRITE: a form label for the field email>",
"name": "<WRITE: a form label for the field name>"
},
"road_description": "<WRITE: one or two sentences walking the reader through the stages this goes through, in order (the stages are listed above), in their words>",
"road_icon": "<WRITE: an icon name from the list at the end that fits this section; or empty>",
"road_title": "<WRITE: a short title, two to four words, for the line that says what happens after sending>",
"who_description": "<WRITE: one sentence: who reads what they send, and how to reach them meanwhile>",
"who_icon": "<WRITE: an icon name from the list at the end that fits this section; or empty>",
"who_title": "<WRITE: a short title, two to four words, for the line that says who reads it>"
}
},
"question": "<WRITE: the one question this page asks its reader>"
}
Reply with the JSON object only.
=== REPLY ===
{
"description": "Three ways to be part of what UHHM builds: work with us, hear from us, or fix something on this site.",
"needs": {
"collaborate": {
"button": "Get in touch",
"description": "You want to build software with people who read the whole brief, not just the summary.",
"encouragement": "A person reads this, not a form filter — worth the ten minutes.",
"form_description": "Tell us who you are and what kind of work you're after.",
"form_title": "Say hello",
"heading": "Work with people who read the whole thing",
"hints": {
"email": "you@example.com",
"interest": "Backend work, or something design-heavy",
"name": "Your name",
"note": "A bit about what you'd want to work on, or a link to your work"
},
"icon": "handshake",
"labels": {
"email": "Email",
"interest": "What kind of work",
"name": "Name",
"note": "Tell us more"
},
"road_description": "We read what you send and get back to you. If there's a fit, we invite you in and you start working with us — and if things ever change, that's fine too.",
"road_icon": "route",
"road_title": "What happens next",
"who_description": "One of the owners reads this directly — for anything urgent, write to bl@uhhm.no.",
"who_icon": "user-check",
"who_title": "Who reads this"
},
"propose": {
"button": "Send change",
"description": "You've spotted something on this site that should read differently, and you know roughly how.",
"encouragement": "Even a rough version helps — we can tidy the wording ourselves.",
"form_description": "Point us to the page and show us the change.",
"form_title": "Propose a change",
"heading": "Get a page fixed the way you'd write it",
"hints": {
"email": "you@example.com",
"page": "questions/join/index.yaml",
"proposed_yaml": "heading: \"A clearer way to say this\"",
"rationale": "The current heading doesn't say what you actually get",
"submitted_by": "Your name"
},
"icon": "pencil",
"labels": {
"email": "Email",
"page": "Which page",
"proposed_yaml": "Your proposed text",
"rationale": "Why this is better",
"submitted_by": "Your name"
},
"road_description": "Someone here reads your proposal and either makes the change or explains why not. Either way, you'll hear back.",
"road_icon": "route",
"road_title": "What happens next",
"who_description": "An owner reads every proposal before anything changes — reach us at bl@uhhm.no if it's time-sensitive.",
"who_icon": "user-check",
"who_title": "Who reads this"
},
"subscribe": {
"button": "Sign up",
"description": "You'd rather hear from us now and then than check back on your own.",
"encouragement": "One click unsubscribes you later, no questions asked.",
"form_description": "Just your email, or your name too if you'd like.",
"form_title": "Stay in the loop",
"heading": "Hear from us only when there's something to say",
"hints": {
"email": "you@example.com",
"name": "Your name"
},
"icon": "mail",
"labels": {
"email": "Email",
"name": "Name"
},
"road_description": "You're on the list. We write when there's something worth saying, and you can leave the list whenever you like.",
"road_icon": "bell",
"road_title": "What happens next",
"who_description": "An owner sends these notes directly — write to bl@uhhm.no if you'd rather ask something first.",
"who_icon": "user-check",
"who_title": "Who reads this"
}
},
"question": "How do you want to be part of this?"
}