Canvas Reference Overview
Canvas is the admin-only, versioned authoring surface for a Space. This section documents its snapshot format, its operations, and its access rules.
Canvas is available only to Space admins, and only in Spaces where Ligantic has enabled it. Elsewhere, Canvas pages and operations return a 404, and Canvas does not appear to exist.
Scope
This section covers:
- The Canvas resource, its lifecycle states, and its version history
- The canonical Canvas snapshot format, including node kinds and backing references
- Ingestion of uploaded files into artifacts
- Tabular preview, table extraction, and Schema literal derivation
- The candidate review and provenance model
- Conversion of literal nodes into first-class Schemas, Experiences, and Flows
- Flow literal runs and run compatibility
- Enablement, authorisation, and route access
- Space export and import of Canvas data
Entry Points
- Canvas Access
- Canvas Lifecycle and Versions
- Canvas Snapshot Format
- Canvas Ingestion
- Canvas Tabular Preview and Extraction
- Canvas Review and Provenance
- Canvas Conversion
- Canvas Flow Literal Runs
- Canvas Space Transfer
- Canvas Editor Actions
Object Model
Object | Description |
|---|---|
Canvas | Named, Space-scoped authoring surface with a current version |
Canvas version | Immutable snapshot with a parent version and a change summary |
Canvas audit record | Lifecycle change record, kept outside version history |
Candidate | Generated or derived content attached to a Canvas node |
Candidate decision | Immutable accept, reject, or supersede record |
Provenance record | Link from a source artifact to a derived artifact |
Conversion record | Record that a literal node became a resource |
Artifact | Immutable stored content that Canvas nodes refer to |
Limitations
- Candidates cannot be reviewed, edited, or re-run in Studio or through the API. Table extraction and Schema derivation accept their output automatically.
- Convert to resource is not offered for
flow:literalnodes. See Canvas Conversion. - Canvas does not create
flow:literalnodes. See Canvas Flow Literal Runs. - Stored content is not metered, billed, or quota-limited.