Applied Epistemic Engineering toolkit — AEE agent sessions, execution profiles, FPGA/HDL governance, tool installer, 50+ CLI commands.
Project description
specsmith
Applied Epistemic Engineering toolkit for AI-assisted development.
Intelligence proposes. Constraints decide. The ledger remembers.
specsmith treats belief systems like code: codable, testable, and deployable. It scaffolds epistemically-governed projects, stress-tests requirements as BeliefArtifacts, runs cryptographically-sealed trace vaults, and orchestrates AI agents under formal AEE governance.
It also co-installs the standalone epistemic Python library for direct use in any project:
from epistemic import AEESession # works in any Python 3.10+ project
from epistemic import BeliefArtifact, StressTester, CertaintyEngine
What is Applied Epistemic Engineering?
AEE treats requirements, decisions, and assumptions — the beliefs your project depends on — as engineering artifacts subject to the same discipline as code: version control, testing, and refactoring.
The 4-step core method: Frame → Disassemble → Stress-Test → Reconstruct
The 5 foundational axioms:
- Observability — every belief must be inspectable
- Falsifiability — every belief must be challengeable
- Irreducibility — beliefs decompose to atomic primitives
- Reconstructability — every failed belief can be rebuilt
- Convergence — stress-test + recovery always reaches Equilibrium
The AEE Workflow — 7 Phases
specsmith tracks your project through the full AEE development cycle:
🌱 Inception → 🏗 Architecture → 📋 Requirements → ✅ Test Spec
→ ⚙ Implementation → 🔬 Verification → 🚀 Release
specsmith phase # show current phase + readiness checklist
specsmith phase next # advance to the next phase (runs checks first)
specsmith phase set requirements # jump to a specific phase
specsmith phase list # list all phases
The current phase is persisted in scaffold.yml as aee_phase and displayed in the VS Code
Settings Panel. Each phase has a checklist of file/command criteria, recommended commands,
and a readiness percentage.
Install
Recommended — via the VS Code extension (creates a project-isolated environment):
- Install the specsmith AEE Workbench VS Code extension
- Open
Ctrl+Shift+,(⚙ specsmith Settings) - Click 🔒 Create Environment — creates
~/.specsmith/venv/with specsmith + your provider packages
The extension uses this environment for all agent sessions and terminal commands.
Or via pipx (system-wide):
pipx install specsmith # core CLI + epistemic library
pipx inject specsmith anthropic # + Claude support
pipx inject specsmith openai # + GPT / O-series support
pipx inject specsmith google-generativeai # + Gemini support
Or with pip:
pip install specsmith # core
pip install "specsmith[anthropic]" # + Claude
pip install "specsmith[openai]" # + GPT/O-series
pip install "specsmith[gemini]" # + Gemini
Update:
pipx upgrade specsmith
specsmith self-update
Quick Start
# New project (interactive)
specsmith init
# Adopt an existing project
specsmith import --project-dir ./my-project
# Check governance health
specsmith audit --project-dir ./my-project
# Run AEE stress-test on requirements
specsmith stress-test --project-dir ./my-project
# Full epistemic audit (certainty + logic knots + recovery proposals)
specsmith epistemic-audit --project-dir ./my-project
# Start the agentic REPL
specsmith run --project-dir ./my-project
# Check current AEE workflow phase
specsmith phase --project-dir ./my-project
VS Code Extension
The specsmith AEE Workbench VS Code extension is the flagship client:
# VS Code: Ctrl+Shift+P → specsmith: New Agent Session
# Settings: Ctrl+Shift+, (⚙ specsmith Settings — global)
# Project Settings: Ctrl+Shift+G (⚙ Project Settings — per-project)
Key features:
- Dual-panel architecture — ⚙ specsmith Settings (global: venv, version, Ollama, system) and ⚙ Project Settings (per-project: scaffold, tools, files, actions, execution)
- Global environment management —
~/.specsmith/venv/with Create / Update / Rebuild / Delete; persistent restart banner; Remove System Installs cleanup button - VCS context at session start — git status + recent commits shown in chat and in system prompt
- Execution profiles — safe / standard / open / admin; custom allow/block command lists
- AEE phase indicator — shows current phase with readiness %, Next Phase button, phase selector
- AI agent sessions — independent process per project, JSONL bridge, chat with file injection
- Live model listing — Anthropic, OpenAI, Gemini, Mistral, local Ollama (GPU-aware)
- Ollama integration — model manager (update/remove/update-all), version check, upgrade
- FPGA/HDL tool support — vivado, gtkwave, vsg, ghdl, verilator, yosys, nextpnr, and 15 more
- Tool installer — scan installed tools; one-click install via winget/brew/apt for missing tools
- API key management — stored in OS credential store (Windows Credential Manager / macOS Keychain)
- Update checker — PyPI version check, auto-checks on panel open, release channel selector
Supporting specsmith
specsmith is open source and built by a small team. Every bit of support helps:
- ⭐ Star specsmith and specsmith-vscode on GitHub
- 📣 Tell your friends and colleagues — word of mouth is our best marketing
- 🐛 Report bugs via GitHub Issues — even small ones help
- 💡 Suggest features via GitHub Discussions — we read every suggestion
- 🔧 Fix bugs and contribute — see CONTRIBUTING.md; PRs welcome
- 📝 Write about specsmith — blog posts, tutorials, and talks help the community grow
- ❤️ Sponsor BitConcepts — directly funds development
Ollama — Local LLMs (Zero API Cost)
specsmith has first-class Ollama support, including:
specsmith ollama gpu # detect GPU and VRAM tier
specsmith ollama available # show catalog filtered by VRAM budget
specsmith ollama available --task code # filter by task type
specsmith ollama pull qwen2.5:14b # download a model
specsmith ollama suggest requirements # task-based recommendations
specsmith ollama list # show installed models
GPU-aware context sizing in the VS Code extension: 4K/8K/16K/32K tokens based on detected VRAM.
Override with specsmith.ollamaContextLength in VS Code settings.
FPGA / HDL Projects
specsmith supports FPGA-specific project types with full governance:
# scaffold.yml
type: fpga-rtl-amd # or fpga-rtl-intel / fpga-rtl-lattice / fpga-rtl
fpga_tools:
- vivado
- gtkwave
- vsg
- ghdl
- verilator
Supported tools: Synthesis: vivado, quartus, radiant, diamond, gowin. Simulation: ghdl, iverilog, verilator, modelsim, questasim, xsim. Waveform: gtkwave, surfer. Linting: vsg, verible, svlint. Formal: symbiyosys. OSS flow: yosys, nextpnr, openFPGALoader.
50+ CLI Commands
Governance: init import audit validate diff upgrade compress doctor export architect
AEE Epistemic: stress-test epistemic-audit belief-graph trace seal/verify/log integrate
Workflow: phase show/set/next/list ledger add/list req list/add/gaps/trace
Agent: run agent providers/tools/skills
Ollama: ollama list/available/gpu/pull/suggest
Workspace: workspace init/audit/export
VCS: commit push sync branch pr status
Tools: tools scan [--fpga] tools install <tool> tools rules [--tool] [--list]
Tools: exec ps abort watch optimize credits self-update
Auth: auth set/list/remove/check
Patent: patent search/prior-art
35 Project Types
Software: Python CLI/lib/web, Rust, Go, C/C++, .NET, Node.js/TypeScript, mobile, microservices, data/ML.
Hardware/Embedded: FPGA/RTL (Xilinx, Intel, Lattice, generic), Yocto BSP, embedded C/C++.
Documents: Technical specs, research papers, API specs, requirements management.
Business/Legal: Business plans, patent applications, compliance frameworks.
epistemic Library
The standalone epistemic Python library works in any Python 3.10+ project — no specsmith coupling:
from epistemic import AEESession, BeliefArtifact, StressTester
session = AEESession("my-project", threshold=0.70)
session.add_belief(
artifact_id="HYP-001",
propositions=["The API always returns valid JSON"],
epistemic_boundary=["Valid auth token required"],
)
session.accept("HYP-001")
result = session.run()
print(result.summary())
# certainty=0.55, failures=2, equilibrium=False
Use cases: linguistics research, compliance pipelines, AI alignment, patent prosecution.
Governance Rules (H1–H13)
13 hard rules enforced by specsmith validate:
- H11 — Every loop or blocking wait must have a timeout, fallback exit, and diagnostic message.
- H12 — Windows multi-step automation goes into
.cmdfiles, not inline shell invocations. - H13 — Agent tools must declare epistemic contracts (what they claim and what they cannot detect).
The specsmith Bootstrap
specsmith governs itself — the specsmith repo is a specsmith-managed project. Run specsmith audit
in this repo to check its governance health. This means every feature we add to specsmith is
immediately dogfooded on specsmith itself. The VS Code extension
is developed alongside it as the flagship client.
Documentation
specsmith.readthedocs.io — Full manual: AEE primer, command reference, project types, tool registry, governance model, Ollama guide, VS Code extension.
Links
License
MIT — Copyright (c) 2026 BitConcepts, LLC.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file specsmith-0.3.6.dev185.tar.gz.
File metadata
- Download URL: specsmith-0.3.6.dev185.tar.gz
- Upload date:
- Size: 307.6 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
573d1a9748e517ca8d6d40ecdd92ea250779fe0ce83ce53e326c9bb2af1497ba
|
|
| MD5 |
b73079383ff17281d54f06f88105ed82
|
|
| BLAKE2b-256 |
6ed0bfbfc910a4b25c8366b3db2c99c6c9cb17c8bbe73eb5599ef4bd57c5dd40
|
Provenance
The following attestation bundles were made for specsmith-0.3.6.dev185.tar.gz:
Publisher:
dev-release.yml on BitConcepts/specsmith
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
specsmith-0.3.6.dev185.tar.gz -
Subject digest:
573d1a9748e517ca8d6d40ecdd92ea250779fe0ce83ce53e326c9bb2af1497ba - Sigstore transparency entry: 1262521556
- Sigstore integration time:
-
Permalink:
BitConcepts/specsmith@1620a4b5f8539afed4fded69a8993f4b9cc68937 -
Branch / Tag:
refs/heads/develop - Owner: https://github.com/BitConcepts
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
dev-release.yml@1620a4b5f8539afed4fded69a8993f4b9cc68937 -
Trigger Event:
push
-
Statement type:
File details
Details for the file specsmith-0.3.6.dev185-py3-none-any.whl.
File metadata
- Download URL: specsmith-0.3.6.dev185-py3-none-any.whl
- Upload date:
- Size: 349.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
23989f1256d5a91f3a432d143613f34d8902fac16ba998b7273670fa907def96
|
|
| MD5 |
67b87bc761638c8d52b1848ab9b8f9c9
|
|
| BLAKE2b-256 |
a77a1586f41fe633bacaf0aa2693a7451a16d57a598fffd8bb7c0358a9ca5464
|
Provenance
The following attestation bundles were made for specsmith-0.3.6.dev185-py3-none-any.whl:
Publisher:
dev-release.yml on BitConcepts/specsmith
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
specsmith-0.3.6.dev185-py3-none-any.whl -
Subject digest:
23989f1256d5a91f3a432d143613f34d8902fac16ba998b7273670fa907def96 - Sigstore transparency entry: 1262521567
- Sigstore integration time:
-
Permalink:
BitConcepts/specsmith@1620a4b5f8539afed4fded69a8993f4b9cc68937 -
Branch / Tag:
refs/heads/develop - Owner: https://github.com/BitConcepts
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
dev-release.yml@1620a4b5f8539afed4fded69a8993f4b9cc68937 -
Trigger Event:
push
-
Statement type: