Portfolio Portal
Capability maturity: operational living owner: Azwaan reviewed: 2026-07-05

Intelligence Productization — Capability

Purpose

Package the platform’s intelligence into versioned, immutable, machine-consumable packs that downstream apps pin and consume — intelligence as a stable dependency, not ad-hoc copies.

At a glance

Field Value
Slug cap-intelligence-productization
Maturity ✅ operational (as a contract)
Owning repo(s) intelproducts (data) + personalops (builder skills)
Layer(s) 3 · Intelligence Products (produced by layer 2)
Last reviewed 2026-07-05

Business value

Lets multiple ventures/apps reuse the same governed intelligence with version stability — the concrete embodiment of “knowledge referenced, never owned” (Principle 3).

Technical responsibilities

  • Hold immutable, versioned packs grouped by domain; provide consumer skills to act on them.
  • Preserve the Stage-1 → Stage-3 pack contract; enforce versioning (additive → in place; structural → new version dir).
  • Not responsible for producing intelligence (Knowledge Intelligence) or consuming it (downstream apps).

Owning repository or repositories

Repo Role
intelproducts Published packs + consumer skills
personalops Builder skills that author packs

Consuming repositories

Repo How it consumes
leadplatform Vendors intelproducts as a pinned git submodule; uses proposal-generator
outreachagent Uses outreach-messaging consumer skills

Consuming ventures

  • Inexis Digital (proposals, outreach); domain packs for cleaning & travel industries; Inbound Lanka (cinnamon-stories pack).

Inputs

Outputs

  • Versioned packs: proposal, website-assessment, cinnamon-stories, outreach-messaging; consumer skills.

Dependencies

Capability relationships

graph LR
    FIP[Knowledge Intelligence] --> CAP[[Intelligence Productization]]
    SS[Reusable AI Skills] -.underpins.-> CAP
    CAP -->|proposal pack| LEAD[leadplatform]
    CAP -->|outreach pack| OA[outreachagent]
    CAP -->|website-assessment pack| WA[[Website Assessment]]

Current maturity

✅ Operational as a data contract. Multiple packs published across 4 domains, already consumed by leadplatform (pinned submodule) and outreachagent. (Source: intelproducts digest.)

Planned evolution

New pack domains as the estate grows; MCP-server access for agent consumers; the Hermes loop to feed consumption outcomes back into pack quality.