Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#400 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 2 días

@suuus ya está trabajando en esto.

Desde el 7/10/2026.

  • #405 de @suuus — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.
Lenguaje dominante
JavaScript
Estrellas
269
Forks
48
Merge medio
2 d 19 h
PR fusionados (30 d)
15

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/git-ape

Todos los issues de Azure/git-ape

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.