//APPS AND SURFACES
A focused job on top of the same core.
Apps shape the user task. Access keeps their operations within shared Core controls. The two native examples below are development evidence, not a public App catalogue.
01APP CONTRACT
The surface can shape the task. It cannot create new authority.
An App binds exact Core operations and an immutable presentation asset. It can collect inputs and display a result. Approval, adoption and delivery remain separate governed commands with their own permissions.
02DEVELOPMENT EXAMPLE 01
Text Studio
A native copy form on the product feature branch collects Brand, Authority manifest, Prompt, Rules, Target and Task. It submits a produce-copy operation through Access and displays the returned proposed copy when eligible. It has no approval or delivery control.
Built on a product feature branch. Integration to main and deployment are not established.
Proposed copy is shown only when eligible. Approval and delivery remain separate.
03DEVELOPMENT EXAMPLE 02
Core Admin
A native read and inspection surface lists Apps and versions through Access. It supports inspection, not management mutation. Its current evidence is feature-branch implementation and tests.
Built on product development branches. Production availability is not established.
04SURFACE BOUNDARY
One operation contract across admitted surfaces.
Native Apps, other UIs, API or agent adapters may enter through Access under the architecture. General surface equivalence and an external App catalogue are not established by the current proof.