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
19 lines
983 B
Plaintext
19 lines
983 B
Plaintext
words: questions/counter/index.yaml
|
|
words: questions/firms/index.yaml
|
|
words: questions/hiring/index.yaml
|
|
words: questions/index.yaml
|
|
words: questions/office/index.yaml
|
|
words: questions/received/account-request.yaml
|
|
words: questions/received/breakdown.yaml
|
|
words: questions/received/hire-request.yaml
|
|
words: questions/yard/damage-on-return-sent.yaml
|
|
words: questions/yard/damage-on-return.yaml
|
|
words: questions/yard/index.yaml
|
|
content repo written to runs/hire-2026-09-22
|
|
OK: 11 question(s), 5 aggregate(s) valid
|
|
need "hire-request": / [Need a machine for a while?] -> /hiring [Hire a machine for your job] -> "hires"
|
|
need "breakdown": / [Need a machine for a while?] -> /hiring [Machine has stopped working] -> "breakdowns"
|
|
need "account-request": / [Frequent hire? Set up an account] -> /firms [Set up a firm account] -> "accounts"
|
|
need "damage-on-return": /yard/damage-on-return [Record damage on return] -> "damage_reports"
|
|
OK: 4 need(s) structurally met, 0 planned, 7 persona(s)
|