# mindspring ADF Manifest
load core.adf always
📂 ON_DEMAND:
- backend.adf (Triggers on: backend)
- core.adf (Triggers on: core)
- frontend.adf (Triggers on: frontend)
- state.adf (Triggers on: state)
ADF: 0.1
🎯 ROLE: MindSpring context router
📦 DEFAULT_LOAD:
- core.adf
- state.adf
📂 ON_DEMAND:
- backend.adf (Triggers on: backend, api, hono, worker, queue, vectorize, kv, r2, upload, ingestion, telemetry)
- frontend.adf (Triggers on: frontend, ui, css, vanilla js, app.js, styles, spa)
Summary
Running
npx @stackbilt/cli bootstrap --yesin an existing repo produced a manifest that looked valid to a human but parsed as0 default-load, causingverify:adfto fail in CI mode until the manifest was manually rewritten.Environment
Stackbilt-dev/mindspring@stackbilt/cli@0.12.1.ai/core.adf+ customCLAUDE.md)Repro
.ai/core.adfand.ai/manifest.adf, run:npx @stackbilt/cli bootstrap --yesnpm run verify:adfObserved
charter doctor --adf-only --ci --format jsonthen reports:Parsed: 0 default-loadMissing from DEFAULT_LOAD: core.adf, state.adfExpected
DEFAULT_LOAD: [core.adf, state.adf]ON_DEMANDexcludingcore.adf/state.adfunless explicitly intended.verify:adfshould pass immediately after bootstrap for the generated files.Workaround used
Manually replaced manifest with canonical ADF section format:
After this, both passed:
npm run charter:doctornpm run verify:adfPossible fix directions
ADF: 0.1manifest structure.core.adfexists.core.adf/state.adfas ON_DEMAND when required default wiring is expected.