Repository navigation
[Extension]: Update AEE catalog entry to v1.5.1 #4984
Description
Extension ID
aee
Extension Name
Applied Epistemic Engineering
Version
1.5.1
Description
Checks the claims in a spec-driven project against their evidence at every stage, and shows plainly what is verified, what is not, and what remains not understood.
Author
ElectroHire
Repository URL
https://github.com/electrohire/spec-kit-aee
Download URL
https://github.com/electrohire/spec-kit-aee/archive/refs/tags/v1.5.1.zip
License
MIT
Homepage (optional)
https://github.com/electrohire/spec-kit-aee
Documentation URL (optional)
https://github.com/electrohire/spec-kit-aee#readme
Changelog URL (optional)
https://github.com/electrohire/spec-kit-aee/blob/main/CHANGELOG.md
Required Spec Kit Version
=1.0.0,<2
Required Tools (optional)
- python (>=3.11) — required
- aee CLI (>=1.5.0,<2) — the Applied Epistemic Engineering engine, published on PyPI as
applied-epistemic-engineering. Required, but installed automatically: when the Python running the extension lacks it, the runner installs it, together withjsonschema>=4.0for evaluator composition, into a private environment under.specify/extensions/aee/.runtime. - spec-kit-evaluator (>=1.0.0,<2) — the Spec Kit extension implementing the Evaluator Contract. A required companion, installed automatically:
assessinstalls the pinned v1.1.1 release archive throughspecify extension add evaluatorafter verifying its SHA-256. - rtk — optional token-economy tool; every workflow degrades gracefully when it is absent
- headroom — optional token-economy tool; every workflow degrades gracefully when it is absent
- token-router — optional token-economy tool; every workflow degrades gracefully when it is absent
- ollama — optional; used only by the optional token-economy routing
Automatic installation can be turned off with SPECKIT_AEE_AUTO_INSTALL=0. The runner then refuses (exit 2) and names the manual install command.
Number of Commands
10 (speckit.aee.draft-claims, speckit.aee.assess, speckit.aee.challenge, speckit.aee.trace, speckit.aee.verify, speckit.aee.gate, speckit.aee.review, speckit.aee.gaps, speckit.aee.route-evidence, speckit.aee.report-savings)
Number of Hooks (optional)
5 (after_specify, after_plan, after_tasks, after_implement, after_verify)
Tags
epistemics, evidence, provenance, uncertainty, governance
Key Features
- One install step (since 1.5.0; 1.5.1 fixes the last command document that blocked it). After
specify extension add aee, the extension installs its engine,jsonschema, and the Evaluator extension by itself on first use, with no manual pip or extension installs. - Draft atomic claims from a spec's requirements for human ratification; drafts start as
draftand the tool never upgrades them - Assess claims against their evidence and show the life-cycle stage each claim has actually reached (created, checked, explained, accepted, digested), with the reported status capped by that stage
- Ships as one system with the common Evaluator extension. AEE's results are composed through it, so every evaluator's output is handled consistently.
composeruns the Evaluator's composer with dependencies AEE has installed. - Report machine verification and human acceptance side by side, never merged into one number, plus a plain statement of what remains not understood
- Challenge claims on atomicity, boundaries, falsifiability, dependencies, and evidence independence
- Policy gates (accept / challenge / abstain) and measured per-source reliability
- Render the claim dependency graph; verify the tamper-evident evidence ledger without claiming its contents are true
- CI-friendly decision gate; materiality-filtered review queue between assessments; gap register from a verification matrix
- Route oversized evidence into raw slices, with token-savings figures that are measured, never estimated
Testing Checklist
- Extension installs successfully via download URL
- All commands execute without errors
- Documentation is complete and accurate
- No security vulnerabilities identified
- Tested on at least one real project
Submission Requirements
- Valid
extension.ymlmanifest included - README.md with installation and usage instructions
- LICENSE file included
- GitHub release created with version tag
- All command files exist and are properly formatted
- Extension ID follows naming conventions (lowercase-with-hyphens)
Testing Details
Release: https://github.com/electrohire/spec-kit-aee/releases/tag/v1.5.1 (published, not a draft). Tag v1.5.1 points to commit 4fe7e1846da0699f08a60bfcd3cc2549b2577423. The download URL returns HTTP 200. The archive's SHA-256 is f26bb26e78d1adea78ec09c1dbdb466e071cfa9791a1fbd21eb27bd099b665a5 (stable across downloads). Its extension.yml reads id aee, version 1.5.1, 10 command files, 5 hooks, with README.md and LICENSE at the root.
Exact public archive, hosted sandbox installs on 9 platforms. Two runs, both passing on Ubuntu, Windows, and macOS × Python 3.11, 3.12, and 3.13, each with a fail-closed gate job:
- https://github.com/electrohire/spec-kit-aee/actions/runs/38788737495, started by publishing the release.
- https://github.com/electrohire/spec-kit-aee/actions/runs/38790174097, a re-run against the same
v1.5.1archive whose logs record the resolved dependency versions.
Each run:
- Starts from a fresh GitHub-hosted runner with only
specify-cli==1.2.0installed (hash-locked) in a new environment, and confirms theaeepackage and command are absent. - Runs
specify init, thenspecify extension add aee --from https://github.com/electrohire/spec-kit-aee/archive/refs/tags/v1.5.1.zip, and asserts that Spec Kit reports version 1.5.1 installed: 10 rendered commands, 5 hooks, all placeholders resolved. - Runs the first AEE operation (
assess) on a package-free Python with noaeeon PATH. AEE installs its dependencies by itself, and the logs record, on every platform:applied-epistemic-engineering 1.5.1(the latest engine on PyPI),jsonschema 4.26.0, and the Evaluator extension1.1.1, installed throughspecifyfrom its SHA-256-verified release archive. - Exercises assess, compose (with the Evaluator's real composer), gate, verify (ledger valid), graph, challenge, and gaps. It also checks that, with automatic installation disabled, assess refuses cleanly when the Evaluator is missing, and that a removed Evaluator is reinstalled by the next assess.
Test suite: on PR #23 (identical tree to the release commit), tests and sandbox acceptance ran on all 9 OS × Python combinations: 23 of 23 checks passed. CI on main at the release commit also passed.
The commands are agent prompts. Their scripted operations ran in the sandbox tests above.
Example Usage
# One install step: the engine, jsonschema, and the Evaluator extension follow automatically
specify extension add aee --from https://github.com/electrohire/spec-kit-aee/archive/refs/tags/v1.5.1.zip
# Draft ratifiable claims from your spec, then assess them
/speckit.aee.draft-claims
/speckit.aee.assess phase=after_specify artifact=specs/001-search/spec.mdProposed Catalog Entry
{
"aee": {
"name": "Applied Epistemic Engineering",
"id": "aee",
"description": "Checks the claims in a spec-driven project against their evidence at every stage, and shows plainly what is verified, what is not, and what remains not understood.",
"author": "ElectroHire",
"version": "1.5.1",
"download_url": "https://github.com/electrohire/spec-kit-aee/archive/refs/tags/v1.5.1.zip",
"sha256": "f26bb26e78d1adea78ec09c1dbdb466e071cfa9791a1fbd21eb27bd099b665a5",
"repository": "https://github.com/electrohire/spec-kit-aee",
"homepage": "https://github.com/electrohire/spec-kit-aee",
"documentation": "https://github.com/electrohire/spec-kit-aee#readme",
"changelog": "https://github.com/electrohire/spec-kit-aee/blob/main/CHANGELOG.md",
"license": "MIT",
"category": "process",
"effect": "read-write",
"requires": {
"speckit_version": ">=1.0.0,<2",
"tools": [
{ "name": "python", "version": ">=3.11", "required": true },
{ "name": "aee", "version": ">=1.5.0,<2", "required": true },
{ "name": "spec-kit-evaluator", "version": ">=1.0.0,<2", "required": true },
{ "name": "rtk", "required": false },
{ "name": "headroom", "required": false },
{ "name": "token-router", "required": false },
{ "name": "ollama", "required": false }
]
},
"provides": {
"commands": 10,
"hooks": 5
},
"tags": ["epistemics", "evidence", "provenance", "uncertainty", "governance"],
"verified": false,
"downloads": 0,
"stars": 0,
"created_at": "2026-09-15T00:00:00Z",
"updated_at": "2026-10-15T00:00:00Z"
}
}Additional Context
Note for maintainers: this updates the existing catalog entry for the AEE extension to v1.5.1. It supersedes the pending v1.5.0 update #4981 (catalog PR #4982), which has not been merged. If #4982 is merged first, this is a 1.5.0 → 1.5.1 update; either way only the fields below change. It is not a duplicate. The Evaluator Contract v1.1.1 update (#4979, catalog PR #4980) is already merged.
What changed relative to the v1.5.0 entry:
- Version 1.5.0 → 1.5.1, with the download URL and the
sha256of the v1.5.1 archive. - Unchanged: commands (10), hooks (5), Spec Kit range (
>=1.0.0,<2), tools and their version ranges, tags, license, and category. - 1.5.1 is documentation only. The
speckit.aee.draft-claimscommand document no longer tells the agent to confirm the engine is installed before running, which blocked the automatic engine install. The usage and dependency-audit docs are updated, and the README states the supported platforms. The runner and its dependency pins are unchanged.
The v1.5.1 tag will not be moved or recreated.
AI assistance disclosure: the 1.5.1 changes, their tests and CI, the release, and this submission were prepared by Claude Code (Anthropic; model claude-opus-5-5), working autonomously on behalf of @tbitcs. Commits carry Assisted-by: trailers. All test results above are from runs that actually took place, with links provided.
Activity
github-actions commentedon Oct 16, 2026
cc @github/spec-kit-maintainers — new catalog submission for review.
Update Applied Epistemic Engineering extension to v1.5.1
github-actions commentedon Oct 16, 2026
Pull request created: #4995
Update Applied Epistemic Engineering extension to v1.5.1 (#4995)