[Extension]: Update AEE catalog entry to v1.0.1
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Locate the existing AEE v1.0.0 catalog entry and compare it with the proposed v1.0.1 JSON in this issue. Update the version, description, tool dependencies, URLs, and command or hook counts, then run the catalog's automated validation; done means the entry validates and matches the released v1.0.1 metadata.
Written by the indexing model from the issue text.
Description
Extension ID
aee
Extension Name
Applied Epistemic Engineering
Version
1.0.1
Description
Challenge claims, trace evidence, propagate uncertainty, and route epistemic failures across phases
Author
ElectroHire
Repository URL
https://github.com/electrohire/spec-kit-aee
Download URL
https://github.com/electrohire/spec-kit-aee/archive/refs/tags/v1.0.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
Required Tools (optional)
- python (>=3.11) — required
- aee CLI — the Applied Epistemic Engineering engine (>=1.0.2,<2); 1.0.2 introduced the
gapscommand — required - spec-kit-evaluator (>=1.0.0,<2) — Spec Kit extension implementing the Evaluator Contract; install it first — required
Number of Commands
6 (speckit.aee.assess, speckit.aee.challenge, speckit.aee.trace, speckit.aee.verify, speckit.aee.gate, speckit.aee.gaps)
Number of Hooks (optional)
5 (after_specify, after_plan, after_tasks, after_implement, after_verify)
Tags
epistemics, evidence, provenance, uncertainty, governance
Key Features
- Challenge claims on atomicity, boundaries, falsifiability, dependencies, and evidence independence
- Assess explicit claims and emit a rich AEE assessment plus an Evaluator Contract result
- Render the claim dependency graph and inspect epistemic provenance
- Verify the tamper-evident AEE ledger without claiming its contents are true
- Apply a CI-friendly decision gate to an AEE assessment
- Generate and update the gap register from a verification matrix and test evidence
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
Tested on (CI): Ubuntu 24.04 with Python 3.11 and 3.13; Windows with Python 3.12 — all installing the real AEE engine 1.0.2 from hash-locked requirements (pip install --require-hashes).
Manifest validation: the release extension.yml is parsed with Spec Kit's own manifest parser in CI (validate job), and deterministic extension.yml/documentation compliance tests run on every push.
What changed in v1.0.1 vs v1.0.0: dependency metadata now uses Spec Kit's documented tool metadata (Python, AEE engine 1.0.2, Evaluator Contract); the unsupported requires.commands field was replaced with explicit installation guidance; the description was trimmed to 99 characters per the publishing guide; the exact AEE claim field vocabulary is documented in speckit.aee.assess.
Example Usage
# Install extension
specify extension add aee --from https://github.com/electrohire/spec-kit-aee/archive/refs/tags/v1.0.1.zip
# Assess the claims in your current spec
/speckit.aee.assess
Proposed Catalog Entry
{
"aee": {
"name": "Applied Epistemic Engineering",
"id": "aee",
"description": "Challenge claims, trace evidence, propagate uncertainty, and route epistemic failures across phases",
"author": "ElectroHire",
"version": "1.0.1",
"download_url": "https://github.com/electrohire/spec-kit-aee/archive/refs/tags/v1.0.1.zip",
"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",
"requires": {
"speckit_version": ">=1.0.0",
"tools": [
{ "name": "python", "version": ">=3.11", "required": true },
{ "name": "aee", "version": ">=1.0.2,<2", "required": true },
{ "name": "spec-kit-evaluator", "version": ">=1.0.0,<2", "required": true }
]
},
"provides": {
"commands": 6,
"hooks": 5
},
"tags": ["epistemics", "evidence", "provenance", "uncertainty", "governance"],
"verified": false,
"downloads": 0,
"stars": 0
}
}
Additional Context
Note for maintainers: this updates the existing catalog entry for the AEE extension (v1.0.0 → v1.0.1, new description). It is separate from #4626, which requested dependency-metadata corrections for the existing v1.0.0 entry. Please do not close this as a duplicate of #4626.
- This issue supersedes #4661, which failed automated validation only because the validator's execution environment blocked the archive download (all other checks — extension ID, semver, repository files, URL ownership/pinning, matching release, all submission checkboxes — passed); #4661 is being closed.
- Existing catalog entry (v1.0.0) should be updated to this v1.0.1 entry: new version, new 99-character description, declared tool dependencies.
- Release: https://github.com/electrohire/spec-kit-aee/releases/tag/v1.0.1
- Dominant language
- Python
- Stars
- 138k
- Forks
- 12.4k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 154
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/spec-kit
-
enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
enhancement needs-triage triage-can-wait
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·