Different apps can use the same Markdown files, online or offline.

Here is one small mdbase.

This project collection has ordinary Markdown records, definitions for the kinds of records it contains, and one configuration file.

projects/
├── mdbase.yaml
├── _types/
│   ├── project.md
│   └── person.md
├── projects/
│   └── website-redesign.md
└── people/
    └── sam.md

Each record remains useful on its own. The extra files let an app recognise a project, understand fields such as status and owner, and check that a change is valid.

• Project appUpdates status and owner through typed operations
• Report appReads the same projects for a weekly summary
• Text editorOpens the exact Markdown records directly

The files make sense to people and apps.

A project record is still a normal Markdown document. A short block at the top gives apps the facts they need; the rest is writing you can read and edit anywhere.

---
type: project
title: Website redesign
status: active
owner: "[[people/sam.md]]"
---

The new site should make mdbase
easier to understand.

The type definition stored in the same collection explains these fields. A new app can check that it understands them before asking you for access.

Keep it local or host it with mdbase.

Hosting is optional. In both cases the records remain Markdown, apps use the same basic actions, and you decide which apps can connect.

The difference is which copy has the final say. For a local mdbase, that is the folder on your computer. For a hosted mdbase, it is the online copy kept by mdbase.

• LocalYour folder is the main copy; your computer must be reachable
• Hostedmdbase keeps the main copy available online
• Either wayYou keep readable files and explicit app permissions

An app asks before it sees anything.

The request names the app, the kind of collection it understands, and every action it wants to perform. Your records stay private while you decide.

You choose one compatible collection and approve only the actions that make sense. Permission belongs to that app and that collection; it can be narrowed, paused, or revoked later.

1. 1Review the app and the collection it understands
2. 2Choose a collection and its allowed actions
3. 3Approve the connection or keep the collection private

• ReadOpen records and see their contents
• SearchFind matching records
• EditCreate, update, rename, or delete records

The main copy stays in control.

For a local collection, the mdbase connector on your computer checks every request before opening or changing a file. Local folder paths stay on your computer.

For a hosted collection, mdbase checks the same permission beside the online main copy. An approved app may keep an offline copy of records it can use, and you may keep an optional synced Markdown copy for local tools.

• Main copyOne authoritative history keeps changes in order
• Working copiesUseful for offline and local work
• Your controlPause or revoke an app's access at any time