Advanced Settings Atlas

Use these pages after the first JSON file works. They explain which knob changes source discovery, schema contracts, runtime persistence, exposed routes, operation refs, mock behavior, and generated artifacts.

db.config.js
stores.default = "json"
resources.orders.store = "appDb"
server.expose.rest = "registered-only"
operations.acceptRefs = "ref"

Layer	What it controls
source	Where data files and schema files live.
runtime	Where writes and hydrated state land.
public API	Which routes clients may call.

Decision map

Question	Default	Advanced setting	Page
Where do data files live?	`./db`	`dbDir`, `sourceDir`	Configuration
When should schema drift fail?	`warn`	`schema.unknownFields`	Schema contracts
Where do writes land?	`.db/state`	`stores`, `resources.*.store`	Runtime stores
Which routes are public?	open local dev	`server.expose`	Server routes
How do clients call stable contracts?	raw REST	`operations`, refs	Operations
How realistic should local responses feel?	30–100ms	`mock.delay`, `mock.errors`	Mocking
What belongs in git?	ignore `.db`	`outputs.*`	Generated files

Advanced pages

**Configuration** — Use config when defaults stop matching the project shape.
**Schema contracts** — Know what inference can prove and when explicit schema should take over.
**Runtime stores** — Keep JSON where it fits and move only the resource that outgrows it.
**Server routes** — Separate local data explorer routes from app-facing data routes.
**Registered operations** — Expose reviewed callable refs instead of raw resource exploration.
**Mocking** — Make loading, retry, and empty states visible while staying local.
**Generated files** — Keep .db/ out of git, then deliberately commit generated types, manifests, or operation refs only when the app imports them.