Capabilities

Understand the help being imagined.

Explore the help Waymorrow is intended to offer, the behavior that would make it useful, and the limits still to be demonstrated.

Future direction · dated evidence

Understand the ambition and the record beside it.

The new guide uses concrete examples to explain the intended experience. The earlier Alpha register remains below, preserving its dates and limitations. Neither is a list of public features available today.

Project update ·

Building the foundation first.

Waymorrow remains Wayfinder Systems’ long-term flagship product direction. Following the October reset, current engineering is focused on making Wayforge and Abriella reliable enough to support that future work.

Earlier Waymorrow prototypes and Alpha plans have been archived. They remain useful development history, but their tests and milestones do not establish a current, ready-to-use application.

Read the October update → · See the Wayfinder project family →

The intended experience

What useful help should make possible

A capability matters when it helps someone understand a situation, make a choice or carry an idea forward. The following guide explains what Waymorrow is intended to help with and the behavior that would make that help worth trusting. The examples are hypothetical, offered to make the direction concrete.

These are future design directions, not available product features. Earlier private Alpha records are historical evidence of limited work, not proof of a ready public application. Current foundation work does not establish that Waymorrow can deliver these experiences. Public accounts, signup and hosted product access remain unavailable.

Future design direction

Give an unfinished thought somewhere to begin

People do not always arrive with a specification. Waymorrow is intended to help turn a loose concern into a clearer question, explore possible directions and define a useful next step. Abriella should make room for uncertainty before treating an idea as a task.

For example

Imagine saying, “I want to bring our scattered project notes together.” A useful response would clarify who needs them, what is missing and what a manageable first result might look like.

What useful behavior would require

  • Ask questions that change the next decision, rather than demanding every detail at once.
  • Offer alternatives with their tradeoffs and let you correct the objective.

The limit: A clearer objective is still yours to choose. Discussing an idea, comparing options or drafting a plan does not give permission to act.

Future design direction

Keep the conversation readable and connected

Abriella is intended to remain the human-facing guide as you move between destinations and return to earlier work. The conversation should be something you can read, question and revisit, with enough visible context to understand what a suggestion is based on.

For example

Imagine returning after a break. A helpful starting point would explain the last agreed direction, what remains unresolved and whether anything has changed, without pretending that a missing detail was remembered.

What useful behavior would require

  • Preserve your reading position when you review an earlier part of the conversation.
  • Accept corrections and make uncertainty about past context clear before relying on it.

The limit: Continuity is a design goal, not a promise of unlimited memory, reliable long-term recall or working continuity between hosted accounts.

Future design direction

Keep your place as an idea grows

The later design refinements favor a simpler dashboard with functional navigation and Abriella together with the conversation. The aim is to make your current context understandable while keeping the next useful choice easy to find. Moving between areas should preserve orientation rather than turn navigation into a task of its own.

For example

A small question might become a project over time. You should be able to find the question, related material and next decision, then return to the conversation without having to reconstruct what you were doing.

What useful behavior would require

  • Make your current location and the way back clear as you move between areas.
  • Keep navigation functional and conversation readable as the amount of work grows.

The limit: A visible workspace does not prove that work has been completed. Earlier spatial explorations and standalone visual checks do not demonstrate a current integrated application.

Future design direction

Understand what an answer rests on

Useful assistance needs more than a convincing answer. The direction separates contextual memory, candidate material, reviewed knowledge and supporting evidence, so that something mentioned in conversation is not silently treated as established truth. Relevant sources should help you inspect an answer and its limits.

For example

Imagine comparing two versions of a project brief. A useful explanation would identify their dates, show where they disagree and ask which version should guide the work when the record does not settle it.

What useful behavior would require

  • Distinguish a source statement from an inference or a suggestion.
  • Keep missing, conflicting or outdated information visible instead of smoothing it away.

The limit: Remembering or importing material does not make it accurate, approved or shareable. Historical Library work does not establish an available upload or research service.

Future design direction

Move toward work you can inspect and choose

The intended path connects a goal to proposed steps, candidate work and an understandable account of what was checked. Help should make a decision easier to assess. It should also leave room to revise the approach, pause or decline before a consequential action.

For example

For a proposed website change, you would need to see the draft, the affected pages and the checks that were actually run. Publishing would remain a separate decision with a clear scope.

What useful behavior would require

  • Describe what changed, what was checked and what remains uncertain in plain language.
  • Keep your permission tied to the action you actually chose.

The limit: A candidate, passing check or specialist opinion cannot supply human acceptance or permission to publish. Autonomous app-building reliability and a complete Waymorrow workflow are not established.

Future design direction

Shape the environment without losing control

An adaptive environment should become easier to use without becoming harder to understand. The design calls for understandable, reversible choices about layout, information density, motion and Abriella’s presence. Personalization should support attention and comfort while preserving a clear way to change your mind.

For example

Someone who prefers a quiet, text-led workspace should be able to reduce movement and visual density while keeping access to the same conversation, destinations and decisions.

What useful behavior would require

  • Explain meaningful changes and provide direct controls instead of relying on hidden adaptation.
  • Respect reduced motion and keep important information readable without animated presentation.

The limit: These are design requirements to demonstrate with people. Earlier settings screens do not prove accessibility, complete personalization or support for a particular device.

Future exploration

Explore other ways to interact carefully

Voice and richer forms of interaction raise a useful question: could another way to communicate make a particular moment easier? Any future approach should serve a clear human need, preserve the readable conversation and make its use and limits understandable.

For example

Speaking a rough idea might eventually be helpful when typing is inconvenient. You would still need to review what was understood, correct it and choose what happens next.

What useful behavior would require

  • Make activation and permission explicit, with a clear way to stop.
  • Retain a readable path for reviewing intent and consequential decisions.

The limit: No current Waymorrow voice, microphone, sensing or other multimodal experience is announced here. Earlier voice research does not establish availability or a delivery date.

The record should stay beside the ambition

The capability records below preserve what earlier private work investigated, the evidence dates and the conditions that limited it. They are useful history when kept at that scale. They should not be read as a list of features you can use today.

The next meaningful step is to demonstrate useful, reliable behavior before making new product commitments. That means checking what happens when context is missing, a person changes direction or something fails, as well as when a carefully prepared example succeeds.

Read the historical capability records and limits

Historical capability register

Read the earlier evidence in its original scope.

Select a category, then open any capability to see its requirements, limitations, evidence date, and Human decision boundary.

The capability ledger below preserves its earlier evidence dates. Its October status review marks the archived application records as historical. Newer Living Interface design direction does not upgrade any capability’s evidence status, public availability, or readiness. Voice and other future modalities remain separately gated.

Loading capabilities…

Understanding capability

A role, a capability, and authority are different things.

Scoped capabilities may support Abriella behind the conversation. The earlier Team records below preserve their evidence and limits; they are not a current persona-selection experience. Availability never creates authorization.

See the workflow

Human authority remains explicit

Person, role, capability, availability, assignment, and authority are separate states. No state silently promotes another.

Waymorrow Library captured 2026-09-05, cropped to category controls and default seed counts: 33 Knowledge Objects, 19 skills, and no candidates or Semantic Memory records.
Earlier Alpha interface · recorded September 5, 2026Cropped overview · native seed counts in synthetic demonstration state

Knowledge and context

Know what kind of information you are looking at.

The Library capture separates Knowledge Objects, sources, candidates, registered skills and contextual memory. Its seed counts are demonstration data.