Capability map

What the software does — and what remains to be proven

Capabilities are organized by the business task rather than by internal tool names. Statuses refer to specific evidence: a live reader experience, a bounded test, implemented code, or a future direction.

Research, strategy, creative

Discover and produce

Research and problem discovery · Developing

Find the language, audience and problems around which useful digital properties could be built. End-to-end acquisition learning is not verified.

Strategy and planning · Developing

Map problem → audience → message → journey → offer → channel → outcome, preserving human judgment.

The functional chain

Different capabilities, one operating direction

Six distinct conceptual tools connected from research and editorial production to publishing and evidence-led revision
Illustrative capability chain. These components are at different stages of implementation and verification.

Evidence boundary: A visible webpage or an image job proves a particular output can be produced. It does not prove traffic acquisition, customer demand or commercial effectiveness.

Promotion, conversion, measurement

Reach and convert

Promotion and acquisition · Developing

Campaign runners and channel integration are a strategic direction. Autonomous paid acquisition is not claimed live.

Tracking and experimentation · Built, not proven end to end

Tracking configuration and experimental structures exist. Cross-channel attribution and measured profitability are not established.

Knowledge accumulation and learning · Planned closed loop

Use observed behavior to maintain a perishable Knowledge Property. Measurable commercial learning is a future proof point.

How labels work: Verified live means a specific outcome was observed on a deployed service. Tested means a named controlled case passed. Built but not proven live means implementation exists without the required production result. Planned is an intent. Illustrative is a sample, not production evidence. Unverified means more information is needed.

Operate with control

Agents and orchestration · Workflow-specific

Specialized agents can operate within supported tools and permissions. There is no blanket claim of independent end-to-end operation.

Further reading