Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat: Native Intent → Execution → Evidence foundation with optional ISEE governance

Open
  • Is something wrong?
#400 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 2 days

@suuus is already working on this.

Since Oct 7, 2026.

  • #405 by @suuus — open

Assessment

This issue has not been assessed yet.

Description

AI-evals documentation feature

Summary

Establish a portable governance foundation for Git-Ape that records deployment
Intent, captures what actually executed, and preserves immutable Evidence without
requiring the ISEE suite to be installed.

ISEE remains an optional governance and independent-verification layer that can
be installed before or after Git-Ape records are created.

Motivation

Git-Ape already performs security, cost, architecture, approval, deployment, and
validation stages. However, these stages need portable, machine-readable records
that preserve:

  • what was intended;
  • which execution path actually occurred;
  • which artifacts and control results were produced;
  • who or what authorized the deployment;
  • whether records were independently governed or verified.

These records should remain useful without introducing a mandatory runtime or
package dependency.

Scope

  • Save onboarding and deployment Intent as ADRP-compatible draft records.
  • Declare versioned deployment execution graphs.
  • Capture immutable, graph-bound execution traces.
  • Derive CI traces from actual workflow step outcomes.
  • Label interactive traces as agent-observed.
  • Emit immutable AERP-compatible Evidence bundles for successful and failed runs.
  • Bind Evidence to exact artifact bytes and archived graph versions.
  • Support delayed adoption by ADRP, ASRP, and AERP tooling.
  • Preserve truthful lifecycle states:
    • native Intent is draft;
    • native Evidence is generated;
    • only authoritative tooling may ratify or independently verify records.
  • Retain Git-Ape's existing Bash, jq, and SHA-256 dependency baseline.

Relationship to #148

#148 delivers the structured execution-trace portion of this foundation.

The trace implementation deliberately uses workflow-owned reconstruction in CI
rather than requiring agents to self-report their own completeness. Interactive
agent observations remain supported, but are explicitly identified as
agent-observed and are not represented as independent proof.

The Intent, trace, Evidence, and optional ISEE integration are tightly connected
and may be delivered through one implementation PR referencing both issues.

Acceptance criteria

  • Onboarding preserves platform Intent as an ADRP-compatible draft.
  • Each deployment preserves deployment-specific Intent before execution.
  • Each workflow attempt receives an immutable invocation identity.
  • The exact execution graph used by each attempt is archived.
  • Traces are bound to the archived graph digest.
  • Trace validation checks nodes, transitions, receipts, ordering, continuity,
    required successful nodes, and terminal outcomes.
  • Failed attempts can produce valid traces ending at the failed node.
  • Evidence bundles include trace, validation, graph, state, test, and relevant
    deployment artifacts.
  • Evidence is emitted for successful and failed attempts.
  • Optional ISEE adoption validates existing records without regenerating or
    automatically ratifying them.
  • Record or Evidence failures do not rewrite Azure deployment lifecycle state.
  • Native operation introduces no runtime dependency beyond existing Bash/jq
    tooling.
  • Scaffolding, tests, evaluations, and user documentation cover the lifecycle.
Dominant language
JavaScript
Stars
269
Forks
48
Avg merge
3d 32m
Merged PRs (30d)
14

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/git-ape

All issues in Azure/git-ape

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.