Give every agent the same starting point.
Schema alone cannot explain why a database exists, which sources are authoritative, or how an agent should update it. OnDemandDB stores that operating context beside the database—versioned, explicit, and portable.
DATABASE.mdentrypoint
docs/identity.mdsupporting document
docs/sources.mdsupporting document
skills/reconcile/SKILL.mdportable skill
A deliberate retrieval model
Context is available, never silently injected.
- Agents request the bundle or named files through MCP, REST, SDK, or CLI.
- ETags prevent one author from overwriting another revision.
- Manifests record paths, sizes, and SHA-256 hashes.
- Provenance distinguishes the starter template from customer-authored context.
- Markdown is treated as untrusted account content—not executable policy.
Explain the data
Record purpose, entities, naming conventions, and the questions this database should answer.
Carry the workflow
Keep source rules and small, portable skills with the state they operate on.
Review every change
Read history, pull a directory, edit it locally, and publish against the ETag you inspected.
Connect once. Ask for context when it matters.
The hosted MCP catalog exposes explicit context reads and writes beside SQL.