Skip to content

P1: Prove Kertas client conformance against an independent runtime #53

Description

@wms2537

Parent

Dependencies

Scope

Prove a Kertas-shaped integration against an independently deployed runtime using only the published HTTP contract and immutable artifact/snapshot references.

Required behavior

  • The client discovers versions before use and never imports runtime stores, migrations, or internal domain modules.
  • It creates/resumes a ManagedSession, delivers a future event, observes ordered resource events, and reads Runs/artifacts/child-result projections through public APIs.
  • Runtime completion is reported only as execution disposition; the client owns its separate outcome/release decision.
  • The deployed test uses authenticated tenant isolation and a non-loopback endpoint.
  • The receipt records exact server/client commits, image digest, contract versions, and cleanup.

Public seams under test

  • independently deployed authenticated HTTP API
  • published machine-readable schemas and standalone client
  • content-addressed artifact/snapshot handoff

Acceptance criteria

  • one complete Kertas integration uses only the public contract
  • a forbidden-import check prevents runtime-internal coupling
  • current and target compatibility modes are exercised according to policy
  • retained exact-commit deployment evidence is redacted and digest-bound
  • independent review and post-merge main evidence pass

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

    enhancementNew feature or requestready-for-agentScoped, dependency-declared work ready for an implementation agent

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions