specsmith 0.10.1.dev262__tar.gz → 0.10.1.dev272__tar.gz

{specsmith-0.10.1.dev262/src/specsmith.egg-info → specsmith-0.10.1.dev272}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: specsmith
-Version: 0.10.1.dev262
+Version: 0.10.1.dev272
 Summary: Applied Epistemic Engineering toolkit — AEE agent sessions, execution profiles, FPGA/HDL governance, tool installer, 50+ CLI commands.
 Author: BitConcepts
 License-Expression: MIT
@@ -38,8 +38,6 @@ Requires-Dist: ruff>=0.4; extra == "dev"
 Requires-Dist: mypy>=1.10; extra == "dev"
 Requires-Dist: pre-commit>=3.0; extra == "dev"
 Requires-Dist: types-pyyaml>=6.0; extra == "dev"
-Requires-Dist: pytest-asyncio>=0.23; extra == "dev"
-Requires-Dist: pytest-textual-snapshot>=1.0; extra == "dev"
 Provides-Extra: docs
 Requires-Dist: mkdocs>=1.6; extra == "docs"
 Requires-Dist: mkdocs-material>=9.5; extra == "docs"
@@ -53,10 +51,6 @@ Provides-Extra: mistral
 Requires-Dist: openai>=1.0; extra == "mistral"
 Provides-Extra: gui
 Requires-Dist: PySide6>=6.6; extra == "gui"
-Provides-Extra: tui
-Requires-Dist: textual>=3.0; extra == "tui"
-Provides-Extra: webui
-Requires-Dist: nicegui>=3.0; extra == "webui"
 Provides-Extra: ag2
 Requires-Dist: ag2[ollama]; extra == "ag2"
 Provides-Extra: history-semantic
@@ -94,23 +88,17 @@ specsmith treats belief systems like code: codable, testable, and deployable. It
 epistemically-governed projects, stress-tests requirements as BeliefArtifacts, runs
 cryptographically-sealed trace vaults, and orchestrates AI agents under formal AEE governance.
 
-**0.10.0 — Multi-Agent + BYOE.** A `/plan` goes to the architect, `/fix`
-goes to the coder, `/review` goes to a reviewer that runs on a different
-model family. Each *profile* is a `(provider, model, endpoint?, fallback_chain)`
-bundle stored in `~/.specsmith/agents.json`; an *activity routing table*
-maps slash commands and AEE phases to profiles; **BYOE endpoints**
-(`~/.specsmith/endpoints.json`) let you point a profile at any
-OpenAI-v1-compatible backend you self-host (vLLM, llama.cpp `server`,
-LM Studio, TGI, ...). Cross-family **diversity guard**, capability
-filtering, transient-failure fallback chains, and TraceVault decision
-seals on every `/agent` pin are wired in by default. See
-[`docs/site/agents.md`](docs/site/agents.md) for the five-minute walkthrough.
+**0.10.1 — Governance REST API, machine-state sync, and least-privilege permissions.**
+Specsmith now serves as the governance backend for Kairos (the epistemically-governed
+Rust terminal) via `specsmith governance-serve`, keeps `.specsmith/` JSON in sync
+with `docs/` Markdown via `specsmith sync`, and gates every agent tool call via
+`specsmith agent permissions-check`. Multi-agent profiles, BYOE endpoints, and the
+AEE phase lifecycle are all fully wired.
 
 ```bash
-specsmith agents preset apply default       # frontier coder + cross-family reviewer
-specsmith endpoints add --id home-vllm \
-  --base-url http://10.0.0.4:8000/v1 --auth bearer-keyring
-specsmith run --agent opus-reviewer         # one-shot per-session pin
+specsmith governance-serve --port 7700     # Kairos governance REST API
+specsmith sync                              # sync .specsmith/ from docs/ markdown
+specsmith agent permissions-check git_push # check tool permission (REG-012)
 ```
 
 It also co-installs the standalone `epistemic` Python library for direct use in any project:
@@ -232,47 +220,82 @@ specsmith phase --project-dir ./my-project
 
 ---
 
-## AG2 Agent Shell — Local AI Agents over Ollama
+## Machine State Sync
 
-specsmith includes an AG2-based agent shell with three specialized agents:
+`.specsmith/` always mirrors the human-readable `docs/` governance files.
+Run `specsmith sync` after any change to `docs/REQUIREMENTS.md` or `docs/TESTS.md`:
 
-- **Planner** — inspects repo, generates execution plans with acceptance criteria
-- **Builder** — makes code/doc changes following the plan
-- **Verifier** — runs tests, accepts or rejects changes
+```bash
+specsmith sync                     # regenerate .specsmith/requirements.json + testcases.json
+specsmith sync --check             # CI mode: exits 1 if out of sync without writing
+specsmith sync --json              # emit sync result as JSON
+```
 
-All agents run locally on Ollama (default: `qwen2.5:14b`). Zero cloud cost.
+## Least-Privilege Agent Permissions (REG-012)
 
 ```bash
-pip install "specsmith[ag2]"              # install AG2 + Ollama support
-specsmith agent status                    # verify config + Ollama running
-specsmith agent run "fix lint errors"     # Plan → Build → Verify pipeline
-specsmith agent improve "add tests for config.py"  # self-improvement with reports
+specsmith agent permissions                      # show active permission profile
+specsmith agent permissions-check git_push       # check if git_push is allowed
+specsmith agent permissions-check git_push --no-log  # dry-run (no ledger write)
 ```
 
-The agent shell stores structured reports at `.specsmith/agent-reports/` with task ID,
-files changed, test results, verdict (ACCEPT/REJECT), and follow-up tasks.
-
-Configurable per-project in `scaffold.yml` under `agents:` or via the VS Code
-Project Settings → Agent tab.
+Configure in `docs/SPECSMITH.yml`:
+```yaml
+agent:
+  permissions:
+    preset: standard       # read_only | standard | extended | admin
+    # Or custom:
+    allow: [read_file, write_file, run_shell, git_status]
+    deny:  [git_push, git_create_pr]
+```
 
 ---
 
-## Nexus — Plain-English Governance, Local-First
+## Kairos + Governance REST API
 
-**Nexus** is the local-first Nexus runtime that turns plain English into Specsmith-governed
-work. You speak in your own words; Specsmith stays the sole authority on what counts as a
-requirement, a test, or a work item — Nexus just brokers the conversation and runs the work.
+**Kairos** is the companion Rust terminal runtime (`BitConcepts/kairos`). specsmith
+acts as the governance backend: Kairos spawns `specsmith governance-serve` at startup
+and routes all preflight and verify calls through it.
 
 ```bash
+# Start the governance REST API (Kairos calls this automatically)
+specsmith governance-serve --port 7700 --project-dir .
+
 # Classify a natural-language utterance under Specsmith governance
 specsmith preflight "fix the cleanup dry-run regression" --json
 
-# Or drop into the Nexus REPL
+# Start the agentic REPL
+specsmith run
+> what does the cleanup module do?           # read-only ask -> answered
+> fix the cleanup dry-run regression          # change -> Specsmith approves, runs
+> delete the entire dist directory            # destructive -> needs clarification
+```
+
+---
+
+## Nexus
+
+The Nexus runtime is specsmith's local-first agentic REPL — a
+governance-gated broker that sits between you and the LLM.
+
+Every utterance passes through `specsmith preflight` before execution.
+The broker classifies intent, matches requirements, and gates the action.
+After execution, `specsmith verify` checks equilibrium. The `/why` command
+shows the full governance trace.
+
+```bash
+# Interactive REPL with governance
 specsmith run
-nexus> what does the cleanup module do?           # read-only ask -> answered
-nexus> fix the cleanup dry-run regression          # change -> Specsmith approves, runs
-nexus> delete the entire dist directory            # destructive -> needs clarification
-nexus> /why                                        # toggle governance details on/off
+nexus> fix the cleanup bug         # broker classifies → accepts → executes → verifies
+nexus> /why                         # show governance trace for last action
+nexus> /exit
+```
+
+The Nexus broker:
+- **Preflight gate**: every change goes through `specsmith preflight`
+- **Bounded retry**: failed actions retry up to 3× with strategy classification
+- **Execution trace**: every action is sealed in the cryptographic trace vault
+- **`/why` toggle**: shows governance rationale in human-readable form
 ```
 
 **How it works.** A natural-language **broker** classifies intent, infers scope from

{specsmith-0.10.1.dev262 → specsmith-0.10.1.dev272}/README.md

@@ -16,23 +16,17 @@ specsmith treats belief systems like code: codable, testable, and deployable. It
 epistemically-governed projects, stress-tests requirements as BeliefArtifacts, runs
 cryptographically-sealed trace vaults, and orchestrates AI agents under formal AEE governance.
 
-**0.10.0 — Multi-Agent + BYOE.** A `/plan` goes to the architect, `/fix`
-goes to the coder, `/review` goes to a reviewer that runs on a different
-model family. Each *profile* is a `(provider, model, endpoint?, fallback_chain)`
-bundle stored in `~/.specsmith/agents.json`; an *activity routing table*
-maps slash commands and AEE phases to profiles; **BYOE endpoints**
-(`~/.specsmith/endpoints.json`) let you point a profile at any
-OpenAI-v1-compatible backend you self-host (vLLM, llama.cpp `server`,
-LM Studio, TGI, ...). Cross-family **diversity guard**, capability
-filtering, transient-failure fallback chains, and TraceVault decision
-seals on every `/agent` pin are wired in by default. See
-[`docs/site/agents.md`](docs/site/agents.md) for the five-minute walkthrough.
+**0.10.1 — Governance REST API, machine-state sync, and least-privilege permissions.**
+Specsmith now serves as the governance backend for Kairos (the epistemically-governed
+Rust terminal) via `specsmith governance-serve`, keeps `.specsmith/` JSON in sync
+with `docs/` Markdown via `specsmith sync`, and gates every agent tool call via
+`specsmith agent permissions-check`. Multi-agent profiles, BYOE endpoints, and the
+AEE phase lifecycle are all fully wired.
 
 ```bash
