Journey Map Framework Selection - AFPS Tracker

Stage 1 review page for $journey-map research/afps-tracker. This page proposes the journey-map research scope and framework set only. No framework research, run manifest, working packet, canonical journey map, or framework intermediate has been created.

Alignment statusreview

Alignment date2026-06-17

Product pathresearch/afps-tracker

Skill stateState E - framework selection

Proposed Scope

Scope is limited to AFPS Tracker as a research-stage workflow-state and branching-decision visualizer for AFPS power users and AI workflow operators. The explicit command argument resolves the active product path to research/afps-tracker, even though research/.progress.yaml also lists research/exec-loop-tracker as active.

Out of scope for this journey-map run: exec-loop-tracker, development execution tracking, generic project management, broad research repository design, active recommendation engines, and UI or architecture specification.

Scope evidence, not findings: the repo contains approved ICP and competitive-analysis artifacts for AFPS Tracker, plus an approved idea brief. These sources justify the proposed research boundary but do not yet create journey-map conclusions.

Required gate: approve the AFPS Tracker scope?

Approve AFPS Tracker-only scope with exec-loop-tracker excluded. Approve with a Product Path Implications note if later journey evidence exposes deferred exec-loop dependencies. Other / None of the above Need clarification

Mode Detection

Detected mode: Pre-product mode, hypothesized. The command did not include product; there is no research/afps-tracker/customer-feedback.md; no production app files were found in the shallow repo scan; and the active product path is at the research stage after ICP and competitive analysis.

Prerequisiteresearch/afps-tracker/icp.md exists, satisfying the hard journey-map prerequisite.

Soft evidenceresearch/afps-tracker/competitive-analysis.md and research/afps-tracker/idea-brief.md exist.

Missing post-launch evidenceNo scoped customer-feedback file was found for AFPS Tracker.

StateNo journey-map run manifest, framework intermediate, or canonical journey-map artifact exists.

Required gate: approve pre-product journey mapping mode?

Approve pre-product mode. Treat as product-exists mode because operational product evidence should be considered. Other / None of the above Need clarification

Available Source Categories

Category	Observed scope evidence	Stage 1 impact
ICP and pain map	`research/afps-tracker/icp.md`	Supports AFPS power-user journey framing.
Competitive synthesis	`research/afps-tracker/competitive-analysis.md`	Provides substitute and market-context inputs for later journey research.
Idea and progress context	`research/afps-tracker/idea-brief.md`; `research/.progress.yaml`	Confirms scope boundaries and pipeline state.
Product code evidence	No shallow production app files found; `CLAUDE.md` and `AGENTS.md` are workflow docs.	Supports pre-product mode.
Customer feedback	No `research/afps-tracker/customer-feedback.md` found.	Keeps claims hypothesized until user/customer evidence exists.

Framework Selection

Pre-product defaults are pre-checked. The selected set becomes the approved scope for the parent journey-map loop. Each selected framework will run inline in a later invocation, one framework per session, after final compiled YAML approval.

JTBD Timeline default

Maps first thought, passive looking, active looking, deciding, consuming, and satisfaction through push, pull, anxiety, and habit forces. Recommended because AFPS Tracker demand is still hypothesized and switching triggers matter.

Experience Map default

Builds the emotional arc with doing, thinking, feeling, pain, and opportunity layers. Recommended because the ICP pain centers on cognitive load, trust, and context reconstruction.

Customer Journey Canvas optional

Audits stages, touchpoints, actions, emotions, backstage support, pain, and opportunities. Useful if you want a broader touchpoint map before UX work.

Service Blueprint optional

Maps front-stage, backstage, support, and evidence lines. Optional now because no running product or operational support surface is validated yet.

User Story Map optional

Organizes activity, task, and story hierarchy with release slicing. Optional until journey evidence is approved enough to shape product-flow work.

Required gate: approve selected framework set?

Approve the currently checked framework set. Run all available frameworks. Other / None of the above Need clarification

Output Paths And Loop Plan

Path	When written	Status now
`alignment/journey-map-afps-tracker.html`	Stage 1	Review page created for approval.
`alignment/index.html`	Stage 1	Updated to include this review page.
`research/afps-tracker/_working/journey-map-run.yaml`	After final compiled YAML approves framework selection	Not created in Stage 1.
`research/afps-tracker/_working/preliminary-journey-map-research.md`	Stage 2 framework or synthesis review when applicable	Not created in Stage 1.
`research/afps-tracker/journey-map-{framework}.md`	After each framework findings page is approved	Not created in Stage 1.
`research/afps-tracker/journey-map.md`	After synthesis review is approved	Not created in Stage 1.

Required gate: approve the staged file-change boundary?

Approve staged boundary: manifest after framework-selection approval, canonical artifacts only after later artifact approvals. Approve page only; revise output paths before future stages. Other / None of the above Need clarification

Assumptions And Source Gaps

Assumption or gap	Status	What could change the plan
AFPS Tracker remains research-stage only.	Evidence-backed by approved idea brief, ICP, and competitive analysis.	User approval expands the product boundary.
Pre-product journey mapping is the right mode.	Supported by missing product/customer evidence.	New product usage evidence or customer feedback is supplied.
JTBD Timeline and Experience Map are enough for the first pass.	Proposed default, not a finding.	User chooses optional frameworks or custom scope.
Journey claims will be hypothesized until direct AFPS operator evidence exists.	Source gap.	Customer-feedback artifacts, interviews, dogfooding logs, or usability sessions are added.

Required gate: is this source plan sufficient for Stage 2?

Sufficient for hypothesized pre-product journey research. Needs additional source context before Stage 2. Other / None of the above Need clarification

Stage 2 Preview

After final compiled YAML approval, the next invocation of the parent orchestrator writes research/afps-tracker/_working/journey-map-run.yaml with only the approved framework slugs, then runs the first pending framework inline at its research stage. The parent loop then stops again for framework findings approval.

Future framework findings pages will render the complete non-canonical working packet as structured HTML, with evidence matrix, assumptions/confidence register, source gaps, proposed canonical file changes, and artifact approval gates. Canonical intermediates are written only after each framework findings page is approved.

Compile Responses

Answer required gates or select section feedback, then compile YAML. Complete approval requires all required gates answered with no unresolved rejection or clarification feedback.