website/design/roadmap-vision
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-09-27 01:23:03 +02:00
..
screens Extend the design vision to the contract lab and settlement stages (#64) 2026-09-15 19:54:34 +02:00
acceptance-qa.html Add roadmap design vision mockups for the planned stages (#61) 2026-09-15 17:34:32 +02:00
artifact-receipts.html Add roadmap design vision mockups for the planned stages (#61) 2026-09-15 17:34:32 +02:00
fair-settlement.html Extend the design vision to the contract lab and settlement stages (#64) 2026-09-15 19:54:34 +02:00
index.html Connect the public home to the Laboratorium 2026-09-27 01:23:03 +02:00
project-coordination.html Add roadmap design vision mockups for the planned stages (#61) 2026-09-15 17:34:32 +02:00
README.md Extend the design vision to the contract lab and settlement stages (#64) 2026-09-15 19:54:34 +02:00
solidity-lab.html Extend the design vision to the contract lab and settlement stages (#64) 2026-09-15 19:54:34 +02:00
vision.css Add roadmap design vision mockups for the planned stages (#61) 2026-09-15 17:34:32 +02:00

Roadmap design vision

Static interface concepts for the planned coordination roadmap stages (release criteria). They let participants review and discuss how stage 02–06 journeys could look and read before any schema or service work exists.

These are design candidates, not a live contract: they bind no API schema, contain only synthetic data, and are never copied into the production site (the build does not package design/). The current API contract remains site/data/commons-openapi.json.

Screens

File Stage Journey shown
index.html Overview Scope, per-screen questions and the criteria each screen addresses.
project-coordination.html 02 · Project coordination Portable hierarchy with dependent milestones, offer versus commitment, capability profile and explained matching.
artifact-receipts.html 03 · Artifact receipts One manifest card, CID versus raw-file digest as separate verification paths, and the matched/mismatched/absent/stale states.
acceptance-qa.html 04 · Acceptance & QA Policy-upfront card, the delivery → revision → delivery → acceptance trail with bound decisions, and the refused states.

Every card carries a Criteria addressed note linking the visual to the exact release criteria it illustrates, so a design discussion can be checked against the roadmap instead of drifting into implied features.

Rendered previews

Captured locally on 15 September 2026 from the pages as committed (dark theme, 1280 px, unless noted). If a screen changes, re-capture the affected image so the previews stay truthful.

Preview What to look at
Overview screen listing the three stage concepts with their design questions Overview: per-stage design questions and the criteria each screen addresses.
Project coordination screen with the mission, project and two dependent milestones Stage 02: the portable hierarchy; note the explicit blocked by dependency gate.
Offer card beside a pink bound commitment card with participants, scope and terms Stage 02: offer versus commitment — outline card against pink bound card; below the tree, matching explains itself.
Delivery manifest card with author, separated timestamps, location and access conditions Stage 03: one manifest card; submission time and established creation time as two distinct facts.
Four verification state cards: matched, mismatch, absent, stale revision Stage 03: every state pairs color with words; a stale revision never reads like a success.
Acceptance timeline with four steps, bound decisions and the threshold indicator Stage 04: the decision trail; each decision binds the exact delivery and criteria versions.
Receipts screen in bright theme with identical layout Bright theme: same layout, swapped color roles.
Acceptance timeline at 390 px width in a single column Mobile 390 px: single column, stacked threshold indicator.
Requirements-first wizard card of the contract lab screen Stage 05: the builder asks before it writes; the lab's refusals (key collection, deployment) are drawn states.
Agreement card and the seven defined settlement outcomes Stage 06: agreement before work; every outcome defined before implementation.

Viewing

Open the files directly in a browser, or serve the folder:

python3 -m http.server --bind 127.0.0.1 4210 --directory design/roadmap-vision

Then open http://127.0.0.1:4210/. Static pages: no JavaScript, no requests, no storage. Dark is the default theme; bright mode mirrors the production theme switch — edit data-theme="dark" to bright on the <html> element (or flip it in the devtools) and reload.

Review checklist

When comparing or discussing these concepts:

  • Both themes: dark and bright read as the same layout with different color roles.
  • Narrow widths down to 320 px stay single-column and readable; definition grids collapse.
  • Keyboard only: every link is reachable, :focus-visible is visible on every interactive element.
  • Reduced Motion: pages are static by design; no animation is required for meaning.
  • No meaning by color alone: every state badge pairs color with words.
  • Synthetic participants and identifiers are labelled as such on every screen.

Design language

vision.css mirrors the production variables from site/assets/styles/site-v2.css (color roles, --radius, --max, Inter). A screen that is later selected for implementation should be rebuilt as a real page fragment inside the production build — these files are development inputs, following the same boundary as the Motion Lab.