Repository map¶
Path |
Purpose |
|---|---|
|
Typed models, ledgers, sandbox, orchestration, providers, CLI, local web UI, and optional TUI |
|
Versioned model-readable interfaces and scientific practice |
|
Harness-owned executable runtime manifests; optional solver binaries remain local and untracked |
|
Release-pinned operator provisioning specifications |
|
Public, committed JSON Schemas |
|
Recorded autonomous runs, compact audit records, and reproduction inputs |
|
Deployment, qualification, audit, and maintenance utilities |
|
Deterministic, integration, replay, and scientific regression tests |
|
Curated documentation |
Local runtimes, provider credentials, mutable ledgers, and bulk raw campaign artifacts are ignored by Git. A small release demo may commit a curated portable record. Large scientific campaigns should publish compact audit records in the repository and deposit complete immutable artifacts in a DOI-bearing data archive.