Skip to content
Merged
388 changes: 133 additions & 255 deletions README.md

Large diffs are not rendered by default.

23 changes: 10 additions & 13 deletions docs/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,10 +44,9 @@ and [TTS service protocol](tts-benchmark.md) expose their documented execution
boundaries. Apps and Harness callers assemble these operations into optimization
rounds under the #362 target architecture. Each task records its qualification.

The local experiment path now has concrete Harness, Model and Infra modules. The
CLI, RunSpec, knowledge retrieval and existing command contracts remain stable.
The diagrams below describe implemented code, with the historical compatibility
boundary called out separately.
The diagrams below show where the CLI assembles an experiment, which package
owns each step and where to extend it. The [compatibility notes](#compatibility-and-historical-evidence)
cover retained interfaces and imports that moved.

## Three-objective delivery framing

Expand Down Expand Up @@ -114,12 +113,9 @@ repository-pack description through the neutral `resources.repository_packs`
leaf, under the one permanent importer rule in
[module-layout.md](module-layout.md#permanent-neutral-leaf-importer-rule-proposed).

The implemented table above is not the target four-module layout. The
suggested rule, including what the import gate does not prove, is
[module-layout.md](module-layout.md). That page does not move code. It also
records the first-wave compatibility pairs that #412 R1 retired and the
permanent neutral-leaf importer rule, both held in
[legacy-knowledge-manifest.json](legacy-knowledge-manifest.json).
The [target module layout](module-layout.md) describes the migration and the
scope of the static import checks. The [migration manifest](legacy-knowledge-manifest.json)
records the retired compatibility pairs and the permanent neutral-leaf importer rule.

The caller still prepares the benchmark runtime and baseline/candidate source
checkouts. Separate working directories alone do not isolate Python imports,
Expand Down Expand Up @@ -309,15 +305,16 @@ forwarding shell or alias: the seven Knowledge shells, whose code is in
`reporting.py`, whose code is in `apps/legacy/`; and `inspection.py`, whose
host binding is `apps/inspection.py`. The build-generated `_version.py` is ignored
wheel metadata, not a tracked root file.
[module-layout.md](module-layout.md#retired-root-modules) maps each retired
path to its replacement and lists what still keeps the isolation gate false.
The [migration list](module-layout.md#retired-root-modules) maps each retired
path to its replacement. The [import gate](module-layout.md#import-gate) defines
the dependency checks.

## Where to extend

| Add | Main extension locations | Required qualification |
| --- | --- | --- |
| Model or scenario | `harness/serving`, `benchmark/metrics.py`, `benchmark/validators`, `harness/scenarios` | Frozen request and metric contract; model-specific quality coverage |
| Repository | `apps/host/targets`, a composed scenario, `data/repo_packs` | Stable source identity; command/result contract; environment isolation |
| Repository | `apps/host/targets`, a composed scenario, `harness/data/repo_packs` | Stable source identity; command/result contract; environment isolation |
| Hardware | `apps/host/platforms` | Device selection, process exclusivity and independent backend/model evidence; a backend is registered in `apps/host/platforms/__init__.py` and its probe command is defined in the implementing module under `apps/host/platforms/`, not in package data |

The acceptance rule is: **a new model or hardware adapter must reuse the common
Expand Down
98 changes: 65 additions & 33 deletions docs/assets/inferrsi-banner.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Loading