Token And Render Boundaries

Creative and design surfaces are current in MyronCMS, but they are not general extension v1 hooks. This page separates the advanced current Creative/JSONM capabilities from prohibited extension behaviors.

The short rule:

Extensions can add supported extension surfaces.
Extensions cannot add design token groups or hook public rendering in extension v1.

Human Path

Before building an extension that touches design or rendering, classify the request.

Request	Current status	Safe path
Add a namespaced action under `/api/v1/x/{vendor}/...`	Stable current	Use extension action docs.
Add an isolated admin route	Stable current	Use admin route docs.
Add isolated `{vendor}_*` migrations	Stable current	Use migration docs.
Register a MIC resolver	Stable current	Use content capability docs.
Register a mail transport	Stable current	Use integration docs.
Author a creative component in local source	Advanced current local authoring	Use the Creative Component SDK.
Read creative authoring guidance through MCP	Advanced current	Read `mcp://creative-component-sdk`.
Export/import JSONM design systems	Advanced current	Use JSONM interchange and scoped design actions.
Register new design token groups from an extension	Prohibited current	Requires a future platform contract.
Hook or override public rendering from an extension	Prohibited current	Requires a future platform contract.
Contribute snapshot sections from an extension	Prohibited current	Requires a future platform contract.
Inject into core admin rail sections	Prohibited current	Use isolated extension admin routes only.

AI Path

An AI coding agent can help classify the idea, author supported local extension files, or author contracted Creative/JSONM documentation.

An installed MCP client can read current MCP resources and call scoped design actions when granted. It cannot install PHP code, register a new token group, hook public rendering, or bypass the extension loader.

If a user asks an AI agent to add an extension render hook or token group registration path, the correct response is to stop at classification and route the platform expansion through Evaluate and Contract.

Scopes

This boundary page has no runtime action scope.

Adjacent current capabilities have their own gates:

Capability	Gate
Read `mcp://creative-component-sdk`	MCP resource read; no action scope in current resource list.
Read `mcp://myroncms/design/jsonm-interchange`	MCP resource read; no action scope in current resource list.
Export current JSONM	`design.read`
Import JSONM	`design.write`
Loaded extension actions	Action metadata scope and extension grants.

Artifacts

Supported extension v1 artifacts include:

app/extensions/{vendor}/manifest.json
app/extensions/{vendor}/bootstrap.php
extension actions/
extension admin/routes/
extension migrations/
extension MIC resolvers
extension mail transports

Current creative/design artifacts live in platform-controlled or local-authoring surfaces:

mcp://creative-component-sdk
mcp://myroncms/design/jsonm-interchange
app/jsonm/schema/style-definition.schema.json
app/jsonm/maps/token-map.json
app/data/runtime-definitions/components/components-atoms-v0.2.0.json
app/modules/content/public/DefinitionTemplateRenderer.php
app/assets/runtime/css/components.css
app/assets/runtime/js/creative-runtime.js

Safety Boundary

Do not document extension examples with a designTokens, renderHooks, publicRender, snapshotSections, or similar bootstrap.php key. The loader does not define those extension payloads.

Do not tell extension authors to mutate the JSONM token map, component registry, renderer, or runtime CSS as an extension install side effect. Those are platform/source surfaces, not extension v1 hooks.

Do not confuse scoped custom CSS with a public render hook. Custom CSS is an operator customization layer; it does not let an extension intercept or replace the renderer.

Verification

For documentation review:

rg -n "design token group|public render hook|snapshot sections|core admin rail" app/extensions/README.md docs/extensions-sdk

Confirm:

app/extensions/README.md still says extensions cannot add design token groups or hook public rendering,
this page uses support_status: "prohibited-current",
examples stop at classification and do not provide runnable unsupported hooks,
adjacent Creative and JSONM pages are linked as separate current design workflows.

Failure Modes

Failure	What it means	Safe response
Docs show extension token group registration	Unsupported extension surface was invented.	Remove the example and return to Evaluate if the platform should grow.
Docs show a public render hook in `bootstrap.php`	Loader contract was overstated.	Remove the hook and document current prohibited status.
Creative SDK is described as an extension install mechanism	MCP resource/local authoring was confused with extension runtime.	Reword to separate Creative Component SDK authoring from extension v1.
JSONM import is described as extension token registration	Design-system interchange was confused with extension API.	Reword around JSONM design-system import/export and scopes.
Custom CSS is treated as token catalog expansion	Operator escape valve was confused with substrate mutation.	Keep custom CSS scoped and outside token-map/catalog claims.