A · Docs Platform
Build a hosted publishing target for Noma. Highest revenue ceiling, longest path to value.
Q3 Roadmap Decision
Three candidate directions for next quarter. This document captures the options, trade-offs, risks, and timeline as structured blocks so an agent can revisit and update each section independently — and so the recommendation can be exported as a prompt for a follow-on review pass.
Options at a glance
B · Research Workflows
Lean into claims/evidence/risk blocks for analyst teams. Narrow ICP, fastest to first paying customer.
C · General Reports
Position Noma as the default format for AI-generated reports across domains. Broadest TAM, weakest wedge.
Decision
Decision matrix
| Dimension | A · Docs | B · Research | C · Reports |
|---|---|---|---|
| Time to first revenue | 6–9 mo | 6–10 wk | 4–6 mo |
| Wedge sharpness | Medium | High | Low |
| Existing block fit | Strong | Native | Medium |
| Defensibility | Network | Workflow | Brand only |
| 18-month revenue cap | High | Medium | High |
Claims and evidence
Risks
Timeline
Wk 1 · Format
Parser, AST, frontmatter, JSON export, basic validation.
Wk 2 · Artifact
HTML renderer, default theme, cards/grids/tabs/charts, mobile.
Wk 3 · Agent
LLM export, patch protocol, copy-as-prompt buttons.
Wk 4 · Launch
3 demos, README, spec, comparison page, OSS release.
Open questions
Agent tasks
Re-run the interview tally each month. If claim-research-wedge evidence base drops below 8 of 11 supporting interviews (or new interviews contradict), lower the claim's confidence attribute and add a counterevidence block.
Every two weeks, scan evidence blocks for source attributes older than 60 days. Flag any whose underlying source has changed materially. Do not auto-edit — propose a replace_block patch for human approval.
On request, package this document's decision, top three claims, and all risks of severity ≥ medium into an LLM prompt for a second-opinion review.
Export
The point of this artifact is not the prose — it's that an agent can re-open it next month, walk the decision/claim/risk graph, and update only the parts that changed. Everything else stays put, and the Git diff stays clean.