Fix:
Validator
Validate an OKF bundle
Paste Markdown, upload individual .md files, or select a folder. The validator checks OKF v0.1 concept-file rules and reports guidance for recommended metadata, timestamps, tags, and links.
Input
Validate Markdown.
Coverage
Checks parseable frontmatter, required concept types, recommended metadata, timestamps, tags, filenames, and internal Markdown links.
Request failed
Validation could not run.
Validation report
Markdown files scanned
Concept files checked
Total issues found
Blocking
Errors
No blocking errors found.
The scanned concept files satisfy the required OKF checks.
Quality
Warnings
No warnings found.
The scanned files include the recommended metadata and link hygiene checks.
Improve:
Validation result
A report will appear here.
Upload an OKF folder or paste one Markdown concept file. The report will separate blocking errors from metadata, filename, timestamp, and link warnings.
Version coverage
What the OKF v0.1 validator checks.
The validator separates required concept-file rules from metadata guidance so teams can fix blocking issues first and improve bundle quality next.
Required checks
- Concept files must contain parseable YAML frontmatter.
- Frontmatter must be an object/map of keys and values.
- Every non-reserved concept file needs a non-empty
type.
Guidance checks
- Recommended metadata includes title, description, resource, tags, and timestamp.
- Tags should be an array for predictable filtering.
- File-relative and bundle-root Markdown links are checked for missing targets.
Permissive behavior
- Reserved files follow their index or dated-log body structures without concept frontmatter.
- The root
index.mdmay declare optionalokf_versionfrontmatter. - Unknown fields and extension keys are allowed.
- Non-Markdown files are ignored during validation.
Next step
