Core public surface
Public messaging, source-checkout smoke, manifest-backed dataset counts, model-fallback registry, active Kaggle kernels, generated page sources, and package-test collection pass without a model or network call.
DueCare is in a time-boxed maintainer transition through 2026-08-25. Core code, public documentation, active Kaggle surfaces, and published dataset claims have a green model-free release gate. New model spending and a new training-improvement claim remain deliberately paused until their separate evidence gates are ready.
A green core gate means the public repository is coherent at the checked revision. It does not silently turn an unfinished dataset, adapter, or experimental judge lane into a completed scientific claim.
Public messaging, source-checkout smoke, manifest-backed dataset counts, model-fallback registry, active Kaggle kernels, generated page sources, and package-test collection pass without a model or network call.
Existing results retain their original model, prompt set, rubric, judge, and date. They are benchmark response-quality evidence, not field-effectiveness, victim-identification, or production-reliability claims.
The autonomous engine remains stopped behind its sentinel. Closeout uses a zero planned-call guard; restarting Ollama or a hosted provider requires a new frozen budget, preflight, and explicit authorization.
The website and documentation are related but intentionally deployed by different systems. This prevents one workflow from overwriting the other.
The FastAPI hub in apps/duecare-ai.com deploys from master on Render. It serves product pages, public coordination APIs, sanitized proposal intake, and health endpoints. It does not load Gemma.
The MkDocs site deploys from docs/ through docs-deploy.yml after changes reach master. It owns the repository's single GitHub Pages site.
duecare-site-build.yml exports the website as a downloadable artifact for a separate root-domain host. It never deploys into the MkDocs Pages environment.
Saved handoff artifacts and ignored reports are historical evidence. A maintainer establishes current truth from Git, live process/engine status, and read-only validators before changing or publishing anything.
git status --short $env:DUECARE_MAX_PLANNED_MODEL_CALLS='0' python scripts/validate_publication_readiness.py --scope handoff python scripts/validate_publication_readiness.py --scope core python scripts/autonomous_engine.py --status
master.