Update handoff with model studio state

This commit is contained in:
Daniel Maddern 2026-08-17 01:04:39 +07:00
parent d61751a099
commit 557764388b

View file

@ -164,3 +164,65 @@ Recommended next steps only if the user asks to continue:
3. Do not regenerate ideas unless explicitly instructed.
4. Do not rerun broad research unless explicitly requested or needed for a new judge repair.
5. Keep all token/mainnet/fundraising/user-contact/no-spend stop conditions active.
## Model Studio V0.1 Update
Commit `d61751a Add Guard model studio foundation` added the initial Model Studio domain.
Key files:
- `control_plane/model_studio/models.py`
- Canonical Django state for training projects, immutable dataset versions and recipes, checkpoints, experiments, runs, evaluation suites/runs/results, regression-bank items, failure clusters, promotion policies/decisions, overnight programs, reports, and artifacts.
- `control_plane/model_studio/services.py`
- Guard import/archaeology, dataset curation, benchmark gate, experiment contract and fingerprinting, simulated run/promotion logic, deadline reserve checks, and morning report.
- `control_plane/model_studio/profiles.py`
- `GuardModelProfile`, based on the discovered ForgeGuard layout.
- `control_plane/model_studio/backends.py`
- `FakeTrainingBackend` for tests and `SparkGuardBackend` for profile-generated remote commands only.
- Commands:
- `python manage.py modelstudio_import_guard --repository <local ForgeGuard path> --slug guard-3b`
- `python manage.py modelstudio_dataset_audit --project guard-3b`
- `python manage.py modelstudio_overnight --project guard-3b --dry-run`
- Minimal UI:
- `/model-studio/`
Guard was imported locally for archaeology from:
- `S:\PycharmProjects\Me3\tools\ForgeGuard`
Current Guard project state in Artifex DB:
- Training project slug: `guard-3b`
- Current base-model Champion candidate: `Qwen/Qwen2.5-Coder-3B-Instruct`
- Selection: explicitly human-mandated starting Champion
- Evidence status: `PENDING_FRESH_SPARK_BASELINE`
- Training project status: `NEEDS_REPAIR`
- Benchmark integrity: `WARNING`, not valid
- Spark checkout is not registered or verified
- Fresh baseline is missing
No local Guard training/evaluation was run. The local machine is unsuitable and the user explicitly required Spark-only execution.
Spark connectivity is confirmed (`ssh spark hostname` returned `Inceptal`), but read-only inspection found no `ForgeGuard` directory under `/workspace`, `/home`, or `/opt`. Do not run training until a Spark ForgeGuard checkout path is provided or explicitly synced, then register it with `--spark-working-directory` and verify it.
Dataset curation result:
- `79` imported JSON artifacts
- `49` blocked
- `30` warning-only
- `0` approved training datasets
- Decision: `NO_TRAINING_DATASET_APPROVED`
Important curation facts:
- Summary JSON files are non-training artifacts.
- Candidate/provisional corpora are blocked.
- `full_source_c4_guard_candidate_v12` is explicitly candidate-only and has not been trained.
- The Qwen 3B verified pilot has 88 records and a claimed EVMBench exclusion, but stays `WARNING` pending record-level provenance/schema/coverage and contamination verification.
- No Spark baseline/canary/overnight program is permitted yet.
Latest verification after Model Studio work:
- `python manage.py check`: passed
- `python -m pytest -p no:django -q tests/test_model_studio_v01.py`: `6 passed`
- Full suite: `163 passed, 1 skipped`