Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.backed.app/llms.txt

Use this file to discover all available pages before exploring further.

​
Runtime and Data

Backed application surfaces resolve environment-specific manifests and read state from the deployed contracts. That means the runtime has two jobs at once: it must point to the correct system, and it must present the resulting data clearly enough that humans can act on it.

​
Runtime model

The runtime is responsible for:
  • selecting the active deployment,
  • resolving contract addresses from that deployment,
  • building read clients,
  • formatting contract outputs for the application and integration surfaces.

​
Data model rule

The runtime can format, cache, and present state. It does not own lifecycle truth.

​
Practical implication

When two sources disagree:
  1. trust the deployed contract reads,
  2. verify the environment,
  3. verify the interface is pointing at the same manifest.

​
Product data versus protocol state

Certain product surfaces may use offchain systems for discovery or catalog behavior. Those systems are useful for product experience, but they are not the authority for approval state, commitment state, or settlement outcomes.