6.9 Resource formats and internal interfaces

These formats support imports and internal communication in the current Alpha. Revalidate them when upgrading; they are not a promise of permanent compatibility for a public API.

Common resource formats

Format	Purpose	What to check
teloa.business-package/v2	Business package manifest	Resource identities, pinned versions, relationships, and scope
teloa.role/v1	Role definition	Duties, data scope, and execution scope
teloa.work-template/v1	Task template	Input requirements, output, and pinned skill references
teloa.mcp-connection/v1	MCP connection declaration	serverName and the tool set
teloa.reference-list/v1	MCP reference list	Sources, byte counts, and SHA-256 versions
teloa.reference/v1	MCP read result	Content and source for the same version

A resource package's scope defaults to domain. Referenced versions must match resource declarations. Do not use JSON field order to determine object equality.

Unknown fields and corrupt data

Many readers enforce strict field validation. Misspelled fields are not silently ignored. Treat invalid input and corrupt stored data separately: correct the input in the first case; preserve evidence and repair from a trusted backup or source in the second.

Internal RPC

The client sends internal RPC requests through the Harness. Endpoints, request envelopes, authentication cookies, and response parsing can change between versions. Requests captured in a browser should not be treated as a stable third-party REST interface.

For system integrations, prefer the supported MCP path. If you need a new stable integration interface, define identity, permissions, idempotency, versioning, and error contracts before implementing the adapter.