Skip to content

Implement the accepted IFC profile representation and admission #1370

Description

@Brad-Edwards

Align published IFC profiles and their execution support with the accepted expressiveness decision.

Acceptance criteria

  • Implement the selected profile representation, source/sink resolution, profile publication, and capability admission. Add authoring/configuration surfaces only where the accepted decision requires them.
  • Preserve owner-specific distinctions where supported and reject requirements the selected profile cannot represent or realize. Keep confidentiality, integrity, release authority, and provenance separate.
  • Integrate profile obligations and admitted support strength with the revised API-424 contracts; no silent profile substitution or runtime weakening.
  • Update schemas, governed publication records, migrations, and support documentation. Verify the accepted owner-qualified cases and rejection of unsupported distinctions.

Prerequisites: #1354, #1365.

References: Diagnosis.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:runtimeRuntime and control-plane codeenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions