---
id: reference.index
title: Reference library
summary: Look up Teammately objects, states, permissions, metadata, schemas, and source-confidence boundaries.
kind: reference
product_area: reference
status: stable
updated: 2026-09-07
canonical: /docs/reference
---

# 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](/docs/object-model) for the main artifact graph, [Permissions](/docs/reference/permissions) for access boundaries, [IDs and keys](/docs/reference/ids) for identity references, and [Glossary](/docs/reference/glossary) for vocabulary.

{% example-demo title="Reference library boundary" %}
Question: A reader asks whether a benchmark run result can be treated as a public export schema.

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](/docs/object-model/benchmarks), [Run metadata](/docs/benchmark-evaluations/run-metadata), or [Product boundaries](/docs/introduction/product-boundaries), depending on the claim.
{% /example-demo %}

## 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.

## Related task pages

{% related-card-grid title="Related task pages" %}
- [Object model](/docs/object-model)
- [Permissions](/docs/reference/permissions)
- [Glossary](/docs/reference/glossary)
- [Product quickstart](/docs/quickstart)
- [Task index](/docs/operating-manual/task-index)
{% /related-card-grid %}