What Waymorrow is
A human-assistance platform built around Abriella, with conversation, Knowledge, roles, governed work, and evidence in connected surfaces. You retain final authority.
How it works · current Alpha interface
Waymorrow Platform Guide
Find your way around Waymorrow. Learn where to look, what each screen tells you, and where your decisions remain essential.
A visual, read-only guide to the captured Alpha. Public hosted application access is not available.
Orientation
A connected place for context, assistance, and human decisions.
Platform and Workspace
Platform is this website’s tour. Workspace is its future application gateway, currently unbound. Inside the Alpha interface, Workspace holds current work and evidence.
Who can use the interface
Application account access is Alpha-restricted. Public account creation, public sign-in, and hosted access are unavailable. These screenshots explain the interface; they do not open it.
Step-by-step usage
Read the screen before acting.
Each original capture has a plain-language reading key below it. Open an original image to zoom in. The controls pictured belong to the Alpha application; the images are not interactive demos.
01 · Orient yourself before deciding what needs attention.
Home / Action Center
Navigate here. Choose Home in the application’s bottom navigation. Home brings together Abriella, Conversation, the Objective candidate, and Action Center.
Look here first. Read the Objective status in the top bar, then Action Center on the right. This capture has no active Objective and nothing waiting for a decision.
- Left — Abriella’s presence panel shows her state, current workspace, and mode. The captured state is Idle in Companion mode.
- Center — Conversation is empty for this workspace and browser session. The message field sits below the Objective candidate; Start New Objective is the entry control for defining an outcome.
- Right — Action Center separates decisions and attention items. Its refresh control and Ask Abriella for a brief are visible; no response or decision is demonstrated here.
What the controls mean. The bottom tabs change application surfaces. Previous / Next and the page indicator belong to the current surface. Interrupt and Revoke Active Access are user-control affordances; this guide does not demonstrate their effects or ask you to activate them.
Your responsibility. You decide the intended outcome, what context to share, and whether any proposed work may proceed. A conversation is not approval.
Alpha limit. This is an idle Alpha capture. It demonstrates orientation and navigation, not a completed conversation, Objective, or decision.
02 · See the canonical roles and distinguish availability from active work.
Team
Navigate here. Choose Team in the bottom navigation, then Overview in the upper row.
Look here first. Read the summary above the role cards. The captured Team is available, has no governed assignments, and has not been evaluated for readiness.
- Upper row — Overview, People, and Coordination are separate views of the Team.
- Role cards — Abriella assists and guides; Luke is the Research and Evidence Specialist; Alexander is the Sandboxed Implementation Engineer; Gabriel is the Independent Verification Engineer.
- State line — Each role shows no current assignment. Availability alone does not mean work is authorized or running.
What the controls mean. Use People to inspect a role in detail. Coordination is visible as a navigation destination, but its detailed behavior is outside this capture set.
Your responsibility. Review the role, current assignment, and authority before relying on assistance. Specialist work needs its own scope, configuration, and authorization.
Alpha limit. No assignment, handoff, or specialist execution was created for these images.
03 · Understand Abriella’s role, current work, and human approval boundary.
Abriella
Navigate here. Choose Team → People, then select Abriella in the list on the left. Her conversational presence is also visible on Home.
Look here first. Start with Current Assignment, Current Work State, and Execution Authority in the detail panel.
- Left — The people list selects whose role and work details you are reading.
- Detail panel — Capabilities include conversation and clarification, navigation and guided capture, and governed workflow projection. Allowed Work is Unknown in this idle capture.
- Lower panel — Current Work has no active assignment. The Work Chat area says its composer appears when a canonical assignment is active; no active work conversation is shown.
What the controls mean. The boundary disclosure reveals additional role limits. Scroll within the detail pane to read its content; selecting a person does not grant execution authority.
Your responsibility. Human authority remains final. Review the explicit approval requirement and the no-implicit-approval boundary before advancing work.
Alpha limit. The screenshot is a role inspection with no assignment. It does not demonstrate an active work chat or autonomous execution.
04 · Read the current Objective and Plan context, then inspect readiness independently.
Mission / Readiness
Navigate here. Choose Mission in the bottom navigation. Overview introduces the current mission state; choose Readiness in the upper row for the screen shown here.
Look here first. Read Release Status before the readiness dimensions. The capture says Target · Not Readiness Approved.
- Upper row — Overview, Plan, Readiness, and History are distinct views. In the recorded Overview, no active Objective or roadmap is recorded, the workstream is not started, and approval is Not Requested.
- Release Status — A target is not a readiness approval. A calendar date cannot establish READY.
- Dimensions — Technical, Operational, Truth, and Human Outcome Intent are each Not Evaluated. Read them separately; an absent evaluation is not a pass.
What the controls mean. Overview’s Active Plan selector identifies the current plan context. Initialize Waymorrow Alpha Plan is visible in the recording, but was not activated. Plan and History are visible destinations; no plan approval or history operation is demonstrated.
Your responsibility. You remain responsible for approving work and assessing evidence. Neither a target nor a technical result grants release or acceptance.
Alpha limit. Only idle Overview and unevaluated Readiness were demonstrated. No successful execution, approved release, or completed readiness gate is implied.
Mission Overview in the recorded tour, at 00:28
Related screen: Workspace / Current Work →05 · Distinguish organized Knowledge, candidate material, skills, and contextual memory.
Library / Semantic Memory
Navigate here. Choose Library in the bottom navigation. Overview shows the category controls and counts. Choose Semantic Memory in the upper category rows to inspect memory state.
Look here first. Read the category labels before interpreting any count. The overview contains native seed Knowledge Objects and skills, while candidates and Semantic Memory are empty.
- Category rows — Overview, Search, Knowledge Objects, Sources, Candidate Queue, Skills, Audit, and Semantic Memory identify different kinds of information.
- Overview counts — The recorded 33 Knowledge Objects, 19 skills, and two relationships are native demonstration seeds, not customer activity or live public metrics.
- Semantic Memory — The recorded view shows no memory records and Authoritative: No. Its banner says promotion to organizational Knowledge requires human approval.
What the controls mean. The category tabs change the view. Import Source is visible, but no import was performed. The cropped overview intentionally stops before lower audit and diagnostic panels.
Your responsibility. Check source, scope, and approval before treating information as organizational truth. Memory and candidate material are not automatically approved Knowledge.
Alpha limit. No search result, source import, memory creation, forgetting, or promotion is demonstrated. An empty memory view can be a valid new-system state.
Semantic Memory in the recorded tour, at 00:44
Related screen: Workspace / Current Work →06 · Inspect execution state, its Plan, authorization, and evidence together.
Workspace / Current Work
Navigate here. Choose Workspace in the application’s bottom navigation, then Current Work. The public website’s Workspace link is a separate gateway page and does not open this application.
Look here first. Start with Execution Status. The captured work is Blocked because an approved Plan Record is required.
- Status panel — Blocked is the current state; it is not an execution in progress.
- Record panels — Linked Plan and Selected Step are Not Recorded. Authorization is Not Requested. Evidence is not evaluated.
- Execution control — Execute · Needs Approved Plan is disabled in the capture. The upper row also names Workflow & Evidence and Engineering & Handoff.
What the controls mean. Current Work selects this overview. Workflow & Evidence and Engineering & Handoff are visible destinations, but their detailed operations are not demonstrated. The disabled Execute control is a boundary, not a suggested next click.
Your responsibility. Review the actual Plan, scope, and authorization before consequential work. Assess evidence separately from accepting an outcome.
Alpha limit. The demonstration never approves a Plan or executes work. Public hosted application access remains unavailable.
Typical workflow · a demonstrated inspection journey
Follow the recorded route without advancing work.
Home → Team → Abriella → Mission Overview → Readiness → Library / Semantic Memory → Workspace / Current Work → Home. This is a navigation and inspection example. No consequential operation or successful outcome was staged.
Start by checking for an Objective and decisions. Read roles and assignment state, inspect the Mission and separate readiness dimensions, distinguish memory from approved Knowledge, and check the Workspace blocker. Return Home with the same human authority intact.
Alpha boundaries
Know what this guide establishes.
- The interface shown is Waymorrow Alpha, captured on 2026-09-05.
- Public hosted application access is not currently available; account access is Alpha-restricted.
- There is no public account creation or sign-in path here.
- Screenshots and demonstrations do not constitute application LIVE status.
- Idle, blocked, and not-evaluated states remain exactly that. They do not establish approval, execution, acceptance, or readiness.
- Review, approval, and control remain with the person. This guide demonstrates navigation, not permission to act.
Quick reference
Find the right screen.
| Surface | Purpose | What to look for | Related screen |
|---|---|---|---|
| Home / Action Center | Orient yourself before deciding what needs attention. | Read the Objective status in the top bar, then Action Center on the right. This capture has no active Objective and nothing waiting for a decision. | Team |
| Team | See the canonical roles and distinguish availability from active work. | Read the summary above the role cards. The captured Team is available, has no governed assignments, and has not been evaluated for readiness. | Abriella |
| Abriella | Understand Abriella’s role, current work, and human approval boundary. | Start with Current Assignment, Current Work State, and Execution Authority in the detail panel. | Mission / Readiness |
| Mission / Readiness | Read the current Objective and Plan context, then inspect readiness independently. | Read Release Status before the readiness dimensions. The capture says Target · Not Readiness Approved. | Workspace / Current Work |
| Library / Semantic Memory | Distinguish organized Knowledge, candidate material, skills, and contextual memory. | Read the category labels before interpreting any count. The overview contains native seed Knowledge Objects and skills, while candidates and Semantic Memory are empty. | Workspace / Current Work |
| Workspace / Current Work | Inspect execution state, its Plan, authorization, and evidence together. | Start with Execution Status. The captured work is Blocked because an approved Plan Record is required. | Home / Action Center |