Portfolio Portal
Operating Model living owner: Azwaan reviewed: 2026-07-05

Knowledge Asset Lifecycle

The lifecycle of information as it is progressively refined from raw source into commercial outcome. Each stage records owner, lifecycle, consumers, persistence, and evolution, grounded in documented evidence. Uncertainty is flagged where the portal’s evidence is incomplete.

The lifecycle

graph TD
    RS[Raw Sources] --> EK[Extracted Knowledge]
    EK --> KA[Knowledge Assets]
    KA --> INT[Intelligence]
    INT --> IP[Intelligence Products]
    IP --> CAP[Capabilities]
    CAP --> CX[Customer Experiences]
    CX --> CO[Commercial Outcomes]
    CO -. feedback (future Hermes, one-way) .-> IP

Stage detail

1 · Raw Sources

  • Meaning: unstructured founder knowledge — markdown docs (knowledge estate, 46 registered / ~4,600 lines), ad-hoc captures (voice, articles, agent research, legacy KB), market signals, and website URLs.
  • Owner: the founder / FIP (personalops). Website URLs are supplied to the assessment engine.
  • Lifecycle: authored/collected continuously; never the retrieval layer (“documents are the source, not the asset”).
  • Consumers: the extraction/harvest pipeline.
  • Persistence: Git markdown (authoritative narrative), plus incoming captures.
  • Evolution: grows continuously; markdown remains the authoritative narrative even after extraction.

2 · Extracted Knowledge

  • Meaning: candidate insights pulled from sources by harvest/extraction scripts — harvest_candidates.
  • Owner: FIP harvest pipeline.
  • Lifecycle: transient — a staging state awaiting human review; not yet canonical.
  • Consumers: the founder (review queue).
  • Persistence: staging tables (ingestion_queue, harvest_candidates) until approved or rejected.
  • Evolution: promoted to a Knowledge Asset on approval, or discarded.

3 · Knowledge Assets

  • Meaning: structured, scoped, maturity-gated records — the canonical intelligence store (knowledge_assets).
  • Owner: FIP (personalops) — one canonical store, no duplication.
  • Lifecycle: maturity working → ready → proven → archived; working internal-only, ready/proven external-facing.
  • Consumers: retrieval (search_assets), pack builders, agents.
  • Persistence: Supabase PostgreSQL (canonical).
  • Evolution: re-scoped/re-matured by the founder; post-MVP relationship graph & semantic search.

4 · Intelligence

  • Meaning: distilled, proven intelligence ready to be productised (the higher-maturity subset of assets + synthesis).
  • Owner: FIP.
  • Lifecycle: the input to pack synthesis; matures via the approval/maturity model.
  • Consumers: builder skills (intelligence-pack-publisher).
  • Persistence: in knowledge_assets; synthesised views are generated, not a new store.
  • Evolution: feeds new/updated packs.

5 · Intelligence Products

  • Meaning: versioned, immutable, machine-consumable packs (proposal, website-assessment, cinnamon-stories, outreach-messaging).
  • Owner: intelproducts (published by FIP builder skills; FIP does not consume them).
  • Lifecycle: immutable once published; additive → v1.x in place, structural → new v2 dir.
  • Consumers: the assessment engine, leadplatform, outreachagent, consumer skills.
  • Persistence: immutable versioned Git; vendored into consumers as pinned submodules.
  • Evolution: re-run the builder skill → publish the next version.

6 · Capabilities

  • Meaning: reusable business/technical capabilities (e.g. Website Assessment) that apply products to produce outputs.
  • Owner: the Capability Registry; some capabilities currently span/are trapped in multiple repos (see Architecture Review).
  • Lifecycle: concept → early-dev → operational; tracked per capability page.
  • Consumers: ventures & apps.
  • Persistence: engine code + pinned packs + service contracts.
  • Evolution: recommended extraction into platform services (ADR 0005, proposed).

7 · Customer Experiences

  • Meaning: the outputs customers touch — assessment reports, Commercial Opportunity Profiles, proposals, outreach, travel journeys.
  • Owner: the ventures/apps (inexisstudios, outreachagent, future venture front-ends).
  • Lifecycle: produced per prospect/engagement; gated by human approval (“nothing auto-sent”).
  • Consumers: prospects & customers of the ventures.
  • Persistence: reports (/api/assessments/:slug), CRM records, emails/proposals.
  • Evolution: improves as packs and capabilities improve.

8 · Commercial Outcomes

  • Meaning: the business results — won engagements, website replacements, bookings, revenue.
  • Owner: the ventures (Inexis Digital, Inexis Consulting, Inbound Lanka, City Retreats).
  • Lifecycle: the end of the value chain; the source of feedback signals.
  • Consumers: the founder (strategy); (future) the Hermes learning loop.
  • Persistence: CRM / venture systems (outside the processed repos — uncertainty recorded).
  • Evolution: outcomes should feed back to re-weight intelligence — planned, not built (Hermes).

Ownership & persistence summary

Stage Owner Persistence Consumers Status
Raw Sources Founder / FIP Git markdown Harvest ✅
Extracted Knowledge FIP harvest Staging tables Review queue ✅
Knowledge Assets FIP Supabase Retrieval, builders 🔶 (schema built; UI phases pending)
Intelligence FIP Supabase (subset) Builders 🔶
Intelligence Products intelproducts Immutable Git Engine, apps ✅ contract
Capabilities Capability Registry Code + packs Ventures 🔶 mixed
Customer Experiences Ventures/apps Reports, CRM Customers 🔶 (mostly mock cross-repo)
Commercial Outcomes Ventures Venture systems Founder, (future) Hermes 🧭 feedback unbuilt

Evidence boundary: stages 7–8 partly rely on systems outside the four processed repos (CRM, venture front-ends); their persistence is asserted only where documented. The feedback edge (8 → 5) is designed, not implemented.