Edge infrastructure must survive the loss of the centre
A LibreInfra field note on edge autonomy, local identity, store-and-forward integrity, updates and recovery.
LibreInfra Field Notes
Field Notes
Readable notes about architecture, operations, ownership and transfer.
All Field Notes
Showing 16-30 of 32 articles. Page 2 of 3.
Infrastructure as code is only as ownable as its state
A LibreInfra field note on infrastructure-as-code state, provider versions, drift, execution authority and recovery.
Kubernetes is an orchestration engine, not an operating model
A LibreInfra field note on treating Kubernetes as one control plane inside a wider platform contract.
AI agents are infrastructure identities, not assistants with tools
A LibreInfra field note on governing AI agents as delegated infrastructure identities with bounded permissions, memory, tools, budgets and evidence.
Digital sovereignty is the ability to change course
A LibreInfra field note on digital sovereignty across authority, data, identity, operations, interoperability, open source and exit capacity.
Sustainable infrastructure begins with deciding what should not run
A LibreInfra field note on infrastructure sustainability, demand, useful work, data retention, hardware lifecycle, location and AI workload classes.
Open source without maintenance is borrowed infrastructure
A LibreInfra field note on open-source maintenance, dependency graphs, stewardship, contribution, forks and operational continuity.
Open weights do not make AI infrastructure ownable
A LibreInfra field note on open weights, rights, runtime, evaluation, organisational data, recovery and AI service ownership.
Observability should produce evidence, not just dashboards
A LibreInfra field note on observability as evidence: control-plane events, recovery records, alerts, retention and incident reconstruction.
Automation that cannot be transferred is another dependency
A LibreInfra field note on automation ownership, transferability, state, credentials, failure behaviour and operational evidence.
Reproducibility is an infrastructure property, not a documentation task
A LibreInfra field note on clean reconstruction, controlled inputs, drift, provenance and why reproducibility must be exercised rather than merely documented.
Managed platforms need an exit design before migration becomes urgent
A LibreInfra field note on designing exit across data, configuration, identity, evidence, operations and supplier boundaries.
Identity is the control plane most infrastructure diagrams leave out
A LibreInfra field note on identity as the control plane for human access, workload access, recovery authority and evidence.
Open source does not automatically make infrastructure ownable
A LibreInfra field note on why open-source rights must be connected to reproducibility, recovery, maintenance and transfer.
Owning the account is not the same as owning the infrastructure
A LibreInfra field note on why infrastructure ownership depends on authority, recovery evidence and transferability, not merely accounts or invoices.