-specsmith agents preset apply default       # frontier coder + cross-family reviewer
-specsmith endpoints add --id home-vllm \
-  --base-url http://10.0.0.4:8000/v1 --auth bearer-keyring
-specsmith run --agent opus-reviewer         # one-shot per-session pin
+specsmith governance-serve --port 7700     # Kairos governance REST API
+specsmith sync                              # sync .specsmith/ from docs/ markdown
+specsmith agent permissions-check git_push # check tool permission (REG-012)
 ```
 
 It also co-installs the standalone `epistemic` Python library for direct use in any project:
@@ -154,47 +148,82 @@ specsmith phase --project-dir ./my-project
 
 ---
 
-## AG2 Agent Shell — Local AI Agents over Ollama
+## Machine State Sync
 
-specsmith includes an AG2-based agent shell with three specialized agents:
+`.specsmith/` always mirrors the human-readable `docs/` governance files.
+Run `specsmith sync` after any change to `docs/REQUIREMENTS.md` or `docs/TESTS.md`:
 
-- **Planner** — inspects repo, generates execution plans with acceptance criteria
-- **Builder** — makes code/doc changes following the plan
-- **Verifier** — runs tests, accepts or rejects changes
+```bash
+specsmith sync                     # regenerate .specsmith/requirements.json + testcases.json
+specsmith sync --check             # CI mode: exits 1 if out of sync without writing
+specsmith sync --json              # emit sync result as JSON
+```
 
-All agents run locally on Ollama (default: `qwen2.5:14b`). Zero cloud cost.
+## Least-Privilege Agent Permissions (REG-012)
 
 ```bash
-pip install "specsmith[ag2]"              # install AG2 + Ollama support
-specsmith agent status                    # verify config + Ollama running
-specsmith agent run "fix lint errors"     # Plan → Build → Verify pipeline
-specsmith agent improve "add tests for config.py"  # self-improvement with reports
+specsmith agent permissions                      # show active permission profile
+specsmith agent permissions-check git_push       # check if git_push is allowed
+specsmith agent permissions-check git_push --no-log  # dry-run (no ledger write)
 ```
 
-The agent shell stores structured reports at `.specsmith/agent-reports/` with task ID,
-files changed, test results, verdict (ACCEPT/REJECT), and follow-up tasks.
-
-Configurable per-project in `scaffold.yml` under `agents:` or via the VS Code
-Project Settings → Agent tab.
+Configure in `docs/SPECSMITH.yml`:
+```yaml
+agent:
+  permissions:
+    preset: standard       # read_only | standard | extended | admin
+    # Or custom:
+    allow: [read_file, write_file, run_shell, git_status]
+    deny:  [git_push, git_create_pr]
+```
 
 ---
 
-## Nexus — Plain-English Governance, Local-First
+## Kairos + Governance REST API
 
-**Nexus** is the local-first Nexus runtime that turns plain English into Specsmith-governed
-work. You speak in your own words; Specsmith stays the sole authority on what counts as a
-requirement, a test, or a work item — Nexus just brokers the conversation and runs the work.
+**Kairos** is the companion Rust terminal runtime (`BitConcepts/kairos`). specsmith
+acts as the governance backend: Kairos spawns `specsmith governance-serve` at startup
+and routes all preflight and verify calls through it.
 
 ```bash
