[Extension]: Update AEE catalog entry to v1.0.1
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 68/100
Línea de trabajo
Encuentra la entrada existente del catálogo para AEE v1.0.0 y compárala con la entrada propuesta en este issue. Actualiza su versión, descripción, dependencias de herramientas, URLs, cantidades de comandos y hooks, y etiquetas para que coincidan con v1.0.1; después, ejecuta las pruebas de validación del catálogo o del manifiesto mencionadas en el issue. La tarea está terminada cuando la entrada se valida y representa la extensión publicada v1.0.1.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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 #4642, which failed automated validation because its body was missing the
Submission Requirementschecklist section; #4642 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
- Lenguaje dominante
- Python
- Estrellas
- 138k
- Forks
- 12.4k
- Merge medio
- 3 d 4 h
- PR fusionados (30 d)
- 154
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/spec-kit
-
enhancement needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
enhancement needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
enhancement needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
enhancement needs-triage triage-can-wait
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Todos los issues de github/spec-kit
Issues similares
-
bug confirmed issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
open-webui/open-webui#30750 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
OpenwaterHealth/openmotion-bloodflow-app#604 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100