Skip to route content
Hara
Open live review
Implemented

Architecture · validation · adoption

One route catalogue and one review procedure.

The guide makes route relationships, navigation ownership, route states, provenance, themes, responsive behavior and downstream responsibility reviewable from one place—without flattening every Hara site and tool into the same information architecture.

Review a live routeRead first findingsAdd an application

Manifest and route inventory

Every current route has one place in the review matrix.

The fourteen closeout routes are represented exactly once. Current extensions and historical studies remain visible below without competing with the primary catalogue.

Required routes14Issue 44 inventory
Theme × viewport cells1402 themes · 5 widths
Review checks11Per route and state
Manifest-backed14/14Catalogue home is the manifest root
14 routes
RouteGroupPrimary taskRequired statesAuthority evidenceDownstream
Catalogue home/ CatalogueCatalogue landing Understand the route families and choose a detailed reference.
loadingemptyerrordisabledsuccessplanned-routeactive-routesettled-route
 Typed route manifest and implementation issue relationships. All Hara interface consumers
Foundations/foundations/ FoundationsDocument catalogue Inspect identity, tokens, type, material, motion and accessibility contracts.
loadingemptyerrordisabledsuccessselected-tokenreduced-motiontheme-parity
 Protected package tokens and shared identity invariants. Every downstream product
Components/components/ LibraryInventory and composition Find a public primitive and inspect its states and ownership.
loadingemptyerrordisabledsuccessselectedpressedvalidationasync-feedback
 Public package export inventory and exact source paths. Every downstream product
UI patterns/ui/ LibraryWorkflow reference Review reusable behavior over time without importing product business rules.
loadingemptyerrordisabledsuccesspartialstaleofflinereconnectingpermission-deniedrevoked
 Shared interaction contract and product-owned rule boundary. Every downstream product
Front matter/frontmatter/ FoundationsContent-contract registry Inspect author, registry, identity, runtime and source-controlled fields.
loadingemptyerrordisabledsuccessvalidinvalidmigratedimportedsupersededwithdrawn
 Public hara.* content contracts, exact schema versions and receipts. All content-producing products
Tool workbenches/tool/ LibraryViewport-first workbench Manipulate and inspect a durable primary surface while secondary panes yield.
loadingemptyerrordisabledsuccessselectedpressedcapability-unavailableconnection-requestedconnection-actual
 Stateless Astro primitives and package-owned workbench geometry. Playground, editors and browser tools
WWW/www/ ApplicationsPublic narrative Understand Hara through bounded claims, proof and executable examples.
loadingemptyerrordisabledsuccesslow-bandwidthruntime-unavailablestale-release
 hara.www claims linked to Specs, Packages, Benchmarks and executable proof. hara-www
Docs/www/docs/ ApplicationsPersistent reading shell Find guidance or reference and optionally run a fenced example.
loadingemptyerrordisabledsuccessno-search-resultsversion-staleruntime-unavailableread-only
 hara.docs content identity, version range, symbols and runtime example revision. hara-docs
Benchmarks/www/benchmarks/ ApplicationsEvidence command board Read an insight, inspect the selected evidence and verify its method.
loadingemptyerrordisabledsuccessmissingincomparablepartiallow-confidence
 Workload, baseline, methodology, environment and exact evidence revision. hara-benchmarks
Playground/playground/ ApplicationsExecutable studio Load exact source, run it and inspect session and observation state.
loadingemptyerrordisabledsuccessrunningcancelledrestartedreplaceddisposedbackend-unavailablestale-link
 Session identity, generation, source revision, backend, capabilities, events and receipts. Playground and Docs live embeds
Specs/specs/ ApplicationsRegistry, reader and checker Find an exact standard, inspect authority and evaluate fenced evidence.
loadingemptyerrordisabledsuccessdraftproposedacceptedsupersededwithdrawnexperimentalunsupportedunavailable
 Specification identity, exact version, source revision, checker implementation and receipt. hara-specs
Packages/packages/ ApplicationsRegistry and publication product Find, evaluate, install, publish and maintain packages and namespaces.
loadingemptyerrordisabledsuccessstale-indexregistry-degradedinstall-failuredeprecatedsupersededwithdrawnrevoked
 Coordinates, release revision, artifacts, namespace stewardship, compatibility and publication receipt. Package and namespace registry product
World/world/ ApplicationsCommunity reader Read source-aware community material and participate in accountable discussion.
loadingemptyerrordisabledsuccesspartial-sourcestale-feedmoderateddeletedowner-awaypresence-hidden
 Canonical source, retrieval, syndication, moderation, contributor and bot-owner evidence. hara-world
Learn/learn/ ApplicationsCurriculum and lesson product Run a visible lesson, follow a concept graph and record meaningful progress.
loadingemptyerrordisabledsuccessanonymouscurrentlockedoptionallocal-passverifiedversion-changedruntime-unavailable
 Exact curriculum, lesson, exercise, project, attempt and completion revisions. learn.hara-lang.org
Current extensionsAdditional active review routes
current-extensionGraphics
/graphics/

Raster fields, material textures and progressive shader surfaces.

Parent · Foundations
compatibilityAgent-first Start
/start/

Agent-first discovery and Habitat study with a canonical Learn relationship.

Parent · Learn
current-extensionWorld discussion
/world/discussion/

Focused article, clipping, comment, profile and presence study.

Parent · World
current-extensionAround Hara
/world/around/

External discovery, provenance, moderation and relay study.

Parent · World
current-extensionHara Chrome
/tool/hara-chrome/

Browser runtime and bounded diagnostics application study.

Parent · Tool workbenches
Historical and compatibilitySecondary by design
historicalCommunity reader study
/world/community/

Retained under Learn for comparison, not a primary World destination.

Canonical relationship · /learn/studies/world-community/
historicalProgrammer onboarding study
/world/onboarding/

Retained as a Learn teaching study, not active World navigation.

Canonical relationship · /learn/studies/programmer-onboarding/
historicalWorld feed infrastructure study
/world/feed/

Retained implementation evidence for source normalization, clustering and relay.

Canonical relationship · /learn/studies/world-feed/

Issue 44 · first matrix pass

Record defects before declaring routes accepted.

Every matrix cell is structurally enumerable and contract-testable. Manual pixel and assistive-technology observations remain required before issue #44 closes.

Required routes14Manifest-backed
Review cells1402 themes × 5 viewports
Common checks11Per exact target
First defects44 resolved in this PR
Manual observations140Still required for #44 closeout
high A11Y-001 keyboard resolved-in-pr

All catalogue routes

The shared catalogue masthead had no direct skip path past global, family and on-page navigation.

Resolution
Add one keyboard-visible skip link and one stable focus target immediately before route-owned content.
Evidence
CatalogueMasthead.astro + CatalogueHeader.astro
high TOUCH-001 responsive resolved-in-pr

840 px, 560 px and minimum-width navigation

Shared family tabs, parent links and section links used 34–42 px targets at touch widths.

Resolution
Raise shared touch navigation targets to at least 44 px without changing desktop density.
Evidence
v2-matrix-regression-fixes.css
medium ANCHOR-001 navigation resolved-in-pr

Deep route section anchors

Sticky catalogue and section navigation could cover the heading selected by an in-page fragment.

Resolution
Apply shared scroll margin for route-owned section and article anchors with a narrower mobile offset.
Evidence
v2-matrix-regression-fixes.css
medium EVIDENCE-001 provenance resolved-in-pr

Live guide review deck

A reviewer could mark checks locally but could not export an exact route/theme/viewport evidence record.

Resolution
Add a non-persistent JSON evidence export containing target, decision, checked contract items, issue reference, notes and guide revision.
Evidence
GuideReviewEvidence.astro + v2-guide-review-export.js

Live route review deck

One route, two themes, five exact widths.

The same-origin preview changes route, theme and viewport without rewriting the parent page preference. Review marks are local to this browser session and do not claim external certification.

Theme
Viewport
Open route
Desktop · 1440 × 900Light theme
Per-target checklist

Eleven questions before acceptance

Evidence export

Turn the current local decision into a fenced record.

JSON · local download
Nothing is uploaded or persisted by this guide.

Catalogue architecture

Four navigation layers. Four ownership layers. No ambiguous middle.

The guide separates where the reviewer is, what the product owns, which controls belong to the demonstrated application and which facts remain authoritative outside Visual Language.

01

Visual Language

Global catalogue

Block-H masthead and Browse launcher

Knows route groups and current location; never absorbs product workflows.

02

Visual Language manifest

Route and family

Breadcrumb, family tabs, status, neighbours and footer

Derived from one route manifest rather than page-local arrays.

03

Application reference

Application-local

Registry, lesson, checker, feed, editor or publishing sections

Names only the workflow owned by that product.

04

Downstream product

Demonstrated product

Embedded app toolbar, tabs, inspector and commands

Must be framed as specimen chrome and cannot masquerade as catalogue navigation.

package

Shared package

Owns

Tokens, type, surfaces, focus, state grammar, stateless components and workbench geometry.

Does not own

Product data, registry decisions, runtime behavior and business rules.

catalogue

Catalogue composition

Owns

Route relationships, review specimens, fixture disclosure and cross-product comparison.

Does not own

Production accounts, authoritative content, moderation, evaluation or publication.

product

Product application

Owns

Information architecture, commands, preferences, forms, local navigation and task composition.

Does not own

Facts controlled by identity, source, registry, reviewer or runtime authorities.

authority

Registry and runtime

Owns

Canonical identities, revisions, capabilities, checks, decisions, artifacts, observations and receipts.

Does not own

Presentation-only claims or visual-language fixture data.

Page anatomy

The same route shown as responsibility bands

Application-local navigation may look different across Specs, Playground, World and Learn. Its placement in the ownership stack does not change.

Global Block-H · Browse · Source · Theme Route Breadcrumb · Family tabs · Status · Product actions Application-local Registry / Lesson / Feed / Workspace / Publish Primary task The route’s durable reading, editing, comparing or execution surface Secondary Outline · Inspector · Capability pane · Evidence ledger Authority Identity · Source · Registry · Reviewer · Runtime · Receipt
Route lifecycle

Plan, activate, settle, retain or deprecate explicitly.

  1. 01
    Planned

    Links to the implementation issue; no shallow placeholder route.

    Entry
    Issue-backed manifest record
    Exit
    Detailed route and focused tests exist
  2. 02
    Active

    Primary navigation and current-route treatment.

    Entry
    Current internal route on main
    Exit
    Contract is stable or route is replaced
  3. 03
    Settled

    Still supported; change requires compatibility review.

    Entry
    Stable reusable contract
    Exit
    Explicit supersession only
  4. 04
    Historical

    Secondary Learn/reference link; never competes with the current product route.

    Entry
    Replaced study remains useful
    Exit
    Removal policy and redirects are documented
  5. 05
    Deprecated

    Retain exact reason, replacement and compatibility period.

    Entry
    Replacement and migration path exist
    Exit
    Removal release
Adding an application

One route record, one route boundary, one complete state model.

  1. 01

    Create an executable issue with outcome, scope, acceptance criteria, validation, relationships, readiness and delivery.

  2. 02

    Add one typed manifest record; planned routes point to the issue until a detailed route exists.

  3. 03

    Declare the route boundary, local information architecture, authoritative data sources and downstream target.

  4. 04

    Consume shared components, UI patterns and content contracts without redefining protected tokens.

  5. 05

    Build realistic landing, deep-work, degraded, responsive, light/dark, keyboard and reduced-motion states.

  6. 06

    Add focused contract tests, package documentation impact and a downstream adoption note.

  7. 07

    Validate the exact branch with repository-wide tests, static build and the live review matrix before merge.

