#Part 11. Library Catalog And OS Development
#Part 11 Section 1. Core And Data Libraries
The current library tree includes these major groups:
| Group | Libraries |
|---|---|
| Core | CB-Action, CB-Bit, CB-Breakable, CB-Console, CB-Data, CB-Math, CB-Parsing, CB-Time |
| Storage | CB-Storage, CB-FileSystem.Path, CB-FileSystem.Storage, CB-FileSystem.Watch, CB-Database.Local, CB-Cache.Local |
| Formats | CB-Data.CSV, CB-Data.TOML, CB-Data.XML, CB-Data.YAML, CB-Library.Config, CB-Library.Serialization |
| Engineering | CB-Library.Compression, CB-Library.Cryptography, CB-Library.DataStructures, CB-Library.Logging, CB-Library.Testing, CB-Library.Validation |
Read the library source and generated reference before using a function. Library presence does not guarantee that every function is available in every target profile.
#Part 11 Section 2. Graphics, Media, And Simulation
Graphics and media libraries include CB-Render, CB-GPU, CB-Graphics.2D, CB-Graphics.3D, CB-Graphics.Font, CB-Shader, CB-Audio, CB-Multimedia.Audio, CB-Multimedia.Image, CB-Multimedia.Video, CB-Physics, and CB-Pathfinding.
Use the highest-level library that meets the requirement, then drop lower only when measurements justify it. Asset decoding should happen outside the frame loop. Treat shaders and model inputs as untrusted packages: validate sizes, counts, offsets, formats, and memory budgets.
#Part 11 Section 3. Networking And Security
Networking libraries include CB-Network, CB-Networking.HTTP, CB-Networking.API, CB-Networking.DNS, CB-Networking.Socket, and CB-Networking.WebSocket. Security-oriented libraries include CB-Security.Auth, CB-Security.RateLimit, CB-Security.RBAC, and cryptography helpers.
Desktop HTTP helpers may rely on the host TLS stack. A ClosedBitOS kernel needs its own NIC drivers, packet buffers, ARP/NDP, IP, routing, TCP/UDP, DNS, TLS, certificate validation, clock trust, and entropy source before an HTTPS API is real. Do not copy a desktop wrapper into kernel code and describe it as a native network stack.
#Part 11 Section 4. Libraries For Building Operating Systems
OS-oriented libraries should stay small and architecture-aware. Useful packages include fixed-width integer and endian helpers, volatile MMIO access, port I/O where applicable, page-table construction, physical frame allocation, interrupt descriptor construction, lock-free queues, ring buffers, checksums, binary object parsing, filesystem structures, device-tree/ACPI parsing, PCI enumeration, and serial logging.
Each freestanding library must declare:
- supported architectures; - whether allocation is allowed; - interrupt-safety and reentrancy; - alignment and endian requirements; - failure behavior without exceptions; - maximum stack use; - which privileged instructions or firmware tables it needs.
Avoid one giant “OS framework.” ClosedBitOS libraries should be direct, inspectable ClosedBit modules with narrow interfaces.
#Part 11 Section 5. AI And Understanding Libraries
The catalog also contains CB-AI.Heuristics, CB-AI.Pattern, CB-AI.Search, CB-Generation, CB-Generation.Image, CB-Generation.Response, CB-Generation.Text, CB-GenerationOptimized, CB-Understanding, CB-Understanding.Image, CB-Understanding.Language, and CB-Understanding.Logic.
These are application capabilities, not permission to put nondeterministic generation in boot, authentication, storage recovery, or access-control decisions. Security and kernel decisions need deterministic validation and auditable fallback behavior.