tegwick c11a942bb7 IB-WP-0020-T01: routing config schema and parser
Add a small YAML routing config schema (schema_version 1) and a
parser-only loader at src/infospace_bench/routing_config.py. The
loader validates the declarative shape — task_types with candidates,
optional per-task quality_floor, optional default_quality_floor,
optional ledger_path, optional stage_to_task_type override map — and
refuses bad shapes before any network or workspace work happens.

Supported provider names: openrouter, claude_code, openai, gemini.
Unknown providers, missing required candidate fields, out-of-range
quality floors, negative max_cost_per_1k, duplicate candidate ids
within a task type, and non-mapping stage_to_task_type all raise
focused InfospaceError codes that callers can pattern-match.

docs/routing-config.md documents the schema with two annotated
examples (OpenRouter-only two-tier, and adaptive with a ClaudeCode
baseline) plus the full "what fails fast" list.

16 parser tests cover happy-path round-trip, file load, missing file,
malformed YAML, and every validation surface (wrong/missing schema
version, empty task_types, empty candidates, missing required fields,
unsupported provider, negative cost, out-of-range quality_floor,
duplicate ids, non-mapping stage_map, non-string ledger_path).

T02 will turn a RoutingConfig into a live llm-connect RoutingPolicy /
AdaptiveRoutingPolicy with constructed LLMAdapter instances.

160 tests pass, 1 skipped.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-18 18:09:28 +02:00
2026-05-03 19:25:29 +02:00
2026-05-18 16:55:43 +02:00
2026-05-18 16:55:43 +02:00
2026-05-03 19:25:29 +02:00
2026-05-03 16:52:54 +00:00
2026-05-15 16:01:35 +02:00

infospace-bench

Workspace and service for creating, developing, evaluating, and inspecting structured knowledge spaces.

This repo is the application-layer successor for the infospace work that began inside markitect-main. It focuses on concrete infospaces and their lifecycle, while lower-level markdown tooling and runtime orchestration remain in sibling projects.

Start with:

  • INTENT.md
  • wiki/ProductRequirementsDocument.md
  • wiki/FunctionalRequirementsSpecification.md
  • SCOPE.md
  • docs/infospace-layout.md
  • docs/evaluation-and-inspection.md
  • docs/reference-pilot-decision.md
  • docs/markitect-main-scope-assessment.md
  • docs/markitect-tool-adapter.md
  • docs/entity-relation-model.md
  • docs/evaluation-history-and-metrics.md
  • docs/workflow-generation-pipeline.md
  • docs/kontextual-engine-boundary.md
  • docs/orthogonal-successor-roadmap.md
  • docs/legacy-infospace-feature-inventory.md
  • docs/successor-boundary-interface-map.md
  • docs/replacement-acceptance-matrix.md
  • docs/legacy-command-parity.md
  • docs/legacy-infospace-migration-guide.md
  • docs/replacement-readiness-decision.md
  • docs/wealth-vsm-generation-pipeline.md
  • docs/generic-source-generator.md
  • docs/agentic-memory-profile-pilot.md
  • docs/lefevre-epub3-validation.md
  • infospaces/bootstrap-pilot/
  • infospaces/wealth-vsm-legacy-slice/
  • infospaces/wealth-vsm-generation-pilot/
  • infospaces/agentic-memory-profile-pilot/
  • workplans/

Current development command:

python3 -m pytest
Description
Infospace project/workbench layer to create, develop, evaluate, and inspect concrete infospaces such as books, departments, projects, domains, or research corpora.
Readme MIT-0 1.3 MiB
Languages
Python 99.9%
Makefile 0.1%