kelly-local-model-lablisted

# Kelly Local Model Lab Use Busabase as the durable data and control plane while a trusted local Worker performs compute on Apple Silicon. Fine-tuning changes behavior; it is not a replacement for RAG when the goal is to inject current knowledge. ## Mandatory Dependencies Before creating, provisioning, or changing the AirApp, read and follow: 1. `$kelly-app-skill-creator` for product behavior and UI quality; 2. `$busabase` for Space selection, node discovery, ChangeRequests, and trusted writes; 3. `$busabase-app-creator` for AirApp runtime, SDK, security, validation, and deployment; 4. `$kelly-app-skill-creator-tests` before claiming full conformance. If a dependency is unavailable, keep the canonical local artifact and training pipeline intact, stop before the unavailable Busabase operation, and report the missing dependency. Never replace Busabase with SQLite, local JSON, or another persistent workflow backend. ## Operating Boundary - The AirApp reviews examples, runs, evaluations, and registered adapters. It never launches MLX, reads local model files, or performs training itself. - A trusted local Agent/Worker claims one eligible `training-runs` record, downloads its immutable Drive snapshot, trains locally, writes heartbeats, uploads the adapter and report, and then marks the run terminal. - Busabase Base records hold structured state and provenance. Drive/File holds dataset snapshots, adapters, reports, and model cards. Vault holds only named credential