Skip to content

Latest commit

 

History

History
50 lines (42 loc) · 5.37 KB

README.md

File metadata and controls

50 lines (42 loc) · 5.37 KB

Code map

Start with the user action below, follow its production owner, then read one representative scenario. This map locates current code and contracts; requirements belong in specifications, implementation detail beside the code, and validation results in the relevant run record.

Read progressively

  1. Find the capability below, or search with rg -n -i '<user action, symptom or domain term>' docs/code-map/.
  2. Once the relevant topic is located, prefer reading its complete code-map page, including ownership boundaries and cross-references. The search match locates the page; its surrounding context helps interpret the entry.
  3. Follow the production owner and a representative scenario, then expand into linked code, specifications or local guides as needed. Unrelated map pages need not be read by default.

Find a capability

User action Start here Representative scenario
Add model sources and inspect usable models Source admission and native configuration, Application owners Installed CLI management loop
Create, edit and publish a routing plan Authoring/lifecycle, compiler, domain Publication and restart
Connect a decision model or custom extension; configure smart saving or custom branches Decision and routing map Real CLI connection lifecycle, listener multi-turn routing
Configure, adjust or disable an Agent's models and task collaboration Agent/Worker map, Desktop feature guide Settings ordering, saved native model journey
Route an authenticated model request and apply bounded fallback Gateway map, execution core Real listener scenarios
Delegate, read, cancel or continue a Worker task Worker lifecycle and native differences Delegation, read/Continue
Inspect sessions, content, cost and competence Observation owners, decision attribution Session queries, stage summaries
Manage the service through CLI or Desktop client-core, CLI, Desktop host, daemon control Real control process, Desktop test map
Upgrade Desktop and recover a failed installation Updater, installer handshake, resident restart Preflight → orderly stop → explicit commit; macOS installation and recovery
Build macOS / Linux release installers for either architecture Release candidate entry, build and publication guide Package-to-publication contract, Linux ABI and installed-runtime gate; final publishing remains in release.yml

Read across boundaries

Map Scope
Architecture and ownership Shared layers, source admission, durable state, observation and change boundaries
Agent integrations and Workers Shared configuration/lifecycle owners, with Codex, Claude, Qoder, Pi and DSH differences together
Decision models and routing Saved connections, provider adapters, per-turn policy and competence attribution
Tests as product documentation Proof levels, reusable fixtures, representative fault cases and validation selection

Keep new navigation organized by stable responsibility, not by a provider or a completed feature. Add an ecosystem to the shared comparison and link its native leaf. Put detailed protocol rules in their canonical contract and operating steps in the existing local guide. When an owner moves, update its entry and incoming links instead of appending another implementation note to this index. Keep each matched entry a short clue about where to look next and why. Detailed rules, parameter lists, exhaustive exceptions and validation history belong in the linked specification, local guide or run record.