Skip to content

Feature: Add generation-provenance provider artifact kind #155

Closed
#156
Closed
Feature: Add generation-provenance provider artifact kind#155
#156
Labels
domain: backendCompiler/backend implementation workrelease:lawpacksLawpack contract and authority source release workrelease:target-profilesTarget-profile contract and authority source release workstate: activeCurrently being implemented or reviewedtype: featureFeature issue for a cohesive capability
Milestone
Provider Artifact Pipeline Alpha

Description

@flyingrobots
flyingrobots
opened on Jul 13, 2026

Purpose

Represent a provider generator's deterministic build-provenance document honestly in edict.provider-manifest/v1. Echo issue #651 needs to freeze this output, and Echo issue #655 needs to package it without misclassifying it as a review artifact or runtime semantic artifact.

Scope

  • Add the generic generationProvenance provider artifact kind.
  • Classify it as generated-source metadata.
  • Accept a digest-locked generationProvenance entry during provider-manifest validation.
  • Reject component provenance for that kind with the existing stable generated-role failure.
  • Update the representative provider fixture and durable provider contract documentation.

Acceptance criteria

  • ProviderArtifactKind round-trips generationProvenance through the manifest JSON contract.
  • A generated, digest-locked generation-provenance entry validates.
  • The same kind with component provenance rejects as GeneratedRoleRequiresGeneratedSource.
  • Existing provider validation behavior remains unchanged for all other artifact kinds.
  • Provider topic requirements, test plan, and design reference describe the new generic category.

Boundaries

This issue adds routing and provenance-envelope vocabulary only. It does not define an Echo-specific provenance schema, interpret generator evidence, load provider packages, change component execution, or add runtime authority.

Parent goalpost: #138
Downstream: flyingrobots/echo#651, flyingrobots/echo#655

Activity

  1. flyingrobots
    added this to the Provider Artifact Pipeline Alpha milestone on Jul 13, 2026
  2. flyingrobots
    added
    release:lawpacksLawpack contract and authority source release work
    release:target-profilesTarget-profile contract and authority source release work
    type: featureFeature issue for a cohesive capability
    state: activeCurrently being implemented or reviewed
    domain: backendCompiler/backend implementation work
    on Jul 13, 2026

  3. coderabbitai commented on Jul 13, 2026

    @coderabbitai
    coderabbitaibot
    on Jul 13, 2026 – with coderabbitai
    🔗 Related PRs

    #2 - docs: apply Phase 0 design review + nail five yellow-light joints [merged]
    #108 - Freeze canonical Target IR artifacts [merged]
    #128 - Parse obstruction strand continuations [merged]
    #132 - Lower obstruction requirements to Echo Target IR [merged]
    #144 - Add built-in lowerer compatibility seam [merged]

    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan
    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
  auto_enrich:
    enabled: false

    💬 Have feedback or questions? Drop into our discord!

  4. flyingrobots
    closed this as completedin #156on Jul 13, 2026
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

    domain: backendCompiler/backend implementation workrelease:lawpacksLawpack contract and authority source release workrelease:target-profilesTarget-profile contract and authority source release workstate: activeCurrently being implemented or reviewedtype: featureFeature issue for a cohesive capability

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions