drksci
Search
Concepts / Concept
Concept · Spatial · 2026

Yonda

The Invisible Passenger

SpatialAudioMobilePostGISICIP
The premise
The road has context. It should not require another screen to reveal it.

Yonda proposes a spatial publishing system for regional travel. It is documented as a concept and product direction, not as a claim that the proposed services, pilots or integrations are already live.

The proposition

A traveller moves through a landscape already dense with history, ecology, work and living culture. Most travel software asks them to stop, search and read. Yonda reverses that interaction: a Trigger Zone can make approved material available as the traveller enters a place, leaving attention where it belongs — on the road or the walk.

The interface is not a map full of pins. It is a decision about when a place has earned the right to speak.
Zero-touch listening
Narration is proposed to start from location and journey context, rather than a driver operating a screen while moving.
Network resilience
A Trajectory Corridor can request material ahead of the traveller across Spatial Partitions, so intermittent regional coverage is treated as a design condition.
Cultural stewardship
First Nations and Indigenous Cultural Custodians are proposed as the authorities for review and publication of culturally sensitive material; no sensitive content is assumed publishable by default.

A concept system map

The interactive Archify system map follows the same documented responsibilities. It is a concept view, not a claim that the architecture is deployed.

diagram

From place to playback

  1. Travellerjourney context
  2. Mobile clientzero-touch request
  3. Trajectory CorridorSpatial Partitions ahead
  4. Spatial knowledge storeprovenance + permissions
  5. Audio-Loomnarration + ambience

Read as: A traveller supplies journey context; the mobile client requests material ahead; the spatial store returns approved records; an Audio-Loom combines them for listening.

A concept-level sequence derived from the supplied Yonda product documents. It names intended responsibilities, not deployed infrastructure.

What is known, and what is not

Evidence boundary

ItemCurrent reading
Product framingDocumented in the supplied Yonda vision, persona, journey and roadmap material.
Technical directionThe repository describes a Flutter client, Directus/PostGIS CMS, geohash-oriented APIs and an Audio-Loom approach.
Field outcomeNot evidenced here. No claim is made about listener retention, safety outcomes, cultural approval, coverage or a live corridor.
Next testA consented Journey Loop pilot with named custodial governance, an explicit audio corpus and a recorded offline-coverage test.
Documented
The core mission, four product axioms, personas, journey sketches and roadmap are stated in the supplied Yonda repository documentation.
Assumed for the concept map
The diagram connects documented responsibilities into one conceptual system view. It does not demonstrate an operating service or data path.
Not yet evidenced
No field trial, listener outcome, offline-coverage result, cultural approval or commercial deployment is established by the supplied material.

ScopeThis article treats the supplied project documentation as source material. It does not independently verify the proposed integrations, locations, commercial partners or cultural protocols.

An authoring contract for future concepts

A concept page is useful only if a reader can tell the difference between a source-backed fact, a design choice and an open question. The prompt below is a reusable brief for turning a PRD, vision, pilot note or system proposal into an article in this collection.

LLM article-authoring prompt
Write a d/rksci Concept article from the supplied source material.
Inputs: work type; title; status (Concept, WIP, Deployed or Retrospective);
source links/notes; known facts; open assumptions; review state; available media;
and the intended reader.
Rules:
1. Lead with a precise, plain-language proposition. Do not invent metrics,
pilots, partners, product status, research or deployment details.
2. Separate documented facts, intended mechanism and unresolved questions.
3. Explain inputs, transformation, decision and output. Name failure modes.
4. Use the project’s canonical vocabulary. Do not name external shows as features.
5. When Indigenous knowledge is involved, state review authority and omit
sensitive detail unless explicit publication approval is supplied.
6. Recommend a diagram only for a real relationship, sequence or boundary.
7. For each media item provide: caption, source, date, rights and alt text.
Treat unavailable media as a placeholder, never as evidence.
8. End with what would change the article and the next evidence needed.
Return: a fact/assumption ledger, an asset manifest and article copy.
  • Use original maps, field photographs, interface captures, audio excerpts or a diagram only when they make a claim easier to inspect.
  • Caption media with what it shows, its source, date, rights and limitation. Generated imagery must not impersonate field evidence.
  • State the work’s actual status and evidence boundary; category membership must not imply maturity or validation.

Source record

  1. Yonda Product Vision: The Invisible Passenger
    context · internal · docs/product/vision.md · as of 2026-08-25
  2. Yonda User Personas and Target Segments
    context · internal · docs/product/personas.md · as of 2026-08-25
  3. Yonda End-to-End User and Creator Journeys
    context · internal · docs/product/journeys.md · as of 2026-08-25
  4. Yonda Outcome-Based Product Roadmap
    context · internal · docs/product/roadmap.md · as of 2026-08-25

Source material: supplied Yonda repository documentation — Product Vision, Personas, Journeys, Roadmap and project guidance — inspected 25 August 2026.