Publication Feed Dependency Map

Complete traceability repository → feed → portal for every generated feed. Read with the Data Contract and Pipeline. Each block lists the feed’s full dependency set and behaviour. OPEN: marks a dependency the final review flagged as undefined (see the Architecture Review that accompanies this document).

Legend — Approval: auto (deterministic, no new claims) · human (founder sign-off) · human+ADR (structural). Failure: what happens if generation/validation fails.

Core feeds

manifest.json

• Purpose: index of all feeds — versions, statuses, hashes; Lovable pins it.
• Source repos: — · Markdown: — · Graph: feed list · Health: — · Platform: — · Editorial: —
• Generated artefacts: the manifest itself.
• Destinations: all · Components: app bootstrap / version pinner.
• Regeneration trigger: any feed republished. · Approval: auto (derived).
• Validation: manifest-integrity (every feed listed; hashes match). · Failure: publish aborts (nothing ships without a manifest).

routes.json

• Purpose: canonical route + link resolution for every entity/page.
• Repos: — · Markdown: all portal/** (paths) · Graph: every node’s route/id/entityType · Health: — · Platform: — · Editorial: —
• Generated artefacts: route table.
• Destinations: all · Components: every link/router.
• Trigger: estate change (new/moved page). · Approval: auto.
• Validation: routes-resolve (covers every ref in publication/**). · Failure: publish aborts (dead links are unshippable).

portfolio-graph.json (existing)

• Purpose: the structured truth — nodes + typed edges + stats.
• Repos: all (via digests) · Markdown: all portal/** · Graph: self · Health: — · Platform: ⏳ awaiting · Editorial: —
• Generated artefacts: graph.
• Destinations: Reference Library, Portfolio Gallery, Architecture Gallery, Arrival (stats) · Components: all data-bound.
• Trigger: estate change. · Approval: human (digest content is human-reviewed upstream).
• Validation: graph build (no orphan digests, links resolve). · Failure: downstream feeds not regenerated (stale set stays canonical).

health.json (existing)

• Purpose: deterministic health metrics over the graph.
• Repos: — · Markdown: current-state (thresholds) · Graph: whole graph · Health: self · Platform: — · Editorial: —
• Generated artefacts: scores, coverage, workQueue, relationships.
• Destinations: Living Platform · Components: HealthDashboard, WorkQueue.
• Trigger: graph change. · Approval: auto (deterministic; no claims).
• Validation: reproducibility (byte-identical across runs). · Failure: previous snapshot stays.

evidence-plates.json

• Purpose: the provenance store — claims bound to sources; referenced by all claim-bearing feeds.
• Repos: all cited (inexisstudios, intelproducts, personalops, …) · Markdown: every page carrying a source citation · Graph: node bodies/links · Health: — · Platform: ⏳ (findings/assets awaiting) · Editorial: plate captions.
• Generated artefacts: plate records with status.
• Destinations: Flagship Experiences, Intelligence Products, Story, Architecture Gallery · Components: EvidencePlate.
• Trigger: estate change · new citation. · Approval: human (a verified plate is a factual claim).
• Validation: evidence-sourced (verified ⇒ resolvable source). · Failure: unsourced claims downgrade to awaiting; publish continues.

canonical/spine.json

• Purpose: THE Platform Spine — the single value chain, defined once and referenced by every destination.
• Repos: — · Markdown: the layer model (architecture) · Graph: layers · Health: — · Platform: — · Editorial: —
• Generated artefacts: 6 ordered stages (Knowledge → Capabilities → Intelligence Products → Applications → Ventures → Customer Outcomes).
• Destinations: Arrival, Architecture Gallery, Story (by spineRef) · Components: HeroSpine, ValueChain.
• Trigger: layer-model change (rare). · Approval: auto (reference).
• Validation: spine-single-source (no other feed inlines stages). · Failure: previous version stays.

navigation.json

• Purpose: the only navigation/site-map source Lovable consumes.
• Repos: — · Markdown: — · Graph: routes · Health: — · Platform: — · Editorial: labels, order, visibility.
• Generated artefacts: destination + section nav tree (+ future reserved destinations).
• Destinations: all (chrome) · Components: TopNav, SiteMap, Menu.
• Trigger: new destination · editorial nav change. · Approval: human (labels/order editorial).
• Validation: navigation-single-source (every route/feed resolves; exactly one nav). · Failure: previous version stays.

search-index.json

• Purpose: the only search source; keyword now, semantic-search compatible (reserved).
• Repos: all (via graph) · Markdown: excerpts · Graph: every indexed entity · Health: — · Platform: — · Editorial: aliases, boosts.
• Generated artefacts: search documents (+ reserved embeddingRef).
• Destinations: all (search) · Components: SearchOverlay, SearchList.
• Trigger: graph change. · Approval: auto (reference).
• Validation: search-single-source (every doc route resolves). · Failure: previous version stays.

Destination feeds

arrival.json — Arrival

• Purpose: the 15-second first screen (thesis, spine, architectural stats, entries).
• Repos: — · Markdown: — · Graph: stats (capabilities/layers/repos/adrs/principles) + spineRef → canonical/spine.json · Health: — · Platform: — · Editorial: content/editorial/arrival.md (eyebrow/headline/lede/CTAs).
• Generated artefacts: arrival payload (references spine, does not inline it).
• Destinations: Arrival · Components: Hero, HeroSpine, ScaleStrip, EntryChips.
• Trigger: graph stats change · editorial change. · Approval: human (publicationClass:editorial).
• Validation: stats-cross-check, enums-valid, spine-single-source. · Failure: previous version stays.
• RESOLVED (I-2): canonical spine now single-sourced in canonical/spine.json; arrival references it.

story.json — Story

• Purpose: the 10-chapter guided narrative with sourced facts.
• Repos: — · Markdown: principles/architecture (facts) · Graph: entities for facts/exploreLinks · Health: meta stats · Platform: — · Editorial: content/editorial/story/* (all chapter prose, takeaways, transitions).
• Generated artefacts: chapters + facts (each with EvidenceRef).
• Destinations: Story · Components: ChapterReader, TakeawayCard, ExhibitViewer, ExploreLinks.
• Trigger: editorial change · graph change (facts). · Approval: human (publicationClass:editorial).
• Validation: evidence-sourced, editorial-boundary. · Failure: previous version stays.
• RESOLVED (C-1): chapter prose now lives in the Claude-owned Editorial Source Layer, not story.astro.

portfolio-gallery.json — Portfolio Gallery

• Purpose: browsable grid of capabilities + systems + ventures (business).
• Repos: — · Markdown: capabilities, ventures · Graph: capability/system nodes + providedBy/consumedBy edges (ventures awaiting) · Health: — · Platform: ⏳ asset thumbnails · Editorial: flagship flags, ordering.
• Generated artefacts: gallery items.
• Destinations: Portfolio Gallery · Components: GalleryGrid, GalleryCard.
• Trigger: graph change · curation change. · Approval: human (flagship/order is editorial).
• Validation: enums-valid, routes-resolve. · Failure: previous version stays.
• RESOLVED (I-1): system and venture are now distinct entityTypes; business ventures are reserved first-class (awaiting).

flagship-experiences.json — Flagship Experiences

• Purpose: flagship end-to-end capability showcases (Website Assessment first).
• Repos: inexisstudios, intelproducts, personalops, website-intelligence-lab (via digests) · Markdown: the flagship capability page · Graph: capabilityRef, layers, decisions · Health: — · Platform: ⏳ live findings/outputs · Editorial: selection + narrative framing.
• Generated artefacts: flagship-experience records + journey diagram ref + artefact (evidence) refs.
• Destinations: Flagship Experiences · Components: CaseStudyLayout, JourneyDiagram, ArtefactPlate, MaturityBreakdown.
• Trigger: flagship page edit · new flagship selected. · Approval: human (customer-facing claims).
• Validation: evidence-sourced (artefacts resolve to plates). · Failure: previous version stays.
• RESOLVED (I-4): canonicalised to “Flagship Experiences” / flagship-experiences.json / flagship-experience everywhere.

architecture-gallery.json — Architecture Gallery

• Purpose: architecture exhibits (diagrams at altitudes) + the canonical picture.
• Repos: — · Markdown: portal/architecture/*, capability pages (Mermaid) · Graph: diagrams count, related entities · Health: — · Platform: — · Editorial: canonical flag, captions.
• Generated artefacts: exhibits (DiagramRefs) + captions.
• Destinations: Architecture Gallery, Story (exhibits) · Components: ExhibitViewer, DiagramRenderer.
• Trigger: estate diagram change. · Approval: human (captions).
• Validation: schema-valid, routes-resolve (each exhibit → source page). · Failure: previous version stays.

intelligence-products.json — Intelligence Products (awaiting)

• Purpose: the versioned packs the platform publishes.
• Repos: intelproducts (OPEN: pack-manifest export) · Markdown: capability digest (seed record) · Graph: consumers · Health: — · Platform: ⏳ pack export · Editorial: —
• Generated artefacts: product records (status:"awaiting" until export).
• Destinations: Intelligence Products · Components: ProductCard, ProductDetail, VersionBadge.
• Trigger: intelproducts export lands. · Approval: human+ADR (tier promotion).
• Validation: evidence-sourced, maturity-honest. · Failure: stays awaiting (empty + seed).

reference-library.json — Reference Library

• Purpose: searchable index of every reference entity + relationships.
• Repos: all (digests) · Markdown: all reference pages · Graph: entire graph (nodes + edges) · Health: — · Platform: ⏳ knowledge-assets · Editorial: —
• Generated artefacts: grouped collections + relationships.
• Destinations: Reference Library · Components: ReferenceIndex, EntityCard, RelationshipRail, SearchList.
• Trigger: graph change. · Approval: auto (pure graph projection, no new claims).
• Validation: no-invented (adds no entity the graph lacks), routes-resolve. · Failure: previous version stays.
• RESOLVED (I-5, I-7): redefined as a thin index (not a graph copy), with shape:"index" reserved for scale; a dedicated search-index.json feed now exists.

engineering-manual.json — Engineering Manual

• Purpose: governance + operating-model how-to/reference.
• Repos: — · Markdown: portal/governance/*, portal/operating-model/* · Graph: governance/operating nodes, related ADRs · Health: — · Platform: — · Editorial: —
• Generated artefacts: section records (+ steps for how-to).
• Destinations: Engineering Manual · Components: ManualSection, StepList.
• Trigger: estate change. · Approval: auto (projection).
• Validation: schema-valid, enums-valid (docType). · Failure: previous version stays.

living-platform.json — Living Platform (snapshot buildable; live layer future)

• Purpose: operational awareness — health snapshot, current state, roadmap, changelog.
• Repos: — · Markdown: current-state (dashboard/roadmap/changelog) · Graph: — · Health: whole health.json · Platform: ⏳ live telemetry (future) · Editorial: —
• Generated artefacts: health snapshot + state/roadmap/changelog lists + future feature flags.
• Destinations: Living Platform · Components: HealthDashboard, RoadmapList, Changelog, StatusBadge.
• Trigger: health/current-state change. · Approval: health part auto; roadmap/changelog human.
• Validation: maturity-honest (roadmap = planned), render-safe. · Failure: previous snapshot stays.
• RESOLVED (F-1): the static snapshot is a generated feed; live/streaming telemetry is the reserved live feed class under live/ (§8 model) — no redesign needed.

Traceability summary (repository → feed)

Editorial-input inventory (the human-authored surface)

RESOLVED (C-1): the Editorial Source Layer (content/editorial/**, model §7) is now the Claude-owned home for all authored narrative. Phase 0b migrates the copy currently in presentation (PlatformHero.astro, story.astro) into it. Lovable never owns editorial truth.