sergio-sisternes-epam OKF — Open Knowledge Format (Pure Standard)
Format authority and hard validator for portable Open Knowledge Format (OKF) v0.2 bundles.
This skill knows nothing about live knowledge-store operations, ingestion, or knowledge processes. Those belong to Atlas (github.com/sergio-sisternes-epam/okf-atlas).
Activation card (on): Before any substantial path work, emit the standard Enter card (skill, skill_path, mode, subject, path, path_module, intent) and a matching path receipt at Exit. See autogenesis workflow-discipline for the canonical schema.
Contained modules
| Module | Purpose |
|---|---|
| okf-authority | Normative rules, frontmatter, reserved files, conformance |
| okf-export | Produce a portable OKF bundle (called by Atlas or directly) |
| okf-import | Materialise an external OKF bundle (called by Atlas or directly) |
Core normative rules (always apply)
- Every non-reserved
.mdfile must contain parseable YAML frontmatter. - Frontmatter must contain a non-empty
typefield. - Reserved filenames at any level:
index.md,log.md(must not be used as concept files). - Directory structure is free; producers organise concepts as they see fit.
- Consumers must tolerate unknown
typevalues and unknown frontmatter keys. - Prefer update-over-create; never strip unknown frontmatter keys on import.
- Links should be resolvable inside the target environment after import/export.
How to route
- Pure format / compliance / validation questions → load the
okf-authoritymodule (see substrate contract below). - Explicit request to export or import a portable bundle → load the matching module (still apply authority rules via the same contract).
- Any request about live ingest, query, expand, lint of the knowledge store → Atlas:
atlas mount github.com/sergio-sisternes-epam/okf-atlas(compile/query root.../okf-atlas/atlas).
Substrate contract (mandatory for every skill or module load)
When this body must invoke / load / execute another skill (or one of its progressive modules):
- Locate the target skill by name from the harness’s available skills list (do not hard-code absolute paths).
- Load the full body of that skill’s entrypoint (
SKILL.md) using the harness’s on-demand skill-loader tool. Never rely on the short frontmatter description alone. - Follow the loaded body instructions exactly.
- Re-execute any live tool calls the body requires.
For internal progressive-disclosure modules under references/modules/, locate the parent skill first, then read_file the module path relative to that skill root (or follow the loaded parent body’s own progressive-disclosure instructions).
Relationship to Atlas
okfis the pure standard and validator.- Process memory lives in
sergio-sisternes-epam/okf-atlas, not this repo. - Atlas OKF root is the
atlas/folder (atlas/SCHEMA.json), not the git root. - Mount:
atlas mount github.com/sergio-sisternes-epam/okf-atlas - Compile and query from
.../okf-atlas/atlas. - Do not use
okf-wikifor new process memory. - This skill does not depend on Atlas.
Progressive disclosure
Detailed procedures live in references/modules/. Load only what the current request needs.