Reference

Use the reference section when you need to understand the current public model of the core runtime.

This section is where the docs answer questions like:

• what do strategy, channel, execution, session, and message actually mean?
• how does a request move through the runtime?
• what packaged actions exist in core?
• how do security, approvals, and trust layers work?
• which REST surfaces exist and when should each one be used?

Concepts Contracts Control Surfaces

Start In This Order

If you are reading from scratch, use this progression:

1. Read Runtime Model to learn the vocabulary and record boundaries.
2. Read Architecture to understand how requests are routed, executed, and recorded.
3. Read Standard Actions, Security, and API Reference when you need specific operational detail.

Public scope

The reference pages are intentionally core-focused. They describe the current public-safe runtime in force-app, not internal addon implementation details.

Read Runtime Model Read Architecture Review Security Model

Reference Map

Runtime Model

Architecture

Standard Actions

Security

API Reference

When To Leave Reference

If you are trying to deploy, configure, or extend the framework rather than look something up, the Guides section will usually get you to a working outcome faster.