Contact
Keep people and organisations with familiar names, email addresses, phone numbers, and birthdays.
Portable collection semantics
Contracts and type packs
Contracts give applications a small, shared vocabulary without forcing every collection to use the same field names or storage format. Type packs install a contract and a friendly editable type together.
Local notes, shared meaning
A type remains the source of truth for what your Markdown records store. Its implements entries explain how compatible applications should read those fields.
- 1Your type
Uses familiar local names such as
emailorstage. - 2Field mapping
Connects local fields to a compact contract vocabulary such as
primary_emailorstatus. - 3Contract settings
Optionally describe behavior, such as which status values mean complete, using another JSON Schema.
One type can implement several contracts, and any number of applications can consume the same contract. Interchange formats such as JSContact and vCard belong in import and export adapters unless a collection intentionally stores that wire format.
Published contracts
| Contract | Version | Shared semantics | Artifact |
|---|---|---|---|
Contactmdbase.contact | 1.0.0 | A compact application-facing view of a person or organisation. | Markdown |
Record createdmdbase.record.created | 1.0.0 | Published after a record is created and derived collection state is consistent. | Markdown |
Record deletedmdbase.record.deleted | 1.0.0 | Published after a record is deleted and derived collection state is consistent. | Markdown |
Record modifiedmdbase.record.modified | 1.0.0 | Published after a record is modified and derived collection state is consistent. | Markdown |
Record renamedmdbase.record.renamed | 1.0.0 | Published after a record is renamed and derived collection state is consistent. | Markdown |
Durable action attemptmdbase.runtime.action-attempt | 1.0.0 | Durable invocation intent and outcome evidence using the shared interoperability envelope. | Markdown |
Capability grant evidencemdbase.runtime.capability-grant | 1.0.0 | A materialized authorization grant scoped independently from contract conformance. | Markdown |
Runtime checkpointmdbase.runtime.checkpoint | 1.0.0 | A durable, lease-safe workflow continuation. | Markdown |
Runtime dead lettermdbase.runtime.dead-letter | 1.0.0 | Retained event or action evidence that cannot be processed safely. | Markdown |
Runtime diagnosticmdbase.runtime.diagnostic | 1.0.0 | A machine-readable durable runtime diagnostic. | Markdown |
Runtime policymdbase.runtime.policy | 1.0.0 | Local authorization, executor, limit, and provider-selection policy. | Markdown |
Provider registration evidencemdbase.runtime.provider-registration | 1.0.0 | An optional audit snapshot of a verified interoperability declaration; it never activates code. | Markdown |
Cancel durable runtime runmdbase.runtime.run.cancel | 1.0.0 | Request cooperative cancellation of one durable runtime run. | Markdown |
Durable runmdbase.runtime.run | 1.0.0 | The durable state and immutable admitted plan for one workflow execution. | Markdown |
Runtime timer firedmdbase.runtime.timer.fired | 1.0.0 | Published with scheduling evidence and opaque application data when the current generation of a durable timer fires. | Markdown |
Runtime timermdbase.runtime.timer | 1.0.0 | A generation-safe one-shot timer that publishes through the interoperability profile. | Markdown |
Durable workflowmdbase.runtime.workflow | 1.0.0 | A portable workflow whose event and action references are resolved and pinned at admission. | Markdown |
Ready-made types
Add these from Types → Add a type in mdbase-editor. Each pack creates a local, editable type with its portable contract and initial field mapping. You can rename fields later; the editor keeps the mapping visible and aligned.
1 type
Developer and infrastructure packsFor integrations and specialised setups1
Runtime standard library
Internal records and contracts for durable workflows, runs, timers, and diagnostics.
Most collections do not need this pack. Install it only when a runtime integration asks you to.
Published versions are immutable.
Catalog discovery may move forward, but an installation always selects one exact pack version and verifies every embedded resource digest before changing the collection.