Skip to content

ProductCapability Atlas

Start from what platforms can do.Not from what a trend deck says.

The Capability Atlas is a searchable graph of device, platform, and business primitives. Every entry records availability, freshness, confidence, and sources, so opportunity discovery starts on facts you can check.

from available to deprecated
5 availability states
enables, complements, depends on, and more
5 relationship types
with a review flag when it goes stale
Freshness per entry
one atlas, reused by every project
Workspace-owned

How it works

A map of the possible,kept current.

The atlas is shared across a workspace and fed by the same research runs that build your evidence library.

  1. 01

    Curate the atlas

    Add capabilities by hand or let research runs propose them. Each entry gets a category, platform, tags, availability, and the sources behind it.

  2. 02

    Relate what fits together

    Link entries with typed relationships: enables, complements, depends on, conflicts with, supersedes. The graph shows which combinations hold up.

  3. 03

    Select, pin, and explore

    Choose the capabilities a project may use, pin the ones that matter, exclude the rest, and run opportunity discovery from that selection.

Opportunity discovery

Combinations, not keywords.Opportunities grounded in capability.

Discovery reads your selection and strategy profile, then proposes opportunities that pair capabilities in ways a user would notice. Each candidate names the capabilities it relies on, so an unavailable one is caught at the gate rather than after the build starts.

  • Pin capabilities to insist on them, exclude them to rule them out
  • Every opportunity records the capabilities it depends on
  • Unavailable capabilities fail a hard gate during evaluation
  • Saved exploration recipes rerun the same setup later

Capabilities

Built for the questionsdiscovery keeps asking.

  • Search and filter

    Find entries by name, category, platform, or tag across the whole workspace atlas.

  • Freshness tracking

    Each capability carries the date it was last confirmed. Stale entries are flagged for review before they mislead a run.

  • Availability states

    Available, preview, restricted, deprecated, or unknown. Gates read the state, so a concept never rests on something you cannot ship.

  • Typed relationships

    Enables, complements, depends on, conflicts with, supersedes. Each link can carry a short rationale.

  • Sources on every entry

    Capabilities cite the documents they came from and carry a confidence value, like any other claim.

  • Project selections

    Projects select from the workspace atlas, so each exploration runs on a known, reviewable set of building blocks.

What you getA shared map of the possible.

One atlas for the workspace, reused by every project, and kept current by the research that feeds your evidence.

  • A capability graph your whole team can edit
  • Availability and freshness on every entry
  • Relationships that explain which combinations work
  • Project selections with pins and exclusions
  • Opportunity candidates tied to named capabilities
  • Sources and confidence for each capability

Map what is possible,then find what is worth it.

Explore the atlas in the sample project, then add the capabilities your team knows best.