Development reference and live contracts

This reference explains platform boundaries. Available tools, fields and constraints come from the contracts returned by your current authorized connection.

Begin with a task

After connecting an assistant, it uses start_creator_task to obtain current tasks and requirements, then follows the returned specialist Skill and contract references.

tools/list describes tools available to the connection. get_platform_contract_catalog provides the contract slice needed by the selected task. Availability depends on authorization; do not guess operations or substitute internal endpoints.

Core concepts

Concept	Meaning
Product	A stable product identity
Workspace / Build	Current working content and its build and validation result
Runtime Snapshot	Immutable content used for execution
Version	A formal version created through publication
Room / Scenario	Participation space and one running experience

Structure and schemas

The Authoring Contract provides project structure, schemas and the corresponding validator. Obtain them through the task's returned entry and keep contract and Skill identities consistent.

This site does not manually duplicate complete field tables. Generate against the current contract, run its local validator, then submit for platform validation. Server validation remains authoritative.

Ownership boundaries

The platform owns identity, authorization, rooms, versions, commits, storage and recovery. Products own their rules, roles, actions, prompts and presentation. AI output is a candidate result and cannot bypass platform checks.

Interpret older running content using its fixed contract. For new work, read current task requirements instead of guessing from previous conversations.

Markdown for AI readers

Articles are also available through the Markdown index. Use them to understand the product and workflow, while reading live contracts and specialist Skills for execution.