ManagedModelSourceFile · types

The following types define named objects and their relationships. Tables include inherited properties. Schema-derived types refer to their validated structures; a TypeScript declaration does not replace the compiler’s semantic checks.

ManagedModelSourceFile

Exact authored file bytes captured by a source owner, never a path the compiler may read.

Field	Options / expected values	Description
path	string	Required. Defines path for this object. Observe the type, variants and bounds in the Options column.
content	string	Required. Native content matching the selected type and profile; not a UI composition.

export interface ManagedModelSourceFile {
  readonly path: string;
  readonly content: string;
}

All references

Applied examples : Publish a reusable app

Publication describes the app; policies preserve access to instance Actions.

Configuration

Fragment placed in publication. Properties and accepted values.

{
  "kind": "workspace-application",
  "license": "Proprietary",
  "requiredCapabilities": [],
  "requiredConnections": []
}

Variation and connection

Fragment placed in contentActions[]. Properties and accepted values.

{
  "contract": "ContentSpaceActionPolicy@1",
  "spaceKey": "clients",
  "actionKey": "prepare-quote",
  "minimumRole": "editor"
}

UI layout example

The illustrative layout below places this configuration in the Clients/Quotes app. Insert each fragment at the stated location, with Field, Query and Action references matching the Model declarations.

1. Target object
2. Proposed change
3. Checks
4. Confirm

SurfaceClients / North StudioExample

ManagedModelSourceFile · typesPublish a reusable app

Clients

NS

North StudioQuote S-1042

Needs review

Proposed change

Publication describes the app; policies preserve access to instance Actions.

Data and references

Client · Need · Pricing

BackReview then confirm