{
  "schema": "https://libreinfra.com/schemas/content-index-v1.json",
  "items": [
    {
      "id": "sovereignty-platforms-and-hardware",
      "type": "newsletter",
      "title": "Ownable Infrastructure Dispatch: Sovereignty, Platforms and Hardware",
      "summary": "A focused issue on the platform, site, data, server, accelerator and hardware constraints that decide whether infrastructure remains ownable.",
      "status": "published",
      "published_at": "2026-07-23T10:00:00.000Z",
      "output_url": "/newsletter/issues/sovereignty-platforms-and-hardware/",
      "visual": {
        "src": "/assets/content/sovereignty-platforms-and-hardware.svg",
        "fallback_src": "/assets/content/sovereignty-platforms-and-hardware.svg",
        "alt": "Abstract LibreInfra dispatch artwork connecting sovereignty, platforms, edge systems and hardware boundaries",
        "credit": null,
        "credit_url": null
      },
      "topics": [
        "Ownable infrastructure",
        "Open platforms",
        "Security and governance",
        "AI readiness",
        "Operations"
      ],
      "service_families": [
        "Strategy and assessment",
        "Platform engineering",
        "Automation and operations",
        "Security and governance",
        "Transfer and enablement"
      ]
    },
    {
      "id": "a-server-fleet-is-a-power-cooling-firmware-and-spare-parts-system",
      "type": "field-note",
      "title": "A server fleet is a power, cooling, firmware and spare-parts system",
      "summary": "A LibreInfra field note on physical infrastructure control planes, BMCs, firmware baselines, spares and hardware recovery.",
      "status": "published",
      "published_at": "2026-07-21T10:00:00.000Z",
      "output_url": "/insights/field-notes/a-server-fleet-is-a-power-cooling-firmware-and-spare-parts-system/",
      "visual": {
        "src": "https://images.pexels.com/photos/34818811/pexels-photo-34818811.jpeg?cs=srgb&dl=pexels-landiva-weber-34818811.jpg&fm=jpg",
        "fallback_src": "/assets/content/a-server-fleet-is-a-power-cooling-firmware-and-spare-parts-system.svg",
        "alt": "Abstract line-and-node server fleet artwork showing power, cooling, firmware, management and spare-parts paths.",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/abstract-blue-and-purple-curved-lines-design-34818811/"
      },
      "topics": [
        "Ownable infrastructure",
        "Operations",
        "Security and governance"
      ],
      "service_families": [
        "Platform engineering",
        "Automation and operations",
        "Transfer and enablement"
      ]
    },
    {
      "id": "gpus-run-llms-because-memory-movement-is-the-real-workload",
      "type": "field-note",
      "title": "GPUs run LLMs because memory movement is the real workload",
      "summary": "A LibreInfra field note on accelerator sizing for LLM inference, memory capacity, KV cache, interconnect and software support.",
      "status": "published",
      "published_at": "2026-07-20T10:00:00.000Z",
      "output_url": "/insights/field-notes/gpus-run-llms-because-memory-movement-is-the-real-workload/",
      "visual": {
        "src": "https://images.pexels.com/photos/30547567/pexels-photo-30547567.jpeg?cs=srgb&dl=pexels-pachon-in-motion-30547567.jpg&fm=jpg",
        "fallback_src": "/assets/content/gpus-run-llms-because-memory-movement-is-the-real-workload.svg",
        "alt": "Abstract line-and-node AI hardware artwork representing model memory, bandwidth and accelerator interconnects.",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/abstract-digital-circuit-block-graphic-art-30547567/"
      },
      "topics": [
        "AI readiness",
        "Ownable infrastructure",
        "Operations"
      ],
      "service_families": [
        "Strategy and assessment",
        "Platform engineering",
        "Data foundations"
      ]
    },
    {
      "id": "the-r730-generation-is-still-useful-inside-a-deliberate-boundary",
      "type": "field-note",
      "title": "The R730 generation is still useful—inside a deliberate boundary",
      "summary": "A LibreInfra field note on using R730-class hardware responsibly for labs, backup targets and recoverable internal platforms.",
      "status": "published",
      "published_at": "2026-07-19T10:00:00.000Z",
      "output_url": "/insights/field-notes/the-r730-generation-is-still-useful-inside-a-deliberate-boundary/",
      "visual": {
        "src": "https://images.pexels.com/photos/30180436/pexels-photo-30180436.jpeg?cs=srgb&dl=pexels-yakup-gokdeniz-30180436.jpg&fm=jpg",
        "fallback_src": "/assets/content/the-r730-generation-is-still-useful-inside-a-deliberate-boundary.svg",
        "alt": "Abstract line-and-node legacy hardware artwork representing controlled reuse, spares and recoverable service boundaries.",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/abstract-light-trails-on-a-black-background-30180436/"
      },
      "topics": [
        "Ownable infrastructure",
        "Operations",
        "Security and governance"
      ],
      "service_families": [
        "Strategy and assessment",
        "Platform engineering",
        "Transfer and enablement"
      ]
    },
    {
      "id": "a-server-type-is-a-workload-decision-not-a-chassis-preference",
      "type": "field-note",
      "title": "A server type is a workload decision, not a chassis preference",
      "summary": "A LibreInfra field note on choosing server types from workload shape, serviceability, power, cooling and failure boundaries.",
      "status": "published",
      "published_at": "2026-07-17T10:00:00.000Z",
      "output_url": "/insights/field-notes/a-server-type-is-a-workload-decision-not-a-chassis-preference/",
      "visual": {
        "src": "https://images.pexels.com/photos/31066046/pexels-photo-31066046.jpeg?cs=srgb&dl=pexels-kdadan97-31066046.jpg&fm=jpg",
        "fallback_src": "/assets/content/a-server-type-is-a-workload-decision-not-a-chassis-preference.svg",
        "alt": "Abstract line-and-node hardware artwork representing workload shape, chassis constraints and lifecycle trade-offs.",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/colorful-abstract-gradient-texture-wallpaper-31066046/"
      },
      "topics": [
        "Ownable infrastructure",
        "Operations",
        "AI readiness"
      ],
      "service_families": [
        "Strategy and assessment",
        "Platform engineering",
        "Transfer and enablement"
      ]
    },
    {
      "id": "a-historian-a-broker-and-a-data-lake-are-different-systems",
      "type": "field-note",
      "title": "A historian, a broker and a data lake are different systems",
      "summary": "A LibreInfra field note on brokers, historians, data lakes, archives, time, asset identity and recovery contracts.",
      "status": "published",
      "published_at": "2026-07-16T10:00:00.000Z",
      "output_url": "/insights/field-notes/a-historian-a-broker-and-a-data-lake-are-different-systems/",
      "visual": {
        "src": "https://images.pexels.com/photos/30547568/pexels-photo-30547568.jpeg?cs=srgb&dl=pexels-pachon-in-motion-30547568.jpg&fm=jpg",
        "fallback_src": "/assets/content/a-historian-a-broker-and-a-data-lake-are-different-systems.svg",
        "alt": "Abstract line-and-node industrial data artwork connecting gateways, brokers, historians and analytical stores.",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/abstract-digital-circuitry-with-glowing-effects-30547568/"
      },
      "topics": [
        "Data stewardship",
        "Operations",
        "Ownable infrastructure"
      ],
      "service_families": [
        "Data foundations",
        "Platform engineering",
        "Strategy and assessment"
      ]
    },
    {
      "id": "storage-recovery-dispatch-002",
      "type": "newsletter",
      "title": "Ownable Infrastructure Dispatch: Storage, Recovery and Data Ownership",
      "summary": "A focused issue on storage, recovery, archive, data ownership and evidence-driven infrastructure review.",
      "status": "published",
      "published_at": "2026-07-16T10:00:00.000Z",
      "output_url": "/newsletter/issues/storage-recovery-dispatch-002/",
      "visual": {
        "src": "/assets/content/storage-recovery-dispatch-002.svg",
        "fallback_src": "/assets/content/storage-recovery-dispatch-002.svg",
        "alt": "Abstract LibreInfra dispatch artwork showing layered data paths, recovery copies and governed ownership",
        "credit": null,
        "credit_url": null
      },
      "topics": [
        "Data stewardship",
        "Ownable infrastructure",
        "Operations"
      ],
      "service_families": [
        "Data foundations",
        "Strategy and assessment",
        "Automation and operations"
      ]
    },
    {
      "id": "edge-infrastructure-must-survive-the-loss-of-the-centre",
      "type": "field-note",
      "title": "Edge infrastructure must survive the loss of the centre",
      "summary": "A LibreInfra field note on edge autonomy, local identity, store-and-forward integrity, updates and recovery.",
      "status": "published",
      "published_at": "2026-07-15T10:00:00.000Z",
      "output_url": "/insights/field-notes/edge-infrastructure-must-survive-the-loss-of-the-centre/",
      "visual": {
        "src": "https://images.pexels.com/photos/29373638/pexels-photo-29373638.jpeg?cs=srgb&dl=pexels-nui-malama-29373638.jpg&fm=jpg",
        "fallback_src": "/assets/content/edge-infrastructure-must-survive-the-loss-of-the-centre.svg",
        "alt": "Abstract line-and-node edge artwork showing local site autonomy and controlled reconnection.",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/abstract-light-trails-in-motion-29373638/"
      },
      "topics": [
        "Ownable infrastructure",
        "Data stewardship",
        "Operations"
      ],
      "service_families": [
        "Platform engineering",
        "Automation and operations",
        "Transfer and enablement"
      ]
    },
    {
      "id": "infrastructure-as-code-is-only-as-ownable-as-its-state",
      "type": "field-note",
      "title": "Infrastructure as code is only as ownable as its state",
      "summary": "A LibreInfra field note on infrastructure-as-code state, provider versions, drift, execution authority and recovery.",
      "status": "published",
      "published_at": "2026-07-14T10:00:00.000Z",
      "output_url": "/insights/field-notes/infrastructure-as-code-is-only-as-ownable-as-its-state/",
      "visual": {
        "src": "https://images.pexels.com/photos/7429501/pexels-photo-7429501.jpeg?cs=srgb&dl=pexels-solenfeyissa-7429501.jpg&fm=jpg",
        "fallback_src": "/assets/content/infrastructure-as-code-is-only-as-ownable-as-its-state.svg",
        "alt": "Abstract line-and-node artwork representing infrastructure code, provider APIs and state records.",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/abstract-colorful-lines-7429501/"
      },
      "topics": [
        "Ownable infrastructure",
        "Operations",
        "Security and governance"
      ],
      "service_families": [
        "Platform engineering",
        "Automation and operations",
        "Security and governance"
      ]
    },
    {
      "id": "kubernetes-is-an-orchestration-engine-not-an-operating-model",
      "type": "field-note",
      "title": "Kubernetes is an orchestration engine, not an operating model",
      "summary": "A LibreInfra field note on treating Kubernetes as one control plane inside a wider platform contract.",
      "status": "published",
      "published_at": "2026-07-13T10:00:00.000Z",
      "output_url": "/insights/field-notes/kubernetes-is-an-orchestration-engine-not-an-operating-model/",
      "visual": {
        "src": "https://images.pexels.com/photos/30111471/pexels-photo-30111471.jpeg?cs=srgb&dl=pexels-steve-30111471.jpg&fm=jpg",
        "fallback_src": "/assets/content/kubernetes-is-an-orchestration-engine-not-an-operating-model.svg",
        "alt": "Abstract line-and-node platform artwork representing Kubernetes control planes and workload boundaries.",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/dynamic-abstract-lines-in-vibrant-neon-colors-30111471/"
      },
      "topics": [
        "Ownable infrastructure",
        "Operations",
        "Security and governance"
      ],
      "service_families": [
        "Platform engineering",
        "Automation and operations",
        "Transfer and enablement"
      ]
    },
    {
      "id": "ai-agents-are-infrastructure-identities-not-assistants-with-tools",
      "type": "field-note",
      "title": "AI agents are infrastructure identities, not assistants with tools",
      "summary": "A LibreInfra field note on governing AI agents as delegated infrastructure identities with bounded permissions, memory, tools, budgets and evidence.",
      "status": "published",
      "published_at": "2026-07-12T10:00:00.000Z",
      "output_url": "/insights/field-notes/ai-agents-are-infrastructure-identities-not-assistants-with-tools/",
      "visual": {
        "src": "/assets/articles/article-abstract-agents.jpg",
        "fallback_src": "/assets/content/ai-agents-are-infrastructure-identities-not-assistants-with-tools.svg",
        "alt": "Abstract AI systems artwork representing delegated authority, tools and identity control",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/34229982/"
      },
      "topics": [
        "AI readiness",
        "Security and governance",
        "Ownable infrastructure"
      ],
      "service_families": [
        "Strategy and assessment",
        "Security and governance",
        "Automation and operations"
      ]
    },
    {
      "id": "digital-sovereignty-is-the-ability-to-change-course",
      "type": "field-note",
      "title": "Digital sovereignty is the ability to change course",
      "summary": "A LibreInfra field note on digital sovereignty across authority, data, identity, operations, interoperability, open source and exit capacity.",
      "status": "published",
      "published_at": "2026-07-11T10:00:00.000Z",
      "output_url": "/insights/field-notes/digital-sovereignty-is-the-ability-to-change-course/",
      "visual": {
        "src": "/assets/articles/article-abstract-sovereignty.jpg",
        "fallback_src": "/assets/content/digital-sovereignty-is-the-ability-to-change-course.svg",
        "alt": "Abstract digital artwork representing institutional control, governance and digital sovereignty",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/34040736/"
      },
      "topics": [
        "Ownable infrastructure",
        "Security and governance",
        "Open platforms"
      ],
      "service_families": [
        "Strategy and assessment",
        "Security and governance",
        "Transfer and enablement"
      ]
    },
    {
      "id": "sustainable-infrastructure-begins-with-deciding-what-should-not-run",
      "type": "field-note",
      "title": "Sustainable infrastructure begins with deciding what should not run",
      "summary": "A LibreInfra field note on infrastructure sustainability, demand, useful work, data retention, hardware lifecycle, location and AI workload classes.",
      "status": "published",
      "published_at": "2026-07-10T10:00:00.000Z",
      "output_url": "/insights/field-notes/sustainable-infrastructure-begins-with-deciding-what-should-not-run/",
      "visual": {
        "src": "/assets/articles/article-abstract-sustainability.jpg",
        "fallback_src": "/assets/content/sustainable-infrastructure-begins-with-deciding-what-should-not-run.svg",
        "alt": "Abstract systems artwork representing sustainable infrastructure demand and workload choices",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/34229979/"
      },
      "topics": [
        "Ownable infrastructure",
        "Operations",
        "AI readiness"
      ],
      "service_families": [
        "Strategy and assessment",
        "Data foundations",
        "Automation and operations"
      ]
    },
    {
      "id": "open-source-without-maintenance-is-borrowed-infrastructure",
      "type": "field-note",
      "title": "Open source without maintenance is borrowed infrastructure",
      "summary": "A LibreInfra field note on open-source maintenance, dependency graphs, stewardship, contribution, forks and operational continuity.",
      "status": "published",
      "published_at": "2026-07-09T10:00:00.000Z",
      "output_url": "/insights/field-notes/open-source-without-maintenance-is-borrowed-infrastructure/",
      "visual": {
        "src": "/assets/articles/article-abstract-maintenance.jpg",
        "fallback_src": "/assets/content/open-source-without-maintenance-is-borrowed-infrastructure.svg",
        "alt": "Abstract open systems artwork representing shared software dependencies and maintenance stewardship",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/34229976/"
      },
      "topics": [
        "Open platforms",
        "Ownable infrastructure",
        "Security and governance"
      ],
      "service_families": [
        "Strategy and assessment",
        "Platform engineering",
        "Transfer and enablement"
      ]
    },
    {
      "id": "control-source-and-exit",
      "type": "newsletter",
      "title": "Ownable Infrastructure Dispatch: Control, Source and Evidence",
      "summary": "A focused issue on accounts, source access, identity, exit, reproducibility, automation, observability, open weights, maintenance and sustainable demand.",
      "status": "published",
      "published_at": "2026-07-09T10:00:00.000Z",
      "output_url": "/newsletter/issues/control-source-and-exit/",
      "visual": {
        "src": "/assets/articles/newsletter-abstract-control-source-exit.jpg",
        "fallback_src": "/assets/content/control-source-and-exit.svg",
        "alt": "Abstract LibreInfra dispatch artwork connecting control, source, identity and exit paths",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/33485190/"
      },
      "topics": [
        "Ownable infrastructure",
        "Open platforms",
        "Security and governance",
        "AI readiness",
        "Operations"
      ],
      "service_families": [
        "Strategy and assessment",
        "Platform engineering",
        "Automation and operations",
        "Security and governance",
        "Transfer and enablement"
      ]
    },
    {
      "id": "open-weights-do-not-make-ai-infrastructure-ownable",
      "type": "field-note",
      "title": "Open weights do not make AI infrastructure ownable",
      "summary": "A LibreInfra field note on open weights, rights, runtime, evaluation, organisational data, recovery and AI service ownership.",
      "status": "published",
      "published_at": "2026-07-08T10:00:00.000Z",
      "output_url": "/insights/field-notes/open-weights-do-not-make-ai-infrastructure-ownable/",
      "visual": {
        "src": "/assets/articles/article-abstract-open-weights.jpg",
        "fallback_src": "/assets/content/open-weights-do-not-make-ai-infrastructure-ownable.svg",
        "alt": "Abstract AI infrastructure artwork representing model runtime, evaluation and governance layers",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/34215698/"
      },
      "topics": [
        "AI readiness",
        "Ownable infrastructure",
        "Open platforms"
      ],
      "service_families": [
        "Strategy and assessment",
        "Platform engineering",
        "Security and governance"
      ]
    },
    {
      "id": "observability-should-produce-evidence-not-just-dashboards",
      "type": "field-note",
      "title": "Observability should produce evidence, not just dashboards",
      "summary": "A LibreInfra field note on observability as evidence: control-plane events, recovery records, alerts, retention and incident reconstruction.",
      "status": "published",
      "published_at": "2026-07-07T10:00:00.000Z",
      "output_url": "/insights/field-notes/observability-should-produce-evidence-not-just-dashboards/",
      "visual": {
        "src": "/assets/articles/article-abstract-observability.jpg",
        "fallback_src": "/assets/content/observability-should-produce-evidence-not-just-dashboards.svg",
        "alt": "Abstract data and systems artwork representing operational evidence beyond dashboards",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/34014428/"
      },
      "topics": [
        "Operations",
        "Security and governance",
        "Ownable infrastructure"
      ],
      "service_families": [
        "Automation and operations",
        "Security and governance",
        "Transfer and enablement"
      ]
    },
    {
      "id": "automation-that-cannot-be-transferred-is-another-dependency",
      "type": "field-note",
      "title": "Automation that cannot be transferred is another dependency",
      "summary": "A LibreInfra field note on automation ownership, transferability, state, credentials, failure behaviour and operational evidence.",
      "status": "published",
      "published_at": "2026-07-06T10:00:00.000Z",
      "output_url": "/insights/field-notes/automation-that-cannot-be-transferred-is-another-dependency/",
      "visual": {
        "src": "/assets/articles/article-abstract-automation.jpg",
        "fallback_src": "/assets/content/automation-that-cannot-be-transferred-is-another-dependency.svg",
        "alt": "Abstract workflow artwork representing automation control and transfer between operators",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/34215697/"
      },
      "topics": [
        "Operations",
        "Ownable infrastructure",
        "Open platforms"
      ],
      "service_families": [
        "Automation and operations",
        "Platform engineering",
        "Transfer and enablement"
      ]
    },
    {
      "id": "reproducibility-is-an-infrastructure-property-not-a-documentation-task",
      "type": "field-note",
      "title": "Reproducibility is an infrastructure property, not a documentation task",
      "summary": "A LibreInfra field note on clean reconstruction, controlled inputs, drift, provenance and why reproducibility must be exercised rather than merely documented.",
      "status": "published",
      "published_at": "2026-07-05T10:00:00.000Z",
      "output_url": "/insights/field-notes/reproducibility-is-an-infrastructure-property-not-a-documentation-task/",
      "visual": {
        "src": "/assets/articles/article-abstract-reproducibility.jpg",
        "fallback_src": "/assets/content/reproducibility-is-an-infrastructure-property-not-a-documentation-task.svg",
        "alt": "Abstract architecture artwork showing controlled inputs becoming verified infrastructure state",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/34886750/"
      },
      "topics": [
        "Ownable infrastructure",
        "Operations",
        "Security and governance"
      ],
      "service_families": [
        "Strategy and assessment",
        "Automation and operations",
        "Transfer and enablement"
      ]
    },
    {
      "id": "managed-platforms-need-an-exit-design-before-migration",
      "type": "field-note",
      "title": "Managed platforms need an exit design before migration becomes urgent",
      "summary": "A LibreInfra field note on designing exit across data, configuration, identity, evidence, operations and supplier boundaries.",
      "status": "published",
      "published_at": "2026-07-04T10:00:00.000Z",
      "output_url": "/insights/field-notes/managed-platforms-need-an-exit-design-before-migration/",
      "visual": {
        "src": "/assets/articles/article-abstract-exit.jpg",
        "fallback_src": "/assets/content/managed-platforms-need-an-exit-design-before-migration.svg",
        "alt": "Abstract managed-platform exit sequence preserving authority, data context, evidence and closure",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/33485202/"
      },
      "topics": [
        "Ownable infrastructure",
        "Operations",
        "Security and governance"
      ],
      "service_families": [
        "Strategy and assessment",
        "Transfer and enablement",
        "Security and governance"
      ]
    },
    {
      "id": "identity-is-the-control-plane-infrastructure-diagrams-leave-out",
      "type": "field-note",
      "title": "Identity is the control plane most infrastructure diagrams leave out",
      "summary": "A LibreInfra field note on identity as the control plane for human access, workload access, recovery authority and evidence.",
      "status": "published",
      "published_at": "2026-07-03T10:00:00.000Z",
      "output_url": "/insights/field-notes/identity-is-the-control-plane-infrastructure-diagrams-leave-out/",
      "visual": {
        "src": "/assets/articles/article-abstract-identity.jpg",
        "fallback_src": "/assets/content/identity-is-the-control-plane-infrastructure-diagrams-leave-out.svg",
        "alt": "Abstract identity control plane connecting human, workload and recovery authority to infrastructure actions",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/34229974/"
      },
      "topics": [
        "Security and governance",
        "Ownable infrastructure",
        "Operations"
      ],
      "service_families": [
        "Security and governance",
        "Strategy and assessment",
        "Automation and operations"
      ]
    },
    {
      "id": "open-source-does-not-automatically-make-infrastructure-ownable",
      "type": "field-note",
      "title": "Open source does not automatically make infrastructure ownable",
      "summary": "A LibreInfra field note on why open-source rights must be connected to reproducibility, recovery, maintenance and transfer.",
      "status": "published",
      "published_at": "2026-07-02T10:00:00.000Z",
      "output_url": "/insights/field-notes/open-source-does-not-automatically-make-infrastructure-ownable/",
      "visual": {
        "src": "/assets/articles/article-abstract-open-source.jpg",
        "fallback_src": "/assets/content/open-source-does-not-automatically-make-infrastructure-ownable.svg",
        "alt": "Abstract open-source operating chain from source through build, release, deployment and recovery",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/34229971/"
      },
      "topics": [
        "Ownable infrastructure",
        "Open platforms",
        "Operations"
      ],
      "service_families": [
        "Platform engineering",
        "Automation and operations",
        "Transfer and enablement"
      ]
    },
    {
      "id": "owning-the-account-is-not-owning-the-infrastructure",
      "type": "field-note",
      "title": "Owning the account is not the same as owning the infrastructure",
      "summary": "A LibreInfra field note on why infrastructure ownership depends on authority, recovery evidence and transferability, not merely accounts or invoices.",
      "status": "published",
      "published_at": "2026-07-01T10:00:00.000Z",
      "output_url": "/insights/field-notes/owning-the-account-is-not-owning-the-infrastructure/",
      "visual": {
        "src": "/assets/articles/article-abstract-ownership.jpg",
        "fallback_src": "/assets/content/owning-the-account-is-not-owning-the-infrastructure.svg",
        "alt": "Abstract infrastructure ownership map connecting authority, recovery evidence and transfer paths",
        "credit": "Pexels",
        "credit_url": "https://www.pexels.com/photo/34215696/"
      },
      "topics": [
        "Ownable infrastructure",
        "Operations",
        "Security and governance"
      ],
      "service_families": [
        "Strategy and assessment",
        "Automation and operations",
        "Transfer and enablement"
      ]
    },
    {
      "id": "storage-backup-archive-different-decisions",
      "type": "guide",
      "title": "Storage, backup and archive are different decisions",
      "summary": "A practical LibreInfra guide to classifying storage, databases, lakehouses, backup, archive and data-platform layers.",
      "status": "published",
      "published_at": "2026-06-30T10:00:00.000Z",
      "output_url": "/insights/guides/storage-backup-archive-different-decisions/",
      "visual": {
        "src": "/assets/content/storage-backup-archive-different-decisions.svg",
        "fallback_src": "/assets/content/storage-backup-archive-different-decisions.svg",
        "alt": "Layered abstract storage architecture with data paths, protected vaults and analysis layers",
        "credit": null,
        "credit_url": null
      },
      "topics": [
        "Data stewardship",
        "Operations",
        "Security and governance"
      ],
      "service_families": [
        "Data foundations",
        "Strategy and assessment",
        "Automation and operations"
      ]
    },
    {
      "id": "why-storage-decisions-fail-when-teams-compare-products-instead-of-layers",
      "type": "field-note",
      "title": "Why storage decisions fail when teams compare products instead of layers",
      "summary": "A LibreInfra field note on the category errors behind storage, data platform, backup and archive decisions.",
      "status": "published",
      "published_at": "2026-06-29T10:00:00.000Z",
      "output_url": "/insights/field-notes/why-storage-decisions-fail-when-teams-compare-products-instead-of-layers/",
      "visual": {
        "src": "/assets/content/why-storage-decisions-fail-when-teams-compare-products-instead-of-layers.svg",
        "fallback_src": "/assets/content/why-storage-decisions-fail-when-teams-compare-products-instead-of-layers.svg",
        "alt": "Abstract layered infrastructure map separating product labels into architecture responsibilities and failure boundaries",
        "credit": null,
        "credit_url": null
      },
      "topics": [
        "Data stewardship",
        "Ownable infrastructure",
        "Operations"
      ],
      "service_families": [
        "Data foundations",
        "Strategy and assessment",
        "Automation and operations"
      ]
    },
    {
      "id": "ownable-infrastructure-ai-era",
      "type": "field-note",
      "title": "Ownable infrastructure for the AI era",
      "summary": "A LibreInfra field note on why AI-ready systems need open foundations, clear ownership and practical operations.",
      "status": "published",
      "published_at": "2026-06-28T10:00:00.000Z",
      "output_url": "/insights/field-notes/ownable-infrastructure-ai-era/",
      "visual": {
        "src": "/assets/content/ownable-infrastructure-ai-era.svg",
        "fallback_src": "/assets/content/ownable-infrastructure-ai-era.svg",
        "alt": "Abstract LibreInfra artwork with luminous infrastructure paths and connected decision layers",
        "credit": null,
        "credit_url": null
      },
      "topics": [
        "Ownable infrastructure",
        "AI readiness",
        "Open platforms"
      ],
      "service_families": [
        "Strategy and assessment",
        "Platform engineering",
        "Transfer and enablement"
      ]
    }
  ]
}