Design Doc: Schemas, Protocols & Intents w/Delegations

[JoeCap08055]

Description

In the current implementation, schemas are registered with immutable numeric identifiers (SchemaId) and describe the layout and storage semantics (e.g., Avro/Parquet formats, on-chain/off-chain storage). These schema IDs are used as references by clients and runtime modules alike, particularly in the delegation system defined by the msa pallet.

Delegations currently allow a user to authorize a provider (e.g., an app or service) to act on their behalf, but this authorization is tightly bound to a specific SchemaId. This model has proven limiting in several ways:

• Coupling between schema versions and delegations
• Schemas represent data format, not purpose
• Lack of human-readable context
• Rigid governance workflows
• No concept of publisher authority

These limitations have motivated a re-architecture of the schema and delegation systems to introduce the concepts of:

• Named schema protocols with version tracking
• Structured publishing under namespaces
• Intent-based delegation
• More expressive APIs and storage models

Closes #2265