+# Start the governance REST API (Kairos calls this automatically)
+specsmith governance-serve --port 7700 --project-dir .
+
 # Classify a natural-language utterance under Specsmith governance
 specsmith preflight "fix the cleanup dry-run regression" --json
 
-# Or drop into the Nexus REPL
+# Start the agentic REPL
+specsmith run
+> what does the cleanup module do?           # read-only ask -> answered
+> fix the cleanup dry-run regression          # change -> Specsmith approves, runs
+> delete the entire dist directory            # destructive -> needs clarification
+```
+
+---
+
+## Nexus
+
+The Nexus runtime is specsmith's local-first agentic REPL — a
+governance-gated broker that sits between you and the LLM.
+
+Every utterance passes through `specsmith preflight` before execution.
+The broker classifies intent, matches requirements, and gates the action.
+After execution, `specsmith verify` checks equilibrium. The `/why` command
+shows the full governance trace.
+
+```bash
+# Interactive REPL with governance
 specsmith run
-nexus> what does the cleanup module do?           # read-only ask -> answered
-nexus> fix the cleanup dry-run regression          # change -> Specsmith approves, runs
-nexus> delete the entire dist directory            # destructive -> needs clarification
-nexus> /why                                        # toggle governance details on/off
+nexus> fix the cleanup bug         # broker classifies → accepts → executes → verifies
+nexus> /why                         # show governance trace for last action
+nexus> /exit
+```
+
+The Nexus broker:
+- **Preflight gate**: every change goes through `specsmith preflight`
+- **Bounded retry**: failed actions retry up to 3× with strategy classification
+- **Execution trace**: every action is sealed in the cryptographic trace vault
+- **`/why` toggle**: shows governance rationale in human-readable form
 ```
 
 **How it works.** A natural-language **broker** classifies intent, infers scope from

{specsmith-0.10.1.dev262 → specsmith-0.10.1.dev272}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "specsmith"
-version = "0.10.1.dev262"
+version = "0.10.1.dev272"
 description = "Applied Epistemic Engineering toolkit — AEE agent sessions, execution profiles, FPGA/HDL governance, tool installer, 50+ CLI commands."
 readme = "README.md"
 license = "MIT"
@@ -51,8 +51,6 @@ dev = [
     "mypy>=1.10",
     "pre-commit>=3.0",
     "types-pyyaml>=6.0",
-    "pytest-asyncio>=0.23",
-    "pytest-textual-snapshot>=1.0",
 ]
 docs = [
     "mkdocs>=1.6",
@@ -67,8 +65,6 @@ openai = ["openai>=1.0"]
 gemini = ["google-genai>=1.0"]
 mistral = ["openai>=1.0"]  # Mistral uses the openai SDK pointed at api.mistral.ai
 gui = ["PySide6>=6.6"]
-tui = ["textual>=3.0"]
-webui = ["nicegui>=3.0"]
 # AG2 agent shell (Planner/Builder/Verifier over Ollama)
 ag2 = ["ag2[ollama]"]
 # Optional semantic backend for `specsmith history search --semantic` (REQ-135).
@@ -186,15 +182,9 @@ module = [
     "specsmith.serve",
     "specsmith.toolrules",
     "specsmith.tool_installer",
-    "specsmith.commands.*",
-    "specsmith.eval.*",
-    "specsmith.feature_flags",
-    "specsmith.instinct",
-    "specsmith.tui.*",
-    "specsmith.webui.*",
+    "specsmith.commands.intelligence",
 ]
 ignore_errors = true
 
 [tool.pytest.ini_options]
 testpaths = ["tests"]
-asyncio_mode = "auto"