Positioning Synthesis Review — AFPS Tracker

The run manifest (research/afps-tracker/_working/positioning-run.yaml) records three selected frameworks; all three canonical intermediates now exist, and no canonical positioning.md exists yet, so the loop resolves to synthesis (State B), forced explicitly by --synthesize.

Where the three frameworks agree, complement, or expose tension. The strong signal: all three independently land on trust-preserving legibility as the anchor and the manual native-files bundle as the real competitor. The one open strategic question they jointly raise is the category.

No material contradictions surfaced. The frameworks are complementary, not conflicting: JTBD established the job and switching forces, Canvas converted that into eliminate/reduce/raise/create moves and located the uncontested value curve, and Moore compressed both into a testable statement while exposing the category as the element most likely to break under real-buyer contact.

Compressed claim: AFPS Tracker is the passive, source-of-truth-preserving way to stay in command of a multi-branch AI research portfolio — navigable like a board, faithful like the files.

AFPS Tracker wins by making the real workflow state — paths, pipeline stages, evidence, approvals — instantly legible and verifiable without duplicating or mutating the canonical files the operator already trusts. The job-winning frame is trust-preserving legibility, located precisely at the uncontested intersection of portfolio navigability and source-linked, verifiable fidelity. The position is defended as much by disciplined subtraction (no second source of truth, no collaboration surface, no write-back at v1) as by what it adds. The thesis is well-grounded in approved ICP, competitive, and journey research but remains a pre-product hypothesis: its two existential open questions are whether an established category can be taught or must be borrowed, and whether the pain clears the bar to fire free, faithful native files (WTP unproven).

Each positioning claim mapped to the supporting framework(s), source evidence, confidence, and assumption status.

From JTBD Analysis

The single primary job is “hold trustworthy, resumable command of a multi-branch AI research portfolio without manual state reconstruction.” This is a progress (staying in command as AI accelerates artifact production), not a feature (a dashboard). The hire event is reconstruction cost crossing a threshold; the thing being fired is the manual reconstruction bundle. Switch forces explain the design: Push (repeated reconstruction) is real, but Habit (free, faithful native files) and Anxiety (write-back could corrupt canonical YAML) are jointly strong, so the hire only happens past a sprawl threshold and only if the product reads canonically and verifiably. Functional, social, and emotional success all converge on one outcome: open one source-linked view and, within seconds, know which paths are active, what stage each is in, and what evidence/approval backs each — with every claim verifiable to source and nothing manually entered or mutated.

From Strategic Canvas

The red ocean is workspace breadth + collaboration over duplicated state (generic PM and product/research SaaS cluster together: high on navigability/collaboration/execution, low on fidelity/verifiability). Native artifacts are the trustworthy-but-blind corner (high fidelity, no portfolio view). AFPS Tracker’s target value curve is the only one simultaneously High on fidelity, AFPS-native awareness, provenance, verifiability, navigability, and persistence while deliberately Low on collaboration and execution. The Four Actions: Eliminate the duplicate/owned state store and (for v1) the multi-user collaboration surface; Reduce active write-back (read-first) and feature breadth; Raise source-linked verifiability/provenance and portfolio navigability above anyone; Create an AFPS-native pipeline/branch object model and verifiable freshness signaling. The distinctive contribution: the wedge is defended by subtraction as much as addition.

From Moore Hypothesis

The template compresses the above into a single testable statement and grades each element: target customers, statement of need, and competitive alternative are Evidenced (High); key benefit and primary differentiation are Medium–High; market category is the weakest link (Low–Medium). Moore’s key warning: a position whose category is invented is hard to discover and easy to mis-evaluate — if buyers reach for an existing frame (generic PM, research repository, agent memory), the deliberate “Low” scores read as missing features rather than discipline. The second-deepest risk is existence/urgency at scale (whether AFPS operators exist beyond dogfooding and whether multi-path pain clears the bar to fire free native files).

On Category Design (cross-framework flag, not auto-routed)

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. The canvas now shows exactly that, and Moore independently names category as the weakest link. The synthesis therefore surfaces a decision (see the Market Category Treatment gate): treat the new subcategory as a labeled hypothesis and carry forward, with category-design recommended as an optional next framework — or run category-design before finalizing canonical positioning. This synthesis does not auto-invoke any skill; the user owns that call.

Primary (best-fit): the individual AFPS power user / AI-workflow operator running multi-branch, research-stage discovery in repo-local files — buyer = user. Selected by approved ICP verdict for exact product fit and the fastest learning loop (dogfooding + reachable AFPS operators). All three frameworks anchor here. Adjacent (validation, not anchor): AI-native studios / fractional CTO-CPO consultants, where multi-client branch state is expensive and provenance carries business/billable-time WTP — the strongest adjacent budget signal, but over-weighting it pulls toward a client-reporting tool and mis-anchors the primary wedge. Secondary: solo technical founders (high sprawl, price-sensitive). Product-ops / PM teams are adjacent market only.

Proposed category (hypothesized): source-native research-workflow state map — a new subcategory, since no public category term or validated direct competitor exists. This is the position’s weakest element and biggest go-to-market risk. Candidate labels considered:

Cost of being wrong on category: High for GTM (invisible or mis-shelved), moderate for the product (the differentiator holds even if the label changes). This is the element the validation plan prioritizes and the subject of the Market Category Treatment gate.

Confidence per positioning element. The chart shows relative strength; the full source + what-would-change-it table follows (“View as table”).

What must be tested before this position can be treated as canonical rather than hypothesized.

Downstream Impact

No research/afps-tracker/gtm.md exists, so there is no downstream GTM document to revise — impact None for now. Positioning becomes an upstream input the GTM/monetization steps should consume when run.

Next Steps (post-synthesis routing — for the written deliverable)

• Recommended: map the positioning into product direction with /user-flow-map — the product-design pack is not enabled (enabled: business-research, customer-lifecycle), so this needs npx skillpacks install product-design first.
• Consider /category-design — both Canvas and Moore flag “no category fits”/weakest link; run it before treating the category as canonical if GTM legibility is a priority (see the category gate).
• /value-prop-canvas — solution-customer fit is hypothesized; validates jobs/pains/gains → features/relievers/creators fit.
• /lean-canvas — WTP/revenue/channel risk is exposed; pressure-tests the business model.
• /gtm, /monetization (business-growth pack) — no GTM or monetization docs exist; sequence after positioning validates.

These routes are part of the proposed deliverable. They are not invoked now — the terminal handoff stays at the synthesis approval gate until final compiled YAML is provided.

Positioning narratives considered and not selected, carried for honesty and future revisit triggers.

• No direct AFPS-operator interviews or observed switching sessions — the entire position is synthesized from approved research + repo artifacts, not live customer language.
• No measured reconstruction-time baseline — the size of the need (and the benefit) is directional.
• No prototype test of the source-linked read-through — the predicted aha that underwrites benefit + differentiation is untested.
• No direct WTP evidence — adjacent budgets (studios, AI-workflow spend) are directional signals only.
• Category framing untested with real buyers — the single biggest template risk.
• No parser-fidelity audit — differentiation defensibility assumes reliable read-only parsing across AFPS artifact versions.
• Competitor scores from official-page evidence, not hands-on trials; Kiro/Runshift represented only indirectly via the AI-agents column.

Domain-specific terms this positioning introduces. Approved terms are appended to the scoped glossary (research/afps-tracker/glossary.md) on the confirmed-page write. Default scope: scoped (product path), not the parent glossary.

On final approval (after the BIP checkpoint resolves), the agent will:

• Write research/afps-tracker/positioning.md — the unified synthesis whose full content is rendered on this page (Market Positioning mode header, statement, summary, combined evidence matrix, framework synthesis, segment, category, confidence register, validation plan, implications, downstream, next steps).
• Archive the run manifest research/afps-tracker/_working/positioning-run.yaml and any synthesis working packet to docs/history/archive/YYYY-MM-DD/HHMMSS/.
• Update research/.progress.yaml → afps-tracker.pipeline_stage: positioning and last_touched.
• Append approved glossary terms to research/afps-tracker/glossary.md (creating it if absent), per the glossary gate.
• Convert this page and the BIP page to confirmed with the approval record preserved, and update alignment/index.html.

No canonical files are written while this page is in review. The framework intermediates and prior confirmed framework pages are not modified.

Review Gates

Answer the gates below, then compile at the bottom. The category gate is the one materially open strategic decision; the rest confirm the synthesis. The Final Artifact Approval control is locked pending the BIP checkpoint.