Files
portal/runs/tomtervel-cards-2026-09-23
Bendik Aagaard LynghaugandClaude Fable 5.1 255aeb4f4b plan: intake to plan by a model; doors, labelled groups, the whole card
Work from another session, committed as found (tests green):

- `plan` reads an intake into a plan.yaml (a model decides needs,
  stages, forms and budgets; a person reads the result before build).
- Plans gain `doors` (a first question before the forms, when a front
  door would carry more than five needs), `groups` with labels that a
  select may draw its options from (`options_from: groups`), `private`
  fields kept off public pages, `multiple` selects, and `max_fields`
  as what the intake said the person will tolerate.
- `card.rs`: an alternative as the visitor meets it, in text, so the
  answering visitor and `rate` read the served card, not the heading.
- `rate` reads followup pages from the repo and reports "what happens
  next" as not measured rather than zero when it cannot.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L4jrCgLiKKHAEFuZUJjckH
2026-09-23 12:31:51 +02:00
..

Tomter Vel, the whole card worded, scored by a visitor who reads the whole card

Same plan as the day before (plans/tomtervel.yaml, 11 needs behind four doors, with nabohjelp), rebuilt after the builder learned to fill every part of a card and the scorers learned to read it. Claude Sonnet writing the words, 294 s for 27 pages, verifier green by construction. Visitor: qwen3:8b, one task per call, shown each option as portal renders it. This build is what vel.klingenbergbygg.no serves from 2026-09-23.

Visitor could read 2026-09-22 build (heading + description) This build (whole card)
Headings and descriptions 30 of 40 32 of 40
Headings only 28 of 40 29 of 40

Two more routed right with descriptions, one more on headings alone. Not a large move, and the headings-only figure says why: the front door's four door headings still do most of the damage. "Si din mening eller gi en hånd" took two traffic reports, two playground reports, a member with a new email and a waffle volunteer on headings alone. The card cannot help a visitor who only reads the heading, and the door headings are the plan's weakest words.

What the card does do shows in rate: with the whole card shown, "where" (do you know where you are, who this is for, and what the button does) is 2 of 2 on every page, and "asked" is 2 of 2 on every form page. The two context sections the plan supplies, "Hva skjer videre" and "Hvem ser dette", are what makes "next" 2 of 2 on the form pages.

One instrument note: "where" fails its control on three pages, where the gutted twin (which keeps the page's question) still got a yes. A question like "Hva har du sett i nabolaget som ikke er som det skal?" tells a visitor where they are on its own. Fair, and it means "where" is partly a property of the page question, not only the cards.

A card, as built (playground report, /melde-fra):

  • Få fikset noe som er ødelagt: Er noe på lekeplassen eller stien ødelagt eller farlig? Fortell oss hvor og hva, så tar lekeplasskomiteen tak i det.
  • Button: Meld fra. Det holder med noen få ord, så ser komiteen på det så fort de kan.
  • [wrench] Hva skjer videre: Meldingen går til lekeplasskomiteen, som tar tak i saken og utbedrer skaden.
  • [hammer] Hvem ser dette: Lekeplasskomiteen leser det du sender inn; til det haster kan du nå styret på post@tomtervel.no.
  • [construction] Meld fra om skade: Beskriv hva du så og hvor det er. Asks for: Hvor er det?; Hva har du sett? e.g. Løs planke i klatrestativet.