| docRole | lastVerified |
|---|---|
narrative |
2026-03-09 |
🌍 Language / 言語: English | 日本語 | Documentation / ドキュメント
ae-framework is an assurance control plane for agent-driven SDLC. It standardises specifications, verification, evidence, and CI/policy automation so human/agent collaboration stays auditable and repeatable even when the underlying coding agent changes.
flowchart TB
subgraph H[Harness layer]
H1[lint / test / hooks]
H2[E2E / adapters / runners]
end
subgraph C[Assurance control plane]
C1[Context Pack / evidence aggregation]
C2[policy gate / review / release judgment]
end
H --> C
- Baseline stabilises the harness layer with
first-run/verify:lite. - Structured assurance connects Context Pack, property/MBT/conformance, and change evidence into the control plane.
- High-assurance critical core strengthens the control plane for selected high-risk changes with formal/model/proof lanes.
- Assurance control plane: Context Pack, formal/conformance summaries, artifact validation, policy gates, and PR/release automation that turn raw test runs into reviewable assurance evidence.
- Agentic SDLC orchestrator: Ready-to-run GitHub Actions (PR verify / verify-lite, nightly heavy tests, Slack alerts) and CLI scripts that keep requirements, tests, and regression signals aligned.
- Spec & Verification Kit: Traceable spec format, mutation/MBT/property verification pipelines, and formal runners for Alloy/TLA/SMT/Apalache/Kani/SPIN/CSP(cspx)/Lean4 with unified summaries.
- Project scaffolding & policies: pnpm workspace layout, lint/test/type-coverage gates, label gating (typecov, flake), and TDD-friendly Git hooks.
- Cacheable heavy test artifacts:
scripts/pipelines/sync-test-results.mjsto restore/store/snapshot mutation + MBT results;heavy-test-trendsartifacts for CI triage. - Agent integrations: Playbooks and connectors for Claude Code / CodeX; JSON-first outputs and AJV validation to keep agent-produced artifacts safe.
- Not a single-model code generator — code generation is one producer, not the system of record.
- Not an agent runtime or IDE plugin — bring your own agent.
- Not a general-purpose Next.js UI kit or design system starter.
- Not a hosted CI/CD service — workflows are provided for self-hosted GitHub runners or forks.
- Baseline:
verify:lite, schema/AJV validation, PR gates for routine application delivery. - Structured assurance: Context Pack, property/MBT/conformance, richer traceability and change evidence.
- High-assurance critical core: formal/model/proof lanes plus proof-carrying change packages for selected high-risk components.
# Prereqs: Node.js 20.11+ (<23), pnpm 10
corepack enable
corepack prepare pnpm@10.0.0 --activate
pnpm install
pnpm run first-run
pnpm run setup-hooks
# Fast feedback
pnpm run lint
pnpm run test:fast
# Mutation quick run (mktemp-based; supports STRYKER_TEMP_DIR)
STRYKER_TIME_LIMIT=0 pnpm run pipelines:mutation:quick
# If report generation is intentionally optional, set MUTATION_REPORT_STRICT=0
# Formal smoke (non-blocking summary; cspx backend preferred)
pnpm run verify:formal
pnpm run verify:csp -- --file spec/csp/cspx-smoke.cspm --mode typecheck
# Heavy test cache & trend snapshot
node scripts/pipelines/sync-test-results.mjs --store
node scripts/pipelines/sync-test-results.mjs --snapshot
node scripts/pipelines/compare-test-trends.mjs --json-output reports/heavy-test-trends.json
npm installis intentionally blocked bypreinstallbecause this repository usespnpmworkspace dependencies (workspace:*).pnpm run doctor:envwritesartifacts/doctor/env.jsonand returns0(ok) /2(warning) /1(error) /3(invalid arguments).pnpm run first-runrunsdoctor:env -> build -> verify:liteand writes summary JSON/Markdown files under theartifacts/first-rundirectory.
- Overview & nav:
docs/README.md,docs/project-organization.md - Maintenance operations:
docs/maintenance/branch-cleanup-runbook.md - Worktree maintenance operations:
docs/maintenance/worktree-cleanup-runbook.md - TODO triage operations:
docs/maintenance/todo-triage-runbook.md - Current architecture snapshot:
docs/architecture/CURRENT-SYSTEM-OVERVIEW.md - Zero-based ideal redesign blueprint:
docs/architecture/ZERO-BASED-IDEAL-DESIGN.md - Product fit (what to input/output, which tools to use):
docs/product/PRODUCT-FIT-INPUT-OUTPUT-TOOL-MAP.md - Assurance control plane positioning:
docs/product/ASSURANCE-CONTROL-PLANE.md - Assurance model (claim / level / lane / evidence):
docs/quality/ASSURANCE-MODEL.md - Assurance operations runbook:
docs/quality/assurance-operations-runbook.md - Assurance onboarding checklist:
docs/guides/assurance-onboarding-checklist.md - PR automation (Copilot -> auto-fix -> auto-merge):
docs/ci/pr-automation.md - Release engineering (release verify / post-deploy):
docs/operate/release-engineering.md - CI/quality gates:
docs/ci/phase2-ci-hardening-outline.md,docs/ci/label-gating.md,docs/ci/harness-taxonomy.md - Development deep dives: Enhanced State Manager, Circuit Breaker
- Docs consistency lint:
pnpm run check:doc-consistency(docs/quality/doc-consistency-lint.md) - Heavy test observability:
docs/ci/heavy-test-trend-archive.md,docs/ci/heavy-test-alerts.md,docs/ci/heavy-test-album.md - Specification & verification:
docs/quality/,docs/quality/formal-csp.md,docs/ci-policy.md,docs/testing/integration-runtime-helpers.md - Context Pack v1 (spec contract):
docs/spec/context-pack.md - Context Pack onboarding checklist:
docs/guides/context-pack-onboarding-checklist.md - Context Pack Phase5+ cookbook:
docs/guides/context-pack-phase5-cookbook.md - Context Pack troubleshooting runbook:
docs/operations/context-pack-troubleshooting.md - Contract catalog (input/decision/evidence/operation):
docs/reference/CONTRACT-CATALOG.md - Spec & Verification Kit (minimal activation guide):
docs/reference/SPEC-VERIFICATION-KIT-MIN.md - Connectors & agent workflows:
docs/integrations/CLAUDE-CODE-TASK-TOOL-INTEGRATION.md,docs/integrations/CODEX-INTEGRATION.md - License scope and notice management:
LICENSE,LICENSE-SCOPE.md,TRADEMARKS.md,THIRD_PARTY_NOTICES.md
ae-framework は エージェント協調型開発の assurance control plane です。基礎となる coding agent やモデルが変わっても、仕様・検証・証跡・policy gate を同じ契約で束ね、レビューと運用判断を再現可能にします。
flowchart TB
subgraph H[Harness layer]
H1[lint / test / hooks]
H2[E2E / adapters / runners]
end
subgraph C[Assurance control plane]
C1[Context Pack / evidence aggregation]
C2[policy gate / review / release judgment]
end
H --> C
- Baseline は
first-run/verify:liteで harness layer を安定化させる段階です。 - Structured assurance は Context Pack、property/MBT/conformance、change artifact を control plane に接続する段階です。
- High-assurance critical core は selected high-risk change に対して control plane を強化する段階です。
- Assurance control plane: Context Pack、形式検証/Conformance要約、artifact validation、policy gate、PR/release 自動化を束ね、単発のテスト実行結果を判断可能な証跡へ変換。
- SDLCオーケストレーター: PR Verify/夜間ヘビーテスト/Slack通知などのGitHub ActionsとCLIスクリプトで、要件・テスト・退行検知を一元化。
- 仕様・検証キット: トレーサブルな仕様フォーマット、mutation/MBT/Propertyテストのパイプライン、
scripts/pipelines/compare-test-trends.mjsによるトレンド比較。 - プロジェクト骨子とポリシー: pnpmワークスペース、Lint/Test/型カバレッジのゲート、ラベルゲーティング(typecov・flake)、TDDフック。
- ヘビーテスト成果物のキャッシュ:
scripts/pipelines/sync-test-results.mjsによる store/restore/snapshot、heavy-test-trendsアーティファクトでCIトリアージを高速化。 - エージェント統合指針: Claude Code / CodeX 向けプレイブック、JSON成果物のAJV検証など、エージェント生成物を安全に扱うための手順。
- 単一モデル依存のコード生成専用ツール。codegen は producer の一つであり、SSOT は spec / contract / artifact に置く。
- エージェント実行ランタイムやIDEプラグイン(各自のエージェントを利用)。
- 汎用のNext.js UIスターターやデザインシステム配布物。
- ホスト型CI/CDサービス(GitHub Actionsの定義を提供)。
- Baseline:
verify:lite、schema/AJV、PRゲートで通常の業務アプリを安定化。 - Structured assurance: Context Pack、property/MBT/conformance、change evidence を追加し、仕様と検証の対応を明示。
- High-assurance critical core: 重要コンポーネントに対して formal/model/proof lane と proof-carrying change package を適用。
# 前提: Node.js 20.11+ (<23), pnpm 10
corepack enable
corepack prepare pnpm@10.0.0 --activate
pnpm install
pnpm run first-run
pnpm run setup-hooks
pnpm run lint
pnpm run test:fast
# Mutation quick(mktemp利用、STRYKER_TEMP_DIR対応)
STRYKER_TIME_LIMIT=0 pnpm run pipelines:mutation:quick
# レポート生成失敗を許容する場合のみ MUTATION_REPORT_STRICT=0 を付与
# ヘビーテスト結果のキャッシュ運用
node scripts/pipelines/sync-test-results.mjs --store
node scripts/pipelines/sync-test-results.mjs --snapshot
node scripts/pipelines/compare-test-trends.mjs --json-output reports/heavy-test-trends.jsonこのリポジトリは
workspace:*を使うため、npm installはpreinstallガードで意図的に失敗させています。pnpm installを使用してください。pnpm run doctor:envはartifacts/doctor/env.jsonを出力し、終了コードは0(正常)/2(警告)/1(要修正)/3(引数不正)です。pnpm run first-runはdoctor:env -> build -> verify:liteを順に実行し、artifacts/first-runディレクトリに summary の JSON/Markdown を出力します。
- 全体概要:
docs/README.md,docs/project-organization.md - 現行アーキテクチャ全体像:
docs/architecture/CURRENT-SYSTEM-OVERVIEW.md - ゼロベース再設計の理想像:
docs/architecture/ZERO-BASED-IDEAL-DESIGN.md - 適用対象/入力/出力/ツール適性:
docs/product/PRODUCT-FIT-INPUT-OUTPUT-TOOL-MAP.md - Assurance control plane の位置付け:
docs/product/ASSURANCE-CONTROL-PLANE.md - Assurance model(claim / level / lane / evidence):
docs/quality/ASSURANCE-MODEL.md - PR自動化(Copilot→auto-fix→auto-merge):
docs/ci/pr-automation.md - リリース運用(release verify / post-deploy verify):
docs/operate/release-engineering.md - CI/品質ゲート:
docs/ci/phase2-ci-hardening-outline.md,docs/ci/label-gating.md,docs/ci/harness-taxonomy.md - ドキュメント検証ポリシー:
docs/ci/docs-doctest-policy.md - 開発向け設計ドキュメント: Enhanced State Manager, Circuit Breaker
- ドキュメント整合チェック:
pnpm run check:doc-consistency(docs/quality/doc-consistency-lint.md) - ヘビーテスト観測:
docs/ci/heavy-test-trend-archive.md,docs/ci/heavy-test-alerts.md,docs/ci/heavy-test-album.md - 仕様と検証:
docs/ci-policy.md,docs/testing/integration-runtime-helpers.md,docs/quality/,docs/quality/formal-csp.md - Context Pack v1(仕様入力契約):
docs/spec/context-pack.md - Context Pack 導入チェックリスト:
docs/guides/context-pack-onboarding-checklist.md - Context Pack Phase5+ 実践ガイド:
docs/guides/context-pack-phase5-cookbook.md - Context Pack 障害対応ランブック:
docs/operations/context-pack-troubleshooting.md - 契約カタログ(input/decision/evidence/operation):
docs/reference/CONTRACT-CATALOG.md - Spec & Verification Kit(最小パッケージ・有効化手順):
docs/reference/SPEC-VERIFICATION-KIT-MIN.md - エージェント統合:
docs/integrations/CLAUDE-CODE-TASK-TOOL-INTEGRATION.md,docs/integrations/CODEX-INTEGRATION.md - ライセンス適用範囲と notice 管理:
LICENSE,LICENSE-SCOPE.md,TRADEMARKS.md,THIRD_PARTY_NOTICES.md
When using @ts-expect-error comments, follow this structured format:
// @ts-expect-error owner:@username expires:YYYY-MM-DD reason: detailed description
const _example: number = 'type mismatch for policy example';Core fields:
owner:@username- GitHub handle responsible for the suppressionexpires:YYYY-MM-DD- Date when this suppression should be reviewed/removedreason: description- Detailed explanation (minimum 12 characters)
Each suppression entry still carries all three fields.
Examples:
// @ts-expect-error owner:@alice expires:2027-12-31 reason: narrowing todo for complex union
const result = complexUnion as string;
// @ts-expect-error owner:@bob expires:2027-06-15 reason: legacy API compatibility until v2 migration
legacyApi.unsafeMethod(data);Policy enforcement:
- ✅ CI validates all
@ts-expect-errorcomments ⚠️ Local development shows warnings only- 🔍 Script:
node scripts/ci/check-expect-error.mjs
- Full navigation:
docs/README.md - Quick starts:
docs/getting-started/QUICK-START-GUIDE.md(baseline -> structured assurance -> high-assurance PR),docs/getting-started/PHASE-6-GETTING-STARTED.md - CLI Reference:
docs/reference/CLI-COMMANDS-REFERENCE.md, API:docs/reference/API.md - CLI entrypoints in this repo: main CLI
src/cli/index.ts(ae/ae-framework), benchmark CLIsrc/cli/benchmark-cli.ts(ae-benchmark), legacy compatibility shimsrc/cli.ts
We welcome contributions! See CONTRIBUTING.md. 貢献を歓迎します!詳細はCONTRIBUTING.mdをご覧ください。
MIT License - see LICENSE.
Built with: MCP SDK, Claude/CodeX task tools, pnpm workspace, Vitest, AJV, GitHub Actions.
ae-framework — automating agentic specification, verification, and CI quality gates.