Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#400 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

@suuus がすでに取り組んでいます。

2026年10月7日 から。

評価

この issue はまだ評価されていません。

説明

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.
主要言語
JavaScript
スター
269
フォーク
48
平均マージ
2日 19時間
マージ済み PR（30日）
15

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Azure/git-ape のほかの issue

Azure/git-ape の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。