Strategic Canvas Positioning Findings - AFPS Tracker

Stage 2 framework-findings review page for /positioning research/afps-tracker. This is framework 2 of 3 in the approved set (jtbd-positioning → strategic-canvas → moore-positioning). It presents the Blue Ocean value-curve analysis: the competing factors the “stay-on-top-of-research-state” market invests in, where every alternative clusters (red ocean), the gap AFPS Tracker can own (blue ocean), and the Eliminate / Reduce / Raise / Create moves that draw its value curve. No canonical positioning artifact is written yet; this is the per-framework intermediate awaiting approval.

Alignment statusreview

Alignment date2026-06-26

Product pathresearch/afps-tracker

Skill stateState C — framework 2 of 3 (strategic-canvas)

ModeMarket Positioning (hypothesized, pre-product)

Intermediate on approvalresearch/afps-tracker/positioning-strategic-canvas.md

Page Amended updated

This rolling positioning page previously held the confirmed jtbd-positioning findings (framework 1 of 3). That confirmed page was archived to docs/history/archive/2026-06-26/113043/alignment/positioning-afps-tracker.html, and its approval record is preserved there. The page has been amended to present the strategic-canvas findings (framework 2 of 3) for review. The JTBD intermediate research/afps-tracker/positioning-jtbd-positioning.md remains canonical and is consumed as an input here; nothing about that approval is undone.

What changed since the prior page: entirely new framework content (competing factors, value curve, Four Actions), new charts, and a fresh review/gate set. Prior JTBD gate decisions live in the archived confirmed page, not on this page.

Research Scope & Loop State

The framework-selection gate was approved earlier (compiled YAML, approval_status: ready-for-agent-review) — that is the Stage-1 scope approval for the whole selected set, so strategic-canvas enters directly at its research stage. Framework 1 (jtbd-positioning) is complete and its intermediate is written; this session ran the next pending framework, strategic-canvas, inline.

ScopeAFPS Tracker as a research-stage workflow-state tracker for AFPS power users / multi-day operators. exec-loop-tracker and execution tracking excluded.

Sources consumedApproved competitive-analysis.md (+ feature/pricing matrix, strategic group map, SWOT, Porter), icp.md, and the framework-1 intermediate positioning-jtbd-positioning.md.

Working packetresearch/afps-tracker/_working/preliminary-strategic-canvas-research.md (non-canonical; rendered in full below).

Loop progress1 of 3 frameworks complete. On approval this writes framework 2 of 3; moore-positioning remains, then parent synthesis.

Competing Factors

The 10 dimensions the “stay-on-top-of-research-state” market competes on, extracted from the competitive evidence (competitor matrix, feature-coverage pattern, market gaps) — not invented. Each factor is framed so High = more of that attribute.

#	Factor	What it means in this market	Why buyers care
1	Source fidelity (no duplicate state)	The view reflects the canonical repo files with no second copy to maintain.	Duplicate state drifts and breaks trust; the operator wants truth, not a mirror.
2	Portfolio / branch navigability	Scan every product path and pipeline stage at a glance, no file-hopping.	The core reconstruction pain is state scattered across many files / pages.
3	AFPS-native semantic awareness	Understands `product_paths[]`, pipeline stage, alignment-approval YAML, evidence refs as first-class concepts.	Generic tools force the operator to translate AFPS meaning by hand.
4	Evidence & approval provenance	Each state claim links to evidence refs and the approval record behind it.	The operator must defend why a branch is active / parked under scrutiny.
5	Low setup / zero data entry	No migration, mirroring, schema setup, or manual re-entry to get value.	Re-entering state is exactly the cost the operator is trying to escape.
6	Collaboration & team breadth	Multi-user boards, sharing, comments, team workflows.	Matters to teams / studios; the canonical ICP is the individual operator.
7	Active execution / write-back	Mutate state, automate, act on the workflow from the tool.	Some buyers want to do, not just see — but write-back carries corruption risk.
8	Verifiability & non-destructive trust	Every shown claim is checkable against canonical source; reads never mutate.	Stale / mis-parsed / hallucinated state is worse than none; trust is the gate.
9	Persistent reviewable state map	A durable artifact you can return to and review, vs an ephemeral answer.	Agent re-reads re-incur cost each session; the operator wants continuity.
10	Price accessibility (free / low cost)	High = free / near-free (OSS, native files); Low = paid per-seat SaaS.	Native files set a zero-price benchmark any tool must beat on value.

Players (value-curve columns): Native AFPS artifacts (the incumbent + required input) · Ad hoc status files · Generic PM / workspaces (Notion, Trello, Linear) · Product / research SaaS (Jira Product Discovery, Productboard, Dovetail, Condens) · AI coding agents (Claude Code, GitHub Copilot) · AFPS Tracker. Kiro / Runshift are folded into the AI-agents curve (pricing / positioning gaps in the competitive pass).

