What belongs in the platform

Use this test before asking xTerminal to grow a new surface. If it fails, it belongs in the site repo or the host, not in the control panel. The product direction is that we are the state intelligence operates on.

The feature test

State

Does it record the current truth of the site in a way people and agents must share? Membership, Request status, lead stage, published content. Yes.

Permission

Does it decide who may do the thing? Owner vs developer vs worker. Yes. A raw cloud console login is not a permission model we should copy into the owner UI.

Change log

Does it leave a history of what shipped or who accepted a preview? Requests, content history, billing events. Yes.

What already passes

• Who is on the site, and their rank.
• Which Request is open, accepted, or live.
• Inbox leads and, when Pipeline is on, grade and value.
• Published blog and other content types you turned on.

What stays in the developer lane

Repo settings, CI, host env, and design code fail the test. Agents may touch those on a branch. Owners should not have to. If a request needs that work, it still runs through the Request loop so the state lives here.

How to use the test

1. Name the job in owner language (who can change this, what is true today, what already shipped).
2. If all three fail, it stays in the developer lane.
3. If it passes, it still needs a person in the loop when an agent does the work.

What this is not

This is not an app store, not a prompt box that emits a new site, and not a host you buy inside the dashboard. See What xTerminal is.