Frozen document. Dates and status refer to its original source. Private resources and unreviewed images are unavailable.

Discovery and delivery process

Wayfinder

The canonical map is a GitHub issue labelled wayfinder:map. Its discovery destination was reached and the map closed on September 26, 2026. It remains the index of decision tickets and their resolutions.

The map indexes decisions; it does not duplicate their answers. Each ticket's resolution comment is the authoritative decision record. Where a consequential trade-off merits an ADR, the comment links the ADR as an asset and the ADR links back to its decision ticket.

Research tickets use the research skill and scoped background agents. Grilling and prototype tickets require the owner's participation. Charting resolves no human decisions. A later session resolves at most one non-research ticket, then updates the map and its newly visible questions.

ADRs are created only after a real trade-off has been made or a clearly marked proposal needs review. Technology preferences from the original request are constraints, not evidence of an evaluated decision. No ADR is fabricated to fill a numbered list.

Specs

The owner confirmed the local Mac full-stack behavioral seam and separate hosted promotion seam. To-spec synthesized the discussion into four GitHub specifications; the product, employer, and certification specs complete that set. Do not silently fill later implementation details with unsupported assumptions.

Each spec should cover user stories, implementation decisions, testing decisions, out-of-scope behavior, and links to its decision evidence. Apply ready-for-agent only when the spec's prerequisites are met.

Implementation issues

Use to-issues to propose independently verifiable tracer bullets. Every implementation issue must deliver a narrow, demoable path through all applicable UI, API, authoritative state, workflow/integration, and test boundaries. Split an oversized behavior into smaller end-to-end paths, never layer-only tickets. Keep integrated certification, owner decisions, and journey publication as separately identified gates or deliverables. The owner approved granularity, dependencies, HITL/AFK classification, and safe parallel groups on September 26, 2026; the published issue map records all 22 resulting issues.

Every slice must include required context, conceptual ownership, forbidden scope, focused validation, and a structured handoff. These fields are a prerequisite to multi-agent implementation.

The approved issues have a dated issue and milestone ledger. Re-capture after meaningful claim, pause, close, or gate changes using the capture guide; preserve each dated snapshot and update the interactive map's current JSON.

Verification

Workers validate their owned behavior and contracts. The orchestrator checks dependencies and integrates evidence at each convergence point. Full-repository qualification belongs to the final gate or a justified risk escalation.

The first build slice is claimed. No application test result can be claimed until its code and focused validation evidence exist.