Skip to content

Align runtime/content orchestration work by composing existing contract families #51

@mdheller

Description

@mdheller

Recent architecture work around deployment envelopes, content-addressed curation, execution posture, and phase-relative orchestration overlaps with contract families already present here.

We should review the recent model using composition from existing types before adding any new top-level schema.

Review target:

  • WorkloadSpec
  • DataSphere
  • ExecutionSurface
  • ExecutionDecision
  • RunRecord
  • ContentRef
  • control-plane isolation/release profile wrappers where relevant

Acceptance criteria:

  • add a short note or ADR describing how the recent runtime/content placement model maps onto existing schema families
  • identify any true schema gaps
  • if a new schema is needed, keep it additive and reference existing types rather than re-declaring them
  • keep vendor-specific orchestrator names out of canonical schema identity unless strictly necessary

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions