Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#400 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@suuus ci sta già lavorando.

Dal 7/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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.
Lingua principale
JavaScript
Stelle
269
Fork
48
Merge medio
2g 19h
PR unite (30g)
15

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Azure/git-ape

Tutte le issue di Azure/git-ape

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.