Value Curve

The Blue Ocean value curve. The chart plots three contrast curves to show divergence; the full 6-player High / Medium / Low matrix is in the table below the chart (open with “View as table”).

AFPS Tracker Native artifacts Generic PM

Factor	Native artifacts	Ad hoc status files	Generic PM	Product/Research SaaS	AI coding agents	AFPS Tracker
1. Source fidelity (no dup state)	High	Low	Low	Low	Medium	High
2. Portfolio / branch navigability	Low	Low	High	High	Medium	High
3. AFPS-native semantic awareness	High	Low	Low	Low	Medium	High
4. Evidence & approval provenance	Medium	Low	Low	Medium	Low	High
5. Low setup / zero data entry	High	Medium	Low	Low	High	High
6. Collaboration & team breadth	Low	Low	High	High	Low	Low
7. Active execution / write-back	Medium	Medium	High	High	High	Low
8. Verifiability & non-destructive trust	High	Low	Low	Low	Medium	High
9. Persistent reviewable state map	Medium	Medium	High	High	Low	High
10. Price accessibility (free/low)	High	High	Medium	Low	Medium	High

Value Curve Observations

Cluster zone (red ocean): Generic PM and Product/Research SaaS sit together — High on navigability (2), collaboration (6), execution (7), persistence (9) but Low on fidelity (1), AFPS-native (3), verifiability (8). They compete on workspace breadth and collaboration, and winning there means accepting duplicated state.
Trustworthy-but-blind corner: Native artifacts + ad hoc files are High on fidelity (1), price (10), low-setup (5) but Low on navigability (2) — full truth, no portfolio view. This is the incumbent JTBD names as the thing being “fired.”
On-demand corner: AI agents are Medium on fidelity / navigability, High on execution (7) and setup-free use (5), but Low on persistence (9) and only Medium on verifiability (8) — useful, not trusted as final, re-incurred each session.
Divergence point (AFPS Tracker): the only column simultaneously High on fidelity (1) + AFPS-native (3) + provenance (4) + verifiability (8) and navigability (2) + persistence (9), while deliberately Low on collaboration (6) + execution (7). It inverts the generic-PM curve and extends the native-files curve.
Gap (blue ocean): no existing player is High on both “navigable, persistent portfolio view” and “source-linked, verifiable canonical fidelity.” That intersection is uncontested — and it is exactly the JTBD wedge.

Required gate: are the competing factors and value-curve scores accurate?

Approve — the 10 factors and the High/Med/Low scores are accurate for this market. Approve, but adjust specific factors or scores (name them in notes). A dimension that matters in this market is missing (name it in notes). Other / None of the above Need clarification

Four Actions Framework

The strategic moves that draw AFPS Tracker's new value curve. The discipline is subtraction as much as addition — eliminating duplicate state and reducing write-back / breadth is what creates the trust the additions depend on.

Eliminate

Duplicate / owned state store (a second source of truth). The adjacent industry competes on being the place you re-enter and own state; removing the second copy entirely kills drift at the root. Evidence: competitive gap #2; feature matrix “zero data model setup.” Risk: fully dependent on parser fidelity — AFPS schema drift breaks the value.

Generic multi-user collaboration surface (v1). The canonical ICP is the individual operator; collaboration can be dropped entirely without losing them. Evidence: ICP first buyer; “enterprise is a weak first anchor.” Risk: cuts a studio-segment expansion path — so eliminate for v1, expansion-gated.

Reduce

Active execution / write-back — High → Low (read-first; gated optional later). Write-back is the dominant switching-anxiety trigger; reducing it to near-zero at v1 neutralizes the top adoption blocker. Reduce, not Eliminate — the idea brief includes a sync layer, so it is deferred and gated, not deleted. Evidence: competitive gap #4; JTBD Anxiety force; ICP trust-risk.

Feature breadth (docs / wiki / roadmaps / feedback ingestion) — far below PM & research-repo breadth. The industry over-invests in features this operator doesn't need; staying thin protects the boundary. Evidence: feature matrix “evidence depth not to copy”; “broadening weakens the wedge.”

Raise

Source-linked verifiability & provenance — above anyone. Per-claim source links + approval records + visible freshness are the literal force overcoming Habit + Anxiety. Evidence: competitive gap #3; JTBD social/emotional success.

Portfolio / branch navigability over canonical state — raise above the real baseline (native files) to PM-grade scannability without leaving source truth. Evidence: competitive gaps #1/#2; ICP Frustrations.

Create

