Skip to content

Define portable core contracts #155

Description

@yihanzhu

Problem

The accepted portable-control-plane-core umbrella was too broad for one G2 spec. Core record definitions, deterministic profile resolution, and executable adapter contract tests need separate artifact chains.

Outcome

Create the record/validation child only:

  • versioned portable stage, artifact, evidence, risk, qualification, manifest, profile, capability, permission, actor, environment, and execution-metadata records;
  • closed capability argument schemas;
  • pure shape and relational validation with offline positive and adversarial tests;
  • exact safety boundaries between producer, verifier, reviewer, publisher, and human decisions;
  • stable references consumed later by profile resolution and executable adapter tests.

Constraints

  • Parent intent: portable-control-plane-core, blob bd6f37e60aa12378aa00d0ff57aebd36b93c4a32.
  • No Git profile resolver, executable adapter runner, 2×2 matrix, real adapter, profile activation, migration, or autonomous write.
  • The old parent slug does not proceed to another spec or implementation.
  • Merging the intent PR is G1 acceptance into design, not implementation approval.

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions