Reference library
Definition
The reference library is the lookup layer for object semantics, IDs, permissions, metadata, glossary terms, and source-confidence boundaries. Use it when a workflow depends on exact object meaning rather than the broader operating path.
This page is an index, not a schema contract. Use the stable references below for object meaning; draft schemas and internal implementation details do not become public contracts through this index.
Fields, states, or lifecycle rules
- Object references explain identity, state, lifecycle, and relationship boundaries.
- Permission references explain user-facing access boundaries only where source-backed.
- Metadata and context references explain how records and cases remain reviewable.
- Source-confidence labels tell readers whether a claim is code-backed, doctrine-backed, docs-backed, or inferred.
- Draft schema pages are not public API or export contracts.
Related objects
Use Object model for the main artifact graph, Permissions for access boundaries, IDs and keys for identity references, and Glossary for vocabulary.
Worked example
Reference library boundary
Start
Behavior input
- Question
- A reader asks whether a benchmark run result can be treated as a public export schema.
Result
Interpretation
- Reference answer
- The object references can explain benchmark, run, and result semantics. They do not create a public export contract unless a source-backed public schema page says so.
- Next page
- Use Benchmarks, Run metadata, or Product boundaries, depending on the claim.
Source confidence
Docs-backed: the documentation manifest and taxonomy define the published reference groups and canonical page relationships. Each linked reference carries its own product-evidence boundary; this index does not raise a draft or internal schema to stable contract status.