AFPS-native pipeline / branch object model — render product_paths[], pipeline stage, approval state, evidence refs as first-class navigable objects from canonical files. New to the industry; no reviewed tool parses AFPS artifacts. Evidence: competitive gap #1; feature matrix “core differentiator.” Risk: narrow surface; schema drift breaks it.

Verifiable freshness / staleness signaling — per claim, is this view source-true right now + non-destructive guarantee. Neutralizes drift distrust. Evidence: JTBD “freshness visible”; drift-distrust dimension. Risk: a wrong freshness signal is worse than none.

Expansion-gated, NOT a primary move: an agent-readable persistent state substrate. JTBD keeps agent-memory framing latent (Runshift territory, out of scope). Listed for completeness only.

Action	Move	One-line rationale
Eliminate	Duplicate / owned state store; generic collaboration surface (v1)	Removing the second copy and team-workspace scope is what earns trust and keeps the wedge sharp.
Reduce	Active write-back (read-first); feature breadth	Cuts the dominant switching anxiety and resists scope creep into generic PM.
Raise	Verifiability & provenance; navigability over canonical state	The two halves of the wedge native files and PM tools each only half-deliver.
Create	AFPS-native object model; freshness signaling	Genuinely new dimensions no reviewed tool offers.

Required gate: are these Eliminate / Reduce / Raise / Create moves accurate?

Approve — all four actions and their placements are right. Approve, but a move belongs in a different action (e.g. write-back should be Eliminate, not Reduce) — notes. A move feels wrong or needs stronger evidence (name it in notes). Other / None of the above Need clarification

Strategic Implications

New value curve

AFPS Tracker's target curve is High on fidelity (1), AFPS-native (3), provenance (4), low-setup (5), verifiability (8), navigability (2), persistence (9), and price (10); deliberately Low on collaboration (6) and execution (7). This shape exists nowhere else — it inverts the generic-PM curve and extends the native-files curve by adding navigability and provenance without sacrificing canonical truth.

Category impact

No existing category cleanly fits: generic PM (duplicate state), research repository (evidence analysis, not pipeline state), AI coding agent (ephemeral, execution-first), and agent-control-plane (active coordination) each describe a different curve. The canvas supports a new subcategory — source-native research-workflow state map / trust-preserving research-portfolio legibility — rather than a slot in an existing one.

Cross-framework flag (for parent synthesis, not routing): category-design was left unchecked at framework selection on the default that it is recommended only when the strategic canvas shows no existing category fits. This canvas now shows exactly that. The synthesis step should weigh whether to revisit category-design. This finding does not itself invoke any skill.

Positioning direction

The canvas corroborates the JTBD frame: anchor on trust-preserving legibility, lead with read-first / source-linked / non-destructive attributes, and locate differentiation at the fidelity × navigability intersection plus verifiability. It adds a point JTBD did not: the wedge is defended by what AFPS Tracker refuses to do (own state, collaborate, write back, sprawl in features) as much as by what it adds.

Required gate: does the new-subcategory implication (and the category-design reconsideration flag) land correctly?

Approve — new subcategory framing is right, and synthesis should weigh reconsidering category-design. New subcategory is right, but do not reopen category-design — keep the 3-framework set. It should fit an existing category instead (name it in notes). Other / None of the above Need clarification

Evidence Matrix

Claim	Evidence source	Evidence type	Confidence
The red ocean is workspace breadth + collaboration over duplicated state (PM / research-SaaS cluster).	competitive competitor matrix & feature-coverage pattern; `icp.md` Alternatives	Observed (approved synthesis)	High
Native artifacts are High-fidelity but Low-navigability (the incumbent being fired).	competitive Executive Synthesis; `jtbd` Progress Forces (Habit)	Observed	High
No player holds the fidelity × navigability + verifiability intersection (blue-ocean gap).	competitive market gaps #1–#3; feature-coverage pattern	Inferred from approved synthesis	Medium-High
Eliminating a duplicate / owned state store is the structural trust move.	competitive gap #2; feature matrix “zero data model setup”	Inferred	Medium-High
Write-back should be Reduced (read-first), not Eliminated.	idea-brief sync layer; competitive gap #4; `jtbd` Anxiety force	Observed (scope) + Inferred	High
Verifiability & provenance are the factors to Raise above everyone.	competitive gap #3; `jtbd` social/emotional success	Inferred	High
The AFPS-native object model + freshness signaling are genuinely new (Create).	competitive gap #1 (no tool parses AFPS artifacts); feature matrix	Provisional absence-of-evidence	Medium
The canvas supports a new subcategory, not an existing one.	competitive landscape (no category fits); strategic group map	Inferred	Medium
Direct WTP for this curve is unproven; value metric is time saved + confidence.	competitive pricing caveats; `icp.md` WTP; `jtbd` evidence matrix	Observed gap	High (that it’s unproven)

Required gate: is the evidence sufficient to carry this curve into moore-positioning?

Sufficient — carry the canvas + Four Actions into moore-positioning. Sufficient, but flag specific claims needing more support (notes). Not sufficient — a missing source could change the curve / moves (notes). Other / None of the above Need clarification

Alternatives / Lower-Confidence Findings

Alternative reading	Why not selected	Residual uncertainty
Compete inside generic PM by raising collaboration + execution.	Inverts the wedge; lands in the red-ocean cluster where duplicated state is required and fidelity is Low.	If buyers value team workflows over fidelity, the individual-operator curve under-serves them.
Keep write-back a High factor (active sync) from v1.	Contradicts the dominant Anxiety force; premature write-back creates adoption resistance.	If users demand editing before seeing read value, Reduce may be too aggressive.
Treat AFPS-native parsing as Raise, not Create.	Native files contain the semantics, but no tool models them as navigable objects — that layer is new.	Borderline call; a discovered AFPS-native tool would downgrade it to Raise.
Position as a research repository (Dovetail / Condens curve).	That curve is evidence-analysis, not pipeline-state, and invites out-of-scope expectations.	Studio segment could value repository-style evidence depth more.

Source Coverage & Gaps

Scoring is judgment synthesized from approved competitive + ICP + JTBD evidence, not user-tested — no direct AFPS-operator interviews or observed sessions.
No prototype test of whether navigability-over-canonical-state delivers the predicted value vs native files.
No hands-on competitor trials; competitor factor scores rely on official-page evidence from the competitive pass.
Kiro and Runshift were not scored as distinct columns (pricing / positioning gaps); their agent-control-plane curve is represented indirectly via AI agents.
No measured reconstruction-time baseline, so the size of the navigability Raise is directional.
WTP for this curve is unproven; price-accessibility scoring assumes an OSS-core hypothesis, not a validated model.

Assumptions / Confidence Register

Assumption	Status	Confidence	What would change it
The fidelity × navigability + verifiability intersection is genuinely uncontested.	Evidence-backed (absence of evidence)	Medium	A discovered AFPS-native or source-linked portfolio tool.
Eliminating duplicate state is feasible without losing the customer (parser reliable enough).	Hypothesized	Medium	Dogfooding shows parsing too brittle to trust, forcing a cached / owned store.
Collaboration can be eliminated at v1 without losing the primary ICP.	Evidence-backed for individual operator	Medium-High	Studio / consultant segment proves primary, requiring collaboration sooner.
Reducing write-back (read-first) increases adoption rather than capping value.	Inference from Anxiety force	Medium-High	Users reject a read-only tool or expect write-back before paying.
Raising verifiability / provenance is the decisive differentiator.	Evidence-backed across ICP / competitive / journey	High	Users prefer breadth / collaboration over fidelity + verifiability.
The canvas warrants reconsidering category-design in synthesis.	Inference from “no category fits”	Medium	Moore template lands cleanly in an existing category, making new-category design unnecessary.

Proposed Canonical Artifacts & File Changes

On approval, only the strategic-canvas framework intermediate is written. No canonical research/afps-tracker/positioning.md synthesis is created from this framework — that is the later parent synthesis step after moore-positioning also completes.

Path	Action on approval
`research/afps-tracker/positioning-strategic-canvas.md`	Create — canonical strategic-canvas intermediate (2 of 3 framework intermediates feeding parent synthesis).
`research/afps-tracker/_working/preliminary-strategic-canvas-research.md`	Archive to `docs/history/archive/YYYY-MM-DD/HHMMSS/…` and remove the active working packet.
`alignment/positioning-afps-tracker.html`	Convert this findings page from `review` to `confirmed` with the approval record preserved.
`alignment/index.html`	Keep the central alignment index entry current.

The run manifest research/afps-tracker/_working/positioning-run.yaml already exists and is unchanged. research/.progress.yaml pipeline_stage stays at journey-map until the parent synthesis writes canonical positioning.md.

Required gate: do the layout, tables, and evidence density match your expectations?

Format is good — layout, value-curve chart, tables, and evidence density match expectations. Adjust the format (grouping, labels, visuals, or density) per notes. Other / None of the above Need clarification

Required gate: approve writing the strategic-canvas intermediate and the file changes above?

Approve — write the intermediate, archive the working packet, and confirm this page. Approve with the edits requested in the gates / section feedback above. Do not write yet — revise first (notes). Other / None of the above Need clarification

Compile Responses

Answer the required gates above (or select section feedback), then compile. approval_status: ready-for-agent-review is set automatically only when every required gate is answered with no unresolved negative feedback. Paste the compiled YAML into a fresh session running /positioning research/afps-tracker; the parent will write the approved intermediate and recalculate whether another framework or synthesis is next.