Skip to content

Releases: alejandro-ventures/llm-agnostic-icm-framework

v2.1.0 — evidence, contracts, and four real-use workflows

Choose a tag to compare

@alejandro-ventures alejandro-ventures released this 15 Jul 14:56

Evidence and contracts: honest compatibility claims, a written threat model, machine-checked workflow contracts, a leak gate — and four new real-use workflows.

Added

  • COMPATIBILITY.md — per-client evidence ledger (Verified / Experimental / Conceptual / Unsupported); the README's "any LLM-backed assistant" claim narrowed to what's demonstrated.
  • SECURITY.md — threat model and enforcement map; states the core invariant (processed content is data, never instructions) and the honest code-vs-convention line.
  • AGENTS.md → Instruction precedence — fixed 5-level precedence order, deterministic routing, and stop-on-ambiguity for state-changing work.
  • SKILL.md contract keys — every workflow's frontmatter now declares network, destructive, and gates; health_check.py fails the build if any key is missing.
  • _core/scripts/leak_scan.py — publication gate: scans tree or full history (UTF-16-aware) for credential patterns, unlisted emails, and a private terms file that never enters the repo. Wired into CI.
  • CI on windows-latest in addition to ubuntu (the workspace is PowerShell-heavy; test where it runs).
  • Four workflows from real use: transcribe (fully local ASR + diarization, offline-enforced), background-remove (documented model decision tree), data-room-check (read-only checklist audit), recurrence-review (mines scratch history, human-gated workflow promotion — ships with its own test suite).
  • Token-tracker v2 — schema v2 with validated intent keys; writes routed through the sandbox guard.

Changed

  • make_provenance.py hashes committed blob content (platform-independent manifest).
  • PROVENANCE.md — manifest scope clarified: git-tracked source and docs only.

Full changelog: https://github.com/alejandro-ventures/llm-agnostic-icm-framework/blob/main/CHANGELOG.md

v2.0.0 — enforce the rules in code

Choose a tag to compare

@alejandro-ventures alejandro-ventures released this 12 Jul 08:44

From concept demo to hardened workspace: the framework rules are now enforced by code, not just documented.

Highlights

  • _core/scripts/sandbox.py — Tier-0 filesystem guardrail wired into every workflow script (out-of-workspace writes and secret files refused in code), with a CI-strict self-test
  • _core/SANDBOXING.md — explicit threat model + three isolation tiers, incl. a per-workflow disposable Windows Sandbox launcher
  • _core/token-tracker/ — per-run cost accounting (tokens, local-vs-cloud, minutes saved): the automation business case as data
  • _core/integrations/ — MCP connectors defined once, projected into Codex / Claude / VS Code configs by gen-harness-config.py
  • _core/SMALL-MODELS.md + shared/hooks/deny_secret_read.py — design rules and a harness-level PreToolUse guard that keep workflows safe under small local models
  • PORTABILITY.md — the five agnosticism rules and the harness matrix
  • workflows/scratch — routing fallback so no task ever improvises a write location
  • Per-workflow venvs; ocr-folder now uses a pure-pip ONNX OCR stack (no system Tesseract)
  • CI + reproducible provenance manifest (_core/scripts/make_provenance.py)

Full details in CHANGELOG.md.