Review procedure and adoption

Review the exact route. Adopt the merged contract. Keep authority downstream.

Screenshots and live previews are evidence for a precise revision. Downstream repositories remain responsible for product behavior, authoritative data and their own integration tests.

Screenshot and accessibility procedure

Eight repeatable steps

The live deck makes the target deterministic; the durable review record still names the PR, SHA, route, theme, viewport, state and observed result.

  1. 01

    Build the exact branch and serve the static output; record the branch SHA and route revision.

  2. 02

    Open each required route in explicit light and explicit dark themes.

  3. 03

    Capture 1440×900, 1024×900, 680×860, 390×844 and 320×720 frames without resizing between interaction states.

  4. 04

    Exercise keyboard navigation, visible focus, disclosures, local overflow and one representative product mutation before capture.

  5. 05

    Capture loading, empty, error, disabled and success plus every route-specific degraded or lifecycle state named in the matrix.

  6. 06

    Record contrast, reduced-motion, no-hover and source/provenance observations beside the image rather than relying on visual memory.

  7. 07

    Store screenshots as review evidence, not package assets; link the exact PR, SHA, route, theme, viewport and state.

  8. 08

    Treat a changed route, token, shell or state contract as invalidating the affected evidence until it is reviewed again.

Current guide

WWW

Narrative, proof, release and getting-started composition.

Visual route
/www/
Target
hara-www
Adoption guide
V2-WWW.md
Current guide

Docs

Guides, reference, search and embedded live examples.

Visual route
/www/docs/
Target
hara-docs
Adoption guide
V2-WWW.md
Current guide

Benchmarks

Evidence, workloads, methods, environments and result history.

Visual route
/www/benchmarks/
Target
hara-benchmarks
Adoption guide
V2-WWW.md
Current guide

Playground

Execution, session lifecycle, sharing and embed runtime behavior.

Visual route
/playground/
Target
Playground/live-component repositories
Adoption guide
V2-PLAYGROUND.md
Current guide

Specs

Canonical standards, proposals, review and conformance authority.

Visual route
/specs/
Target
hara-specs
Adoption guide
V2-SPECS.md
Current guide

Packages

Package/namespace registry, release, compatibility and provenance.

Visual route
/packages/
Target
package registry product
Adoption guide
V2-PACKAGES.md
Current guide

World

Public reading, source discovery, discussion, profiles and accountable bots.

Visual route
/world/
Target
hara-world
Adoption guide
V2-WORLD.md
Current guide

Learn

Curriculum, lessons, practice, projects and private progress.

Visual route
/learn/
Target
learn.hara-lang.org
Adoption guide
V2-LEARN.md
Release and compatibility impact

The guide adds review infrastructure, not product runtime.

Package exports
No new runtime or component export is required for the guide. V2-GUIDE.md is included in the published documentation set.
Route impact
Adds /guide/ as a current Foundations route and a permanent Catalogue guide link in page footers.
Downstream
Adoption pull requests remain independent and pin only merged Visual Language revisions.
Compatibility
V1 and all existing v2 imports, routes and historical studies remain available.
Next visual-guide domains

The catalogue can now grow without adding another review grammar.

Data visualisation

Charts, matrices, timelines, uncertainty, missing values and accessible evidence alternatives.

Issue 91 →
Diagrams and architecture

Data flow, sequence, state, package graphs and explanatory annotations.

Expansion epic →
Iconography and symbols

Navigation, action, state, capability and product glyph contracts.

Expansion epic →
Delivery media and motion

Email, print, social, low-bandwidth projections and reduced-motion-equivalent choreography.

Expansion epic →