llm-connect/.claude/rules/repo-boundary.md at bd2315cf4c45455ea69578ff0f1279c27de271c2

Files

Bernd Worsch d71f4114d1 feat: WP-0001 foundation + WP-0002 core extensions

WP-0001 — Foundation & GAAF Baseline
- SCOPE.md, ARCHITECTURE-LAYERS.md, contracts/ tree
- .claude/rules/ stubs filled (architecture, stack, boundary)
- 57 tests (pytest), pyproject.toml with ruff+mypy, CI workflow

WP-0002 — Core Extensions (FR-4 + FR-3)
- FR-4: BudgetTracker (thread-safe) + LLMBudgetExceededError +
  optional RunConfig.budget_tracker + enforcement in all adapters
- FR-3: async_execute_prompt on LLMAdapter ABC (asyncio.to_thread
  fallback) + native asyncio.create_subprocess_exec in ClaudeCodeAdapter

81 tests passing.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-01 22:24:14 +00:00

877 B

Raw Blame History

Repo boundary

This repo owns llm-connect — the multi-provider LLM client library — only.

It does NOT own:

API key storage / secret management → caller's environment (env vars, key files, vault). llm-connect resolves keys but does not store them.
Consumer routing logic → inter-hub/AgentBridge.hs, markitect etc. RoutingPolicy (WP-0003) provides primitives; policy data belongs in the consumer.
The Claude Code CLI binary → installed separately; ClaudeCodeAdapter shells out to it.
markitect application code → markitect.llm is a shim that re-exports from here; all implementation lives in this repo.
State hub / custodian infrastructure → the-custodian/state-hub/
IHF bridge scripts → inter-hub/scripts/llm_bridge.py lives in inter-hub, not here. llm-connect is a dependency of that script.

877 B Raw Blame History

Repo boundary

877 B

Raw Blame History