Choose your CALIBER path

This page exists so a reader can choose the right documentation path first, before dropping into deep reference or architecture pages.

At a glance#

1. If you are integrating with CALIBER#

Start with the Python SDK unless you have a concrete reason to work at the raw HTTP layer.

Use the REST API directly when:

• you are not integrating from Python
• you need to compare wire behavior against the SDK
• you are working with an endpoint before a typed SDK method exists

Recommended path:

1. SDK guide
2. Auth and project scoping
3. SDK vs REST API
4. Error handling and retries
5. SDK API reference

2. If you are operating a deployment#

Start from bring-up and readiness, not from architecture.

Recommended path:

1. Local bring-up guide
2. Configuration and provider setup
3. Health and readiness
4. Operator troubleshooting
5. Operations runbook

3. If you are evaluating trust, governance, or release posture#

Start from the trust surfaces that connect evidence, review, and apply.

Recommended path:

1. Trust and governance guide
2. Evaluation and test sets
3. Calibration
4. Review and release flows

4. If you need system architecture#

Start from the layered model, then read only the deep subsystem pages that matter for the question you are answering.

Recommended path:

1. Architecture reader guide
2. Layered architecture
3. Platform
4. the subsystem pages that matter for your topic

5. If you are deciding whether CALIBER fits#

Start from the platform shape and the market position, not the route modules.

Recommended path:

1. Decision-maker overview
2. Competitive analysis
3. Roadmap