Standard Library

The standard library is large, active, and mixed in maturity. A comprehensive page for the stdlib has to explain not only what is present, but also how to distinguish active callable APIs from stub surfaces and disabled inventory.

Current gate-backed snapshot

Surface	Status
Reliability gate	81 pass / 0 fail / 1 skip / 82 total
Inventory	604 .sio files, 111 disabled files, 44 stub module files, 92 active entrypoints
Science pipeline	fmri and darwin_pbpk passing
Hyper execution	7 required lanes passing
Runtime regressions	4 failing probes tracked in soft mode

How to read the stdlib safely

• Treat active_callable modules as real public surface area backed by tests or gates.
• Treat stub_surface modules as shape only: useful for roadmap and compatibility tracking, not for strong API promises.
• Treat *.sio.disabled files as inventory of future work, not as current support.

Where to inspect the truth

• stdlib/ holds the code and module layout.
• tests/stdlib/ holds the most important execution and contract checks.
• artifacts/stdlib/stdlib_reliability_status.v1.json, stdlib_science_pipeline_status.v1.json, and stdlib_hyper_execution_status.v1.json are the canonical machine-readable status artifacts.
• docs/stdlib/STDLIB_REFERENCE.md is the repo-facing reference page for the executable stdlib snapshot.

Reproduce the main stdlib gates

bash scripts/scan_stdlib.sh --json-out artifacts/stdlib/stdlib_inventory.v1.json
bash scripts/stdlib/stdlib_hyper_execution_gate.sh
STDLIB_RUNTIME_REGRESSION_STRICT=1 bash scripts/stdlib_science_pipeline_gate.sh
STDLIB_RUNTIME_REGRESSION_STRICT=1 bash scripts/stdlib_reliability_gate.sh

Practical guidance

• When writing docs or examples, start from active tests instead of from directory names.
• If a module is present but its best current test is only an import or shape check, describe it as a limited or stub surface.
• Use the status artifacts when you need exact counts or lane-level claims.