Strategic Group Map - AFPS Tracker (Confirmed)
Confirmed strategic group map for the active AFPS Tracker product path. The approved Stage 2 packet has been canonicalized at
research/afps-tracker/competitive-analysis-strategic-group-map.md.
Status: confirmed
Stage: 3 final
Date: 2026-06-16
Product path: research/afps-tracker
Framework: strategic-group-map
Visual tier: visual
Archived packet: docs/history/archive/2026-06-16/102454/research/afps-tracker/_working/preliminary-strategic-group-map-research.md
Canonical target: research/afps-tracker/competitive-analysis-strategic-group-map.md
Change Summary Updated
This page has been confirmed from the Stage 2 artifact-review page. It preserves the approved axes, competitor placements, strategic groups, whitespace analysis, evidence matrix, assumptions/confidence register, alternatives, source gaps, and canonicalization file set.
The pre-confirmation Stage 2 review page was archived at docs/history/archive/2026-06-16/102454/alignment/strategic-group-map-afps-tracker.html.
The canonical strategic group map artifact has been written at research/afps-tracker/competitive-analysis-strategic-group-map.md. The approved working packet was archived and removed from active working state.
Confirmation Record Confirmed
alignment_status: confirmed
Confirmation date: 2026-06-16
Confirmed artifact: research/afps-tracker/competitive-analysis-strategic-group-map.md
Approval source: final compiled YAML approved the map axes, placements, group definitions, evidence coverage, assumptions/confidence, and Stage 3 file changes.
This page is current for the completed strategic group map alignment cycle. Later research can amend it only by archiving this confirmed page and highlighting the amendment.
Completed prior frameworks
Porter's Five Forces and SWOT are canonical under `research/afps-tracker/`.
Porter's Five Forces and SWOT are canonical under `research/afps-tracker/`.
Archived working packet
docs/history/archive/2026-06-16/102454/research/afps-tracker/_working/preliminary-strategic-group-map-research.mdCanonical artifact
research/afps-tracker/competitive-analysis-strategic-group-map.mdScope
AFPS Tracker is scoped as a research-stage workflow-state and branching-decision visualizer for AFPS power users and AI workflow operators. It reads workflow state already emitted by AFPS-style repositories, especially `research/.progress.yaml`, `product_paths[]`, working packets, alignment pages, and task docs.
The approved strategic group map scope excludes `exec-loop-tracker` and all development execution tracking. Development-stage and agent-control products are included only as adjacent alternatives because they can absorb context, handoff, planning, or workflow-state jobs.
Strategic Map
The primary map plots source fidelity against workflow stance. AFPS Tracker's proposed whitespace sits near the upper-left: high AFPS/source-native fidelity with passive, reviewable visibility.
Axis Selection
| Axis | Why It Matters | Evidence | Confidence |
|---|---|---|---|
| Generic work system to AFPS/source-native workflow state | AFPS Tracker's wedge is fidelity to source artifacts, not broad PM breadth. | Approved idea brief and ICP define repo-local AFPS artifacts. Reviewed public tools do not describe native AFPS artifact parsing. | High for repo-defined wedge; medium for public absence observation |
| Passive visibility/provenance to active execution/control | AFPS Tracker is intentionally passive in v1; many adjacent tools compete by doing more. | Trello, Linear, Claude Code, Copilot, Kiro, and Runshift emphasize workflow action, agents, or execution; AFPS artifacts emphasize reviewable evidence. | High |
| Secondary lens: research/product evidence depth | Product discovery and research repositories compete through evidence, feedback, and product-decision context. | Jira Product Discovery, Productboard, Dovetail, and Condens focus on product discovery, feedback, research repository, or insights workflows. | Medium-high |
Competitor Placement
| Competitor / Alternative | Axis 1 Position | Axis 2 Position | Group | Evidence | Confidence |
|---|---|---|---|---|---|
| Native AFPS repo artifacts | Very high AFPS/source-native | Passive visibility, manual navigation | Source-native substitutes | Repo artifacts define canonical state; Porter and SWOT identify these as strongest current substitutes. | High |
| Ad hoc status or memory files | Medium to high if manually tailored | Passive to lightly maintained | Source-native substitutes | Prior Porter work identifies local summaries and status files as substitute patterns. | Medium |
| Notion | Low AFPS-native specificity; high workspace breadth | Medium: workspace plus agents, search, projects, docs | Broad workspaces and PM systems | Notion markets agents, enterprise search, knowledge base, docs, and projects. | High |
| Trello | Low AFPS-native specificity; broad board utility | Medium: boards plus automation and integrations | Broad workspaces and PM systems | Trello markets boards, task/project management, automation, Power-Ups, templates, integrations, and free plans. | High |
| Linear | Low AFPS-native specificity; product-development focus | High: planning plus agent-shared workflows | Product development systems | Linear positions itself as a product development system for teams and agents. | High |
| Jira Product Discovery | Low AFPS-native specificity; product discovery focus | Medium | Product discovery and intelligence | Atlassian presents Jira Product Discovery as a product discovery tool with creator plans. | Medium-high |
| Productboard Spark | Low AFPS-native specificity; product intelligence focus | Medium | Product discovery and intelligence | Productboard pricing presents Spark plans for product work and AI product-agent positioning. | Medium-high |
| Dovetail | Low AFPS-native specificity; high research evidence depth | Low to medium | Research repositories and customer intelligence | Dovetail pricing and product pages position around customer insights, research repository, analysis, and sharing. | High |
| Condens | Low AFPS-native specificity; UX research repository focus | Low to medium | Research repositories and customer intelligence | Condens pricing is explicitly for a UX research repository. | High |
| Claude Code | Medium codebase/source context; no AFPS-native evidence found | High | AI coding agents and spec/build systems | Claude Code markets codebase-aware build, debug, ship workflows across terminal, IDE, Slack, web, and desktop. | High |
| GitHub Copilot | Medium code/repo context; no AFPS-native evidence found | High | AI coding agents and spec/build systems | GitHub Copilot plans show paid AI developer tooling and agent-oriented plan options. | Medium-high |
| Kiro | Medium code/spec context; no AFPS-native evidence found | High | AI coding agents and spec/build systems | Kiro markets engineering rigor for agentic development with specs, plans, tasks, steering, hooks, and agent workflows. | High |
| Runshift | Medium source/workflow context; no AFPS-native evidence found | Very high | Agent-control planes | Runshift positions itself as a control plane for AI agents; prior Porter/SWOT evidence records context, locks, trust gates, and audit trails. | Medium |
Strategic Groups
Source-Native Substitutes
Native AFPS repo artifacts and ad hoc status files are closest on source fidelity. They are high-trust and low-cost, but require manual reconstruction across YAML, markdown, HTML, and task history.
Broad Workspaces And PM Systems
Notion, Trello, and Linear offer broad places to mirror work state, route tasks, centralize docs, or manage product work. They are navigable but duplicate source state.
Product Discovery And Intelligence
Jira Product Discovery and Productboard Spark compete for product-context budgets and decision workflows rather than repo-native AFPS state.
Research Repositories
Dovetail and Condens validate evidence-centralization workflows, but they organize research inputs rather than AFPS pipeline state.
AI Coding Agents
Claude Code, GitHub Copilot, and Kiro compete by reconstructing or acting on repository context on demand.
Agent-Control Planes
Runshift is adjacent because shared context, approval gates, and auditability overlap with AFPS Tracker's trust language.
Whitespace And Crowded Zones
Crowded Zones
- Generic workspace/project surfaces are crowded across Notion, Trello, Linear, Jira Product Discovery, and Productboard.
- Active AI execution is rapidly crowding across Claude Code, GitHub Copilot, Kiro, Linear agents, and Runshift.
- Evidence repositories already exist, so AFPS Tracker should not become a generic research repository.
Whitespace
- High AFPS/source-native fidelity plus passive, reviewable visibility is underserved in the reviewed public tools.
- Portfolio-level research branch maps are distinct from task boards: native files are faithful but hard to scan, while generic tools are easy to scan but duplicate state.
- Trust-preserving workflow-state views are a wedge against repeated AI summary prompts because they link directly back to source state.
Evidence Matrix
| Claim | Source | Evidence Type | Inference | Confidence | Decision Impact |
|---|---|---|---|---|---|
| AFPS Tracker's wedge is source-native workflow state. | `research/afps-tracker/idea-brief.md`; `research/afps-tracker/icp.md`; parent packet | Repo artifact | The approved product definition centers on AFPS artifacts and excludes broad PM/execution tracking. | High | Approve Axis 1 if source fidelity remains intended differentiation. |
| Native repo artifacts are the closest substitutes. | `research/.progress.yaml`; `alignment/index.html`; Porter and SWOT canonical artifacts | Repo artifact | Existing users can inspect the same state without a product UI. | High | Keep source-native substitutes as a core cluster. |
| Generic workspaces are broad but not AFPS-native. | Notion; Trello; Linear | Vendor evidence | They can mirror state but do not model AFPS artifacts. | High | Place them low-AFPS and medium/high activity. |
| Product discovery tools compete for product-decision workflow budget. | Jira Product Discovery; Productboard | Vendor pricing/positioning | They validate paid product-context workflows, not AFPS-native state. | Medium-high | Keep them distinct from generic PM tools and research repositories. |
| Research repositories compete through evidence/provenance. | Dovetail; Condens | Vendor pricing/positioning | They centralize research and insights, not AFPS pipelines. | High | Place them low-AFPS and lower-execution, high evidence-depth. |
| AI coding agents can absorb repo-state reconstruction. | Claude Code; GitHub Copilot; Kiro | Vendor evidence | Users may ask agents to summarize AFPS state instead of using a tracker. | Medium-high | Place them medium-source-context and high-active-execution. |
| Agent-control planes validate context and approval-gate needs. | Runshift; Porter/SWOT canonical artifacts | Vendor + prior framework evidence | Control-plane tools show market language around context, locks, trust gates, and auditability. | Medium | Keep Runshift adjacent, active-control, and not product-discovery. |
| Trust-preserving passive state remains valuable despite AI adoption. | Stack Overflow 2025 AI survey; Porter and SWOT canonical artifacts | Survey + repo inference | AI adoption coexists with accuracy/trust concerns. | Medium-high | Use as synthesis input, not standalone positioning. |
Assumptions And Gaps
| Assumption | Status | Confidence | What Would Change It |
|---|---|---|---|
| The two primary axes are sufficient for Stage 2 review. | Inference | Medium-high | User prefers buyer scale, pricing model, or research-depth axes. |
| Public tools lack AFPS-native artifact parsing. | Provisional absence-of-evidence | Medium | Discovery of public AFPS-compatible templates, plugins, trackers, or skill dashboards. |
| Native AFPS artifacts should be plotted as substitutes. | Evidence-backed behavioral substitute | High | User wants only commercial software competitors in the map. |
| Active AI agents are material substitutes. | Inference | Medium-high | User testing shows agents are too slow or unreliable for repeated AFPS state checks. |
| AFPS Tracker should remain closer to passive visibility than active control. | Evidence-backed by approved scope | High | Later approval expands the product into write-back, recommendations, or execution tracking. |
Source Coverage Gaps
- No hands-on product testing against a live AFPS repository.
- No direct interviews with AFPS operators about which map axes feel most accurate.
- No exhaustive public search proving that no AFPS-native tracker exists.
- Runshift page extraction was limited; deeper validation would improve confidence.
- Pricing and packaging depth is deferred to `feature-pricing-matrix`.
Canonicalization Record
| Path | Action | Notes |
|---|---|---|
docs/history/archive/2026-06-16/102454/research/afps-tracker/_working/preliminary-strategic-group-map-research.md | Created archive copy | Preserves the approved Stage 2 packet. |
research/afps-tracker/_working/preliminary-strategic-group-map-research.md | Removed active working packet | Stage 3 cleanup after canonical artifact was written. |
research/afps-tracker/competitive-analysis-strategic-group-map.md | Created canonical artifact | Uses approved packet content with canonical status/header updates. |
alignment/strategic-group-map-afps-tracker.html | Converted from review to confirmed | Preserves approval decisions, caveats, evidence matrix, map data, and final YAML. |
alignment/index.html | Updated status metadata | Keeps the central index current. |
Approval Decisions Confirmed
| Gate | Decision | Status | Target |
|---|---|---|---|
| candidate/verdict decisions | Approve map axes, placements, and group definitions | answered | research/afps-tracker/competitive-analysis-strategic-group-map.md |
| evidence coverage | Evidence coverage is sufficient for strategic group map canonicalization | answered | Strategic group map evidence matrix |
| assumptions/confidence | Approve confidence levels and assumptions as drafted | answered | Assumptions and confidence register |
| proposed file changes | Approve proposed Stage 3 file changes | answered | research/afps-tracker/competitive-analysis-strategic-group-map.md |
Final Approval YAML
response_status: complete
approval_status: ready-for-agent-review
required_gate_status: complete
unanswered_required_questions: none
alignment_page: "alignment/strategic-group-map-afps-tracker.html"
response_status: "complete"
approval_status: "ready-for-agent-review"
required_gate_status: "complete"
unanswered_required_questions:
- []
gate_answers:
- section: "Approval Gates"
gate_type: "candidate/verdict decisions"
status: "answered"
answer: "Approve map axes, placements, and group definitions"
target_artifact: "research/afps-tracker/competitive-analysis-strategic-group-map.md"
- section: "Approval Gates"
gate_type: "evidence coverage"
status: "answered"
answer: "Evidence coverage is sufficient for strategic group map canonicalization"
- section: "Approval Gates"
gate_type: "assumptions/confidence"
status: "answered"
answer: "Approve confidence levels and assumptions as drafted"
- section: "Approval Gates"
gate_type: "proposed file changes"
status: "answered"
answer: "Approve proposed Stage 3 file changes"
target_path: "research/afps-tracker/competitive-analysis-strategic-group-map.md"