4 Commits

Include renames

Author	SHA1	Message	Date
Bendik Aagaard LynghaugandClaude Fable 5.1	e67e841f8c	Question nav: a followup is offered only once it is earned ... The 0.3.34 rule listed every followup "further down" from the current page, so the front door offered the thank-you pages before anything was submitted, and a followup one typed in offered the ones beyond it. The chain half was weaker than it looked too: it matched the question the chain answered, which is a front door anyway. Now a followup is offered only when the visitor has earned it: their verified chain answered the alternative that leads there (the chain index records the alternative from here on; older nodes fall back to every recording alternative of the answered question, and nothing beyond it), or it hangs off an earned page by a link that records nothing. A page behind an answer they have not given is never offered. The walk ends at any front door, so "back to the start" never fans out. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L4jrCgLiKKHAEFuZUJjckH	2026-09-22 16:58:40 +02:00
Bendik Aagaard LynghaugandClaude Fable 5	452ea88fbf	Filesystem routes, sections, dynamic segments; instant YES hero ... The questions/ tree is the router now: ids derive from file paths (index.yaml names its directory; explicit id still wins for legacy content), actions and requires_chain accept relative refs, nested non-index files infer followup, and _section.yaml applies qualifies/ requires_chain/responsible to everything under its directory. Dynamic [name].yaml pages serve any /dir/<value> with the segment substituted into {name} resource-key placeholders; submissions index their chain node in a portal_chains KV so requires_chain pages can verify a visitor's ?chain= lineage actually ends at the required question. Loading uses one recursive git-trees call; question_lint walks subdirectories the same way. Implements docs/design/filesystem-routes.md. Also: the YES hero now starts at HTML parse time via an inline module script (yes.js moved to public/ for a stable /yes.js the wasm binding raw_module-imports too - snippet paths are per-build-hashed), with hydration adopting the running instance; and both gesture containers reserve their box in CSS so mounting doesn't shift content. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-24 22:30:28 +02:00
Bendik Aagaard LynghaugandClaude Sonnet 5	6932816c42	Lighten the comment load ... Drops porting-history narratives (dodrenett), superseded-behavior explanations, and restatements of what the next line does. Constraint notes (fail-closed policies, CAS semantics, cascade behavior, id uniqueness) stay, just shorter. No code changes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-08-12 22:55:36 +02:00
Bendik Aagaard Lynghaug	aa1a7fa572	Initial commit: content-driven onboarding portal ... Leptos/Axum app that renders a Question/Alternative/Feature schema loaded from a sibling content repo (portal-content). Kanidm OIDC login, content-driven authorization (Question.qualifies), a generic NATS KV-backed resource + state-transition mechanism (no bespoke "applicant" concept baked into the runtime - it's all content), a SHA-256 DAG chain tying submissions and decisions together, and the "YES - Rasterized Lines" piece (ported from the live uhhm.no site) as the landing hero.	2026-07-29 19:38:40 +02:00