Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

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

Đang mở
  • Có gì không ổn?
#400 0 bình luận 0 reaction 1 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 2 ngày

@suuus đang làm issue này rồi.

Từ ngày 7/10/2026.

Đánh giá

Issue này chưa được đánh giá.

Mô tả

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.
Ngôn ngữ chính
JavaScript
Star
269
Fork
48
Merge trung bình
2 ngày 19 giờ
Pull request đã merge (30 ngày)
15

Chuẩn bị môi trường

Mở trong Codespaces

Khởi chạy dev container của dự án ngay trên trình duyệt, bằng tài khoản GitHub của bạn.

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của Azure/git-ape

Tất cả issue của Azure/git-ape

Issue tương tự

Thêm issue về JavaScript

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.