1. Starter Schema
A minimal working schema for a new vault.
Copy this into your schema note under # Contract and adjust to fit your vault's note types and tags.
frontmatter:
required:
- name: type
type: enum
severity: error
values:
- concept
- reference
- project
- note
- name: status
type: enum
severity: error
values:
- draft
- active
- complete
- archived
- name: tags
type: list
severity: error
min_items: 1
- name: created
type: date
severity: error
format: "yyyy-MM-dd"
strict_parse: true
- name: updated
type: date
severity: warning
format: "yyyy-MM-dd"
strict_parse: true
- name: review_cycle
type: enum
severity: error
values:
- weekly
- monthly
- quarterly
- yearly
- never
values_meta:
weekly: { days: 7 }
monthly: { days: 30 }
quarterly: { days: 90 }
yearly: { days: 365 }
never: { days: null }
optional:
- name: related_domains
type: list
severity: warning
inline:
allowed:
- name: source
- name: version
ontology:
relationships:
informs:
description: "Shapes understanding, interpretation, or reasoning."
direction: flexible
allowed_between:
- concept
- reference
- note
template_heading: Informs
tag_rules:
require_namespace: true
unknown_tags: warning
severity: warning
allowed_namespaces:
- topic
- tool
forbidden_namespaces:
- type
- status
exempt_paths: []
Once you have this in place, run Forge: Validate Schema to confirm it parses correctly, then run Vault Lint to see your first results.
Expand the schema gradually as your vault grows — add types, relationships, inline fields, and tag namespaces as they become useful rather than upfront.
