meta living owner: Azwaan reviewed: 2026-07-06

Publication Entity Catalogue

Every entity the Publication Model can carry — its definition, source of truth, current feed status, and the Lovable destination(s) that consume it. Statuses use the tiers from the Publication Model (A live · B buildable · C awaiting · D future). This is the honest map of what data actually exists today versus what the contract is ready to carry once the platform emits it.


1 · Entities that exist in the truth layer today (Tier A/B)

These are already in the Portfolio Graph / estate; feeds are live or buildable (projection only, no new data).

Entity Definition Source of truth In graph? Feed(s) Tier
repository A source repo digested to the digest standard portal/repos/*.md + repo CLAUDE.md/README ✅ (7) reference-library, portfolio-gallery(via providers) A
capability A reusable, repo-independent capability portal/capabilities/cap-*.md ✅ (7) portfolio-gallery, reference-library, flagship-experiences A/B
system An internal grouping of repos delivering capability, positioned in a layer (Shared Skills, Intelligence Platform, Applications & Agents) portal/ventures/*.md ✅ (3, retyped system) portfolio-gallery, reference-library A
venture A business the platform serves (Inexis Digital, Consulting, Inbound Lanka, City Retreats) documented in Overview/estate; not yet a graph entity awaiting (0 as entities) portfolio-gallery, reference-library, canonical spine (stage 5) B/C
architecture exhibit A titled architecture view (diagram + caption) mermaid blocks in portal/architecture/*.md (+ capability pages) via diagrams count + body architecture-gallery A/B
flagship-experience A flagship end-to-end showcase of a capability (formerly “case study”) flagship capability page (Website Assessment) + editorial layer derived flagship-experiences B (1 live)
evidence plate A claim bound to a source citation source citations in the estate derived evidence-plates (referenced by all) B
artefact A concrete output (pack, API contract, schema, score model, report) referenced in digests; artefact itself in the repo referenced evidence-plates, flagship-experiences, intelligence-products B/C
ADR An architecture decision record portal/decisions/NNNN-*.md ✅ (7) reference-library, engineering-manual, flagship-experiences (decisions) A
principle An architecture principle portal/architecture/principles.md (H2s) ✅ (12) reference-library, story, flagship-experiences A
operating-principle A how-work-is-done principle portal/operating-model/operating-principles.md ✅ (9) reference-library, engineering-manual A
governance rule A governance objective / gate / lifecycle portal/governance/*.md ✅ (7 pages) engineering-manual A/B
glossary-term An authoritative vocabulary term portal/operating-model/glossary.md ✅ (32) reference-library A
technology A technology in the stack derived from usesTechnology edges ✅ (22) reference-library A
layer An architecture layer (1–6) virtual, from frontmatter layer ✅ (4 realised) arrival(spine), reference-library, architecture-gallery A
diagram A Mermaid diagram exhibit mermaid blocks in the estate count in diagrams architecture-gallery, story, flagship-experiences A/B
route A canonical path for an entity/page route resolver / toRoute() routes.json (all) A
canonical spine THE platform value chain (6 stages), defined once canonical/spine.json (from the layer model) derived arrival · architecture-gallery · story (by spineRef) A
navigation The single site-map / menu structure editorial + routes derived navigation.json A
search document An indexed entity for search graph + estate derived search-index.json B
editorial unit An authored narrative file (hero, chapter, intro, caption) content/editorial/** (Claude-owned) authored arrival · story · galleries · flagship · captions B
intelligence-product (record) A published, versioned pack intelproducts manifests (documented in digests) partial (via capability) intelligence-products C

Note on intelligence-product: the existence and headline facts of website-assessment-pack-v1 (15 rules · 6 domains · REC-001…015 · maturity 1–5) are documented in the capability digest and can seed a minimal record. Full pack internals are not in the portal and must come from an intelproducts export (Tier C). Until then the feed is awaiting.

2 · Entities defined but NOT yet emitted (Tier C — awaiting the Intelligence Platform)

These are documented concepts in the operating model (the FIP knowledge lifecycle), but the platform (personalops/FIP) is early-development and does not emit them as data feeds. The contract reserves a shape for each; they ship awaiting with empty collections until FIP produces them. None may be invented.

Entity Definition (from the estate) Source of truth (when live) Consuming feed Tier
extraction Candidate insight pulled from raw sources by harvest scripts FIP harvest_candidates (internal) → knowledge-asset C
finding An evidence-backed issue from applying a rule to a crawled site assessment engine assessment_findings (in inexisstudios) flagship-experiences (per assessment) C
knowledge asset A structured, scoped, maturity-gated intelligence record FIP knowledge_assets (Supabase) reference-library(intel), story(facts) C
recommendation A rule-based suggested action/offer pack recommendation-library (REC-001…015) flagship-experiences, intelligence-products C
action item A tracked next action from health/review Health workQueue.items (partial ✅) + FIP living-platform (work queue ✅), engineering-manual B (health) / C (FIP)
asset A knowledge/media asset produced by the platform FIP / repos portfolio-gallery(thumbnails), flagship-experiences C
draft An unpublished, in-review artefact FIP staging / engine ai_draft (internal) — not published until approved C
domain brief Named in Phase E but not evidenced in processed docs unresolved C · unresolved

action item is a hybrid: the Health work queue already emits action items deterministically (health.json → workQueue.items) — that half is Tier B (buildable now) via living-platform.json. FIP- sourced action items remain awaiting.

domain brief and review package were requested in an earlier phase but are not substantiated in any processed repo (Concept Ownership). They are catalogued as unresolved and must not be modelled with invented data — confirm against FIP before giving them a feed.

3 · Destination coverage check

Every Lovable destination has at least one live or buildable feed, so nothing renders empty-by-omission:

Destination Has live/buildable data? Awaiting/future portion
Arrival ✅ B (spine + real stats)
Story ✅ B (chapters + facts) richer FIP-sourced facts ©
Portfolio Gallery ✅ A (capabilities, ventures) asset thumbnails ©
Flagship Experiences ✅ B (Website Assessment) additional flagships (awaiting selection)
Architecture Gallery ✅ A/B (estate diagrams)
Intelligence Products ⚠️ C awaiting (minimal WA record) full pack export
Reference Library ✅ A (full graph)
Engineering Manual ✅ B (governance + operating)
Living Platform ✅ B snapshot (health, current-state) D streaming/agent layer

Only one destination (Intelligence Products) has no fully-live feed today — correctly labelled awaiting with a minimal seed record, pending the intelproducts export.

4 · Entity → evidence requirement

Entity class Evidence requirement to publish as fact
repository, capability, venture, ADR, principle, governance, glossary, technology, layer present in the graph (already digested)
diagram / architecture exhibit Mermaid block resolvable to a source page
flagship experience every artefact resolves to an evidence-plate with a real source
intelligence-product a pack manifest reference (repo/path); else awaiting
finding, knowledge asset, recommendation, asset, draft, extraction a platform feed emitting it; else awaiting, empty
action item Health workQueue (✅) or a platform feed
domain brief, review package do not model until substantiated