Visual Waypoint
A Laws of Three productVisual Waypoint

Follow the work.Inspect the evidence.Remember the code.

Visual Waypoint turns captured AI coding sessions into a navigable Timeline and evidence trail—then lets you preserve durable anchors to important code as private or project-shared Waypoints.

Request early accessSee the product
Visual Studio + .NET firstLocal-first session dataHuman approval stays explicit
Spatial viewCity Islands

Current-source Product Tour demo · maps are navigation surfaces, not verdicts.

00 The 30-second version

A diff shows the result. Visual Waypoint preserves the path.

Capture the work while it happens, understand it at the right level, and keep durable anchors back into the code.

01

Capture

Captured agent Turns become a local session record.

02

Timeline

Work Spans reveal how the session unfolded.

03

Waypoints

Save the code and Notes worth keeping.

04

Evidence

Claims stay separate from what was captured.

05

Code

Return to the exact file or changed range.

01 Timeline

See the path behind the diff.

Follow captured agent Turns in Work Spans, filter to changed code or evidence gaps, inspect a Turn in context, then open the corresponding Review item.

Work Span chronologyFocused filtersOpen in Review

The page emphasizes the readable structure; open the complete image for all thirteen Turns. Demo contents are illustrative, not usage metrics.

02 Durable Waypoints

Bookmarks that remember more than a line number.

Save a caret or exact code range, add a Quick Note or formatted Note, organize it, search it, and return to the code later.

My Waypoints

Private by default. They stay in Visual Waypoint’s local data and do not write to the repository.

Project Waypoints

Explicit opt-in. Shared anchors and Note sidecars travel with the repository under .visualwaypoint.

Rich Notes + Quick Notes

Keep a short note directly on the Waypoint or open a formatted Note with emphasis, color, lists, indentation, spelling support, and images. Edits autosave; conflicting drafts surface instead of silently overwriting newer content.

Smart Anchors move with the code

Normalized text, nearby context, keywords, and SHA-256 fingerprints can relocate a Waypoint after line drift or a move within the same file. Ambiguous matches keep the stored location instead of guessing.

Working in someone else’s codebase?Keep private navigation and Notes without changing repository state. Share only when you intentionally choose a Project Waypoint.
Private and project scope in one tree

Folders, point and range bookmarks, formatted Notes, Quick Notes, and anchored file locations stay organized by ownership.

03 Review — Evidence

Claims beside evidence—not mixed into a verdict.

Review Work Spans and Turns with guidance, changed regions, AI statements, receipts, and not-captured states kept visibly distinct. Review progress comes from explicit human action.

AI statementsChanged regionsReceipts / not captured
04 Spatial memory

Change the view. Keep the evidence boundary.

Story Spine, Signal City, Night City, and City Islands are alternate ways to explore the same captured session. They provide alternate navigation and spatial-memory views; they do not declare the code correct.

City IslandsSeparate Work Spans into distinct spatial clusters.
Night CityCompare Work Spans as illuminated tower clusters.
Signal CityExplore grouped session structure.
Story SpineFollow the chronological route through the work.
06 Trust + privacy

Confidence starts with honest boundaries.

Visual Waypoint supports human review. It does not replace human review, declare correctness, or treat global workstation activity as review evidence.

Local-first by design

Session data and private Waypoints stay in the local product workflow. Repository sharing is deliberate.

Approval stays human

Opening or hovering is not approval. Review state changes through explicit user actions.

Bounded handoff

The Handoff Pack uses an allowlisted artifact set and excludes raw source and raw transcripts by default.

Claims stay claims.Evidence stays evidence.Approval stays human.
07 Built first for

People who expect to maintain what the AI creates.

Solo developers

Resume without replaying the whole conversation.

Rebuild context after an interruption and keep private anchors into a client or production codebase.

Senior reviewers

Understand the session, then inspect the code.

Move from Work Spans and evidence gaps to exact files and ranges before making a decision.

Technical leads

Get a factual, non-verdict readout.

Understand scope, review progress, and where human attention is still required.

Engineering validation · Visual Waypoint 1.0.10 candidate1,178 headless scenario checks passed

This validates the Visual Waypoint candidate itself—it is not a report the product generated about customer code. The executed-check total includes intentionally overlapping focused coverage; it is not a count of unique tests, visible-UI certification, security certification, or a guarantee of correctness.

08 Early access

Use AI on a codebase you plan to keep?

Help shape a review and navigation workflow built for human understanding. Visual Waypoint is starting with Visual Studio and .NET developers working in substantial, long-lived codebases.

Built by Laws of ThreeTell us where AI-assisted work becomes hardest to understand, review, or resume.

Optional. It helps us understand who should be in the first preview.

Your request is recorded in the Laws of Three early-access list. We’ll use these details only to contact you about Visual Waypoint early access.