portal/runs/uhhm-2026-09-23/site/llm/04-questions_index.yaml.md

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/index.yaml It is the front door: the first page any visitor sees. question is the page's one question. Under doors, each entry is one alternative that leads to a page of its own for one kind of visitor: its heading must let that visitor recognise themselves from the heading alone. Under needs, each entry is one alternative with a 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:

• question is 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>", "doors": { "build": { "button": "<WRITE: a button, one to three words, saying what pressing it does>", "description": "<WRITE: one or two short sentences>", "for_whom": "<WRITE: a few words naming who this is for, addressed to them; or empty>", "heading": "<WRITE: a heading, at most eight words, saying what the reader gets>", "icon": "<WRITE: an icon name from the list at the end, the one that fits this best; or empty>" }, "join": { "button": "<WRITE: a button, one to three words, saying what pressing it does>", "description": "<WRITE: one or two short sentences>", "for_whom": "<WRITE: a few words naming who this is for, addressed to them; or empty>", "heading": "<WRITE: a heading, at most eight words, saying what the reader gets>", "icon": "<WRITE: an icon name from the list at the end, the one that fits this best; or empty>" } }, "needs": { "custody": { "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": { "about": "<WRITE: an example answer for the field about, as a placeholder; or empty>", "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>", "what": "<WRITE: an example answer for the field what, 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": { "about": "<WRITE: a form label for the field about>", "email": "<WRITE: a form label for the field email>", "name": "<WRITE: a form label for the field name>", "what": "<WRITE: a form label for the field what>" }, "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": "UHHM builds software for organisations that can say what problem they have, and keeps the redoal network underneath.",
  "doors": {
    "build": {
      "button": "Start here",
      "description": "Send us the problem, or try your own workflow as a working site before you pay for anything.",
      "for_whom": "For an organisation with a problem, or a business sizing us up",
      "heading": "Get software built around your problem",
      "icon": "hammer"
    },
    "join": {
      "button": "Start here",
      "description": "Build with us, hear from us now and then, or tell us what should change on this page.",
      "for_whom": "For anyone who wants in, on their own terms",
      "heading": "Work with us, or just stay in touch",
      "icon": "handshake"
    }
  },
  "needs": {
    "custody": {
      "button": "Send to a custodian",
      "description": "For anyone who runs on, builds on, or is affected by the redoal network and needs to reach the people who keep its first node.",
      "encouragement": "A custodian reads every message that comes in here.",
      "form_description": "Tell us what the network is doing, or not doing, and how we can reach you.",
      "form_title": "Reach a custodian",
      "heading": "Get an answer from the people who keep the network",
      "hints": {
        "about": "We run our order system on a relay node and it's been dropping messages since Tuesday",
        "email": "you@yourcompany.com",
        "name": "Your name",
        "what": "A relay node is misbehaving"
      },
      "icon": "shield",
      "labels": {
        "about": "What's going on",
        "email": "Email",
        "name": "Name",
        "what": "In short"
      },
      "road_description": "We open it and start a dialogue with you. Once we understand what the network is keeping that it shouldn't, we work it through to resolved, or tell you plainly if we can't.",
      "road_icon": "route",
      "road_title": "What happens next",
      "who_title": "Who reads this",
      "who_icon": "user-check",
      "who_description": "A custodian reads it directly; if it's urgent, write to bl@uhhm.no in the meantime."
    }
  },
  "question": "What brings you here?"
}