Citizen-facing services · Learning and knowledge

PBB Library / Libria

Governed reference releases from Library Cloud with local offline search, reading, citations, and resource delivery.

Integrated · Production hardening Baseline node service

Primary placement: Library or knowledge node; School or learning node
Primary users: Citizens and families, Students and teachers, Health and response workers, Library content administrators, PBB Learning

What it is

A practical part of one local platform

PBB Library / Libria combines a governed Library Cloud control plane with a local Library Node. Cloud handles source review, ingestion, normalization, licensing, release construction, signing, node assignment, and fleet reports.

The local node verifies and activates approved releases, then serves public catalog, search, collections, resources, citations, content, and approved SDK or embed access without requiring Cloud for routine reading. Large releases use Library-specific transfer paths rather than Relay messages.

Problem it solves

The operational gap

Communities need dependable access to governed reference material without depending on continuous internet access or transferring multi-gigabyte content through emergency messaging infrastructure.

Core workflow

How Libria supports local work

Review and govern sources
Library Cloud ingests approved sources and records provenance, licensing, normalization, review, and content decisions.
Build a signed release
Cloud constructs a release with manifests, objects, signatures, node assignment, and controlled offers.
Verify and activate locally
Library Node downloads or imports approved objects, verifies trust, stages content, and atomically activates the release.
Search and read offline
Local users browse, search, view resources, and use citations or collections from the active node release.

Who uses it

Designed around local service roles

Citizens and families
Students and teachers
Health and response workers
Library content administrators
PBB Learning

Offline-first behavior

What continues locally—and what does not

Works on the local node

The active local catalog, search index, collections, resource payloads, citations, and content remain available after commissioning.
Public reading should not require mandatory login, Cloud, Realtime, or Learning availability.

Required local services

Libria requires its local Laravel Node, MySQL catalog, content volumes, object storage, and verified active release.
Administration can use Account hooks, but public reading remains a separate local boundary.

When a route returns

The node can check Library Cloud for governed offers, download release objects, and report deployment or inventory state.
New releases use authenticated Library-specific object and reporting APIs.

Connectivity-dependent

New Cloud ingestion, review, release construction, and remote offers require a route to Library Cloud.
External source acquisition and new large-object downloads require their configured transfer path.

Not currently synchronized

Routine large Library releases do not travel as PBB Relay messages.
Raw citizen search queries should not be uploaded to Cloud without an approved privacy and consent model.

Deployment placement

Where it fits

Special deployment

Library or knowledge node; School or learning node

Hardware, connectivity, power, training, travel, and field logistics remain deployment-specific.

Practical questions

Frequently asked questions

Can people search and read when the internet is down?

Yes. Once an approved collection has been installed and activated on the local Library Node, people can search and open those local resources without internet access.

Is an Account login required to read public resources?

No. People should be able to read public resources without signing in. An account is mainly needed for administration and optional personal features.

Are large Library packages sent through PBB Relay?

No. Large Library collections use their own download or physical-import process, along with records that report what was deployed.

How does a node know a release is approved?

A node checks information and digital signatures included with the collection before making it available. It also supports withdrawing a release or returning to an earlier approved version.

Is Libria an LMS for PBB Learning?

No. Libria is a source of local references and learning materials. Lumaria may connect to it for search, citations, collections, and related resources.

Is field release installation fully operationalized?

Not yet. Installation, preparing large collections, checking storage, transferring files, returning to an earlier version, and recovery procedures still need more testing and documentation.

Status and readiness

Integrated

Library Cloud and Library Node are implemented with governance, signed release, local catalog, public resource, storage, trust, rollback, SDK, and Account hooks.

Remaining hardening work

Publish field transfer, signing, verification, rollback, and recovery runbooks.
Complete Kit Setup packaging, Data Prep, storage commissioning, and smoke checks.
Verify the minimum Learning-to-Library adapter and citizen search privacy policy.

Connected platform

Local-node foundation

Briefing and pilot discussion

Discuss Libria in a local PBB deployment

Explore how a local-node deployment could support practical service continuity in your community.

Request a briefing