Beautiful, AI-native markdown IDE and LLM wiki
TypeScript 2nd-brainagent-skillsclaudecodexcompany-braindocsknowledge-knowledge-baseknowledge-managementllmllm-wikillm-wiki-karpathymarkdownmarkdown-editormdmdxnotespkmsecond-brainskills
fix(ok): accept OKF v0.2 datetimes in okf provenance lint (PRD-8435) (#3960)
serafin-garcia9104ce4119e0
diff --git a/.changeset/okf-datetime-formats.md b/.changeset/okf-datetime-formats.mdnew file mode 100644index 000000000..921906a9e--- /dev/null+++ b/.changeset/okf-datetime-formats.md@@ -0,0 +1,16 @@+---+"@inkeep/open-knowledge": patch+---++OKF provenance timestamps are now read as ISO 8601 datetimes carrying an explicit UTC offset, which is what OKF v0.2 §5 asks for. This changes the `okf` lint plugin in both directions, and one of the two is a tightening.++- **Documents that already follow OKF v0.2 stop warning.** `stale_after`, `usage_window.from`, `usage_window.to`, and each `sources[]` entry's `last_modified` plus its own window bounds previously accepted only a bare `YYYY-MM-DD` calendar date, so a conformant value such as `2026-09-23T00:00:00Z` was reported as a `frontmatter-provenance` warning. It no longer is.+- **Documents still written with date-only values start warning.** A value such as `stale_after: 2026-09-23` now reports one `frontmatter-provenance` warning, because the format now asks for an explicit offset. The remedy is to write it: `stale_after: 2026-09-23T00:00:00Z`. A datetime carrying no offset (`2026-09-23T00:00:00`) is rejected for the same reason, and the warning now names the shape to write rather than only the schema keyword.++**Why now.** OKF revised §5 in place on 2026-08-21, adding "Every timestamp-valued key in OKF is an ISO 8601 datetime with an explicit UTC offset" and migrating every example in the spec, without bumping the version. Both revisions are labeled v0.2 and a document written to either declares `okf_version: "0.2"`, so the declared version does not tell you which reading a document was authored against. The plugin now records the upstream commit its reading is pinned to.++**Other v0.2 checkers have not caught up yet.** `okf-conformance` still warns on a `stale_after` that is not a bare `YYYY-MM-DD`, which is the pre-revision wording of §5.5, so the two tools currently disagree about the same document. OpenKnowledge follows the current spec text and the format's own reference bundles, which now write `stale_after: 2026-12-31T00:00:00Z`.++Log files are unaffected. OKF §9 governs the date's form in a `log.md` entry heading, not these frontmatter keys, and `log-shape` is unchanged: `## 2026-06-30` and `## 2026-06-30: Shipped v2` both stay conformant.++The `okf` plugin ships disabled by default, so this reaches only projects that turned it on, and it emits advisory warnings rather than blocking anything.diff --git a/docs/content/plugins/okf.mdx b/docs/content/plugins/okf.mdxindex 6e95926a8..10a2ad66e 100644--- a/docs/content/plugins/okf.mdx+++ b/docs/content/plugins/okf.mdx@@ -4,7 +4,7 @@ icon: LuGlobedescription: Keep a project portable to Google's Open Knowledge Format with advisory rules, agent-readable schemas, an optional index generator, and a companion skill.----The **OKF** project plugin checks whether a knowledge base stays portable to [Google's Open Knowledge Format](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md) v0.2. Findings are advisory warnings and never block a save or an agent edit.+The **OKF** project plugin checks whether a knowledge base stays portable to [Google's Open Knowledge Format](https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/main/SPEC.md) v0.2. Findings are advisory warnings and never block a save or an agent edit.<Callout>**Beta.** Off until a project enables it. The [Open Knowledge Format starter pack](/docs/workflows/supporting-open-knowledge-format) enables it while creating an OKF-ready bundle.@@ -44,7 +44,7 @@ Every rule is on while the plugin is enabled unless you switch it off. Findings| Document structure | `reserved-casing` | Flags reserved `Index.md` or `Log.md` filenames that are not lowercase || Frontmatter | `frontmatter-required` | Requires a non-empty `type` on every non-reserved document || Frontmatter | `frontmatter-recommended` | Validates the shape of optional `title`, `description`, `resource`, and `tags` fields |-| Frontmatter | `frontmatter-provenance` | Validates optional `sources`, `generated`, `verified`, `status`, and `stale_after` metadata |+| Frontmatter | `frontmatter-provenance` | Validates optional `sources`, `usage_window`, `generated`, `verified`, `status`, and `stale_after` metadata, including the [timestamp shape](#provenance-timestamps) || Frontmatter | `frontmatter-computation` | Requires `runtime` on documents typed `Attested Computation` || Frontmatter | `frontmatter-reserved-index` | Disallows frontmatter on `index.md`, except at the bundle root || Frontmatter | `frontmatter-root-index` | Checks the bundle root's quoted `okf_version` value |@@ -52,6 +52,16 @@ Every rule is on while the plugin is enabled unless you switch it off. FindingsReserved filenames match exactly and case-sensitively: `5-index.md` and `notes-log.md` are ordinary documents that need a `type`, and `reserved-casing` catches `Index.md` and `Log.md`.+### Provenance timestamps++Every timestamp-valued provenance key is an ISO 8601 datetime carrying an explicit UTC offset, not a calendar date: `stale_after: 2026-12-31T00:00:00Z`. That covers `generated.at`, each `verified[].at`, `stale_after`, each `sources[].last_modified`, and both bounds of a `usage_window`, whether the window is written beside `sources` or inside one entry.++A datetime with no offset (`2026-12-31T00:00:00`) is flagged too, so adding a time is not enough on its own.++Other OKF consumers may not agree yet. Upstream revised this part of the spec in place under the same v0.2 label, so a checker pinned to the earlier reading still expects a bare `YYYY-MM-DD` for `stale_after` and will flag a document written to the rule above. The declared `okf_version` is `0.2` under both readings, so it cannot tell them apart. Check the consumer you are targeting before treating either spelling as portable.++Log entry headings are the exception, and they are governed by a different rule: `log.md` uses plain `YYYY-MM-DD`, checked by `log-shape`.+### Where rules run| Rules | Surfaces |diff --git a/docs/content/workflows/supporting-open-knowledge-format.mdx b/docs/content/workflows/supporting-open-knowledge-format.mdxindex 222a2f691..3677ed6f7 100644--- a/docs/content/workflows/supporting-open-knowledge-format.mdx+++ b/docs/content/workflows/supporting-open-knowledge-format.mdx@@ -10,7 +10,7 @@ The **Open Knowledge Format (OKF)** is a portable convention for agent-readableOpenKnowledge's **Open Knowledge Format** starter pack creates the minimum useful OKF v0.2 bundle. It also enables the [OKF plugin](/docs/plugins/okf), which warns when later edits would be misread by another OKF consumer.<Callout type="info">- **OKF here means Google's Open Knowledge _Format_.** The format keeps its conformance floor deliberately small: every non-reserved document needs parseable YAML frontmatter with a non-empty `type`. Read the [OKF v0.2 specification](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md).+ **OKF here means Google's Open Knowledge _Format_.** The format keeps its conformance floor deliberately small: every non-reserved document needs parseable YAML frontmatter with a non-empty `type`. Read the [OKF v0.2 specification](https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/main/SPEC.md).</Callout>## Start with the OKF pack@@ -72,4 +72,4 @@ The plugin checks the resulting shape. The skill guides the content decision.- **[OKF plugin](/docs/plugins/okf).** Enable the plugin, install its recommended skill, tune rules, and opt into generated indexes.- **[Content rules overview](/docs/advanced/content-rules/overview).** Where warnings appear in the editor, CLI, and agent tools.-- **[Open Knowledge Format v0.2 specification](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md).** The portable format OpenKnowledge implements.+- **[Open Knowledge Format v0.2 specification](https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/main/SPEC.md).** The portable format OpenKnowledge implements.diff --git a/packages/core/src/markdown/lint/frontmatter-validate.ts b/packages/core/src/markdown/lint/frontmatter-validate.tsindex 5f953d667..1943ac84f 100644--- a/packages/core/src/markdown/lint/frontmatter-validate.ts+++ b/packages/core/src/markdown/lint/frontmatter-validate.ts@@ -194,6 +194,16 @@ function parseFrontmatterData(text: string): {return { data: data as Record<string, unknown>, keyLines };}+const FORMAT_HINTS: Record<string, string> = {+ 'date-time':+ 'an ISO 8601 datetime with an explicit UTC offset, for example "2026-09-23T00:00:00Z"',+};++function formatHint(params: unknown): string | undefined {+ const name = (params as { format?: unknown }).format;+ return typeof name === 'string' ? FORMAT_HINTS[name] : undefined;+}+function describeActual(value: unknown): string {if (value === undefined) return '';let rendered: string;@@ -267,10 +277,13 @@ export function validateFrontmatterSource(line = keyLines.get(anchorKey) ?? 0;}const path = pointerToDotPath(error.instancePath);+ const actual = anchorKey !== null && path === anchorKey ? data[anchorKey] : undefined;if (keyword === 'enum') {const allowed = (error.params as { allowedValues?: unknown[] }).allowedValues ?? [];- const actual = anchorKey !== null && path === anchorKey ? data[anchorKey] : undefined;message = `Frontmatter property "${path}" must be one of: ${allowed.map(String).join(', ')}${describeActual(actual)}`;+ } else if (keyword === 'format' && formatHint(error.params) !== undefined) {+ const name = (error.params as { format?: unknown }).format;+ message = `Frontmatter property "${path}" must be ${formatHint(error.params)} (format "${String(name)}")${describeActual(actual)}`;} else {message = `Frontmatter property "${path}" ${error.message ?? `violates "${keyword}"`}`;}diff --git a/packages/core/src/markdown/lint/okf-frontmatter/schemas.ts b/packages/core/src/markdown/lint/okf-frontmatter/schemas.tsindex f1c37671b..ed9e2efcf 100644--- a/packages/core/src/markdown/lint/okf-frontmatter/schemas.ts+++ b/packages/core/src/markdown/lint/okf-frontmatter/schemas.ts@@ -5,7 +5,7 @@ export const OKF_REQUIRED_SCHEMA: Record<string, unknown> = {$schema: 'http://json-schema.org/draft-07/schema#',title: 'OKF v0.2 — required frontmatter',description:- 'The OKF v0.2 conformance floor. A bundle is conformant when every non-reserved .md file contains a parseable YAML frontmatter block whose `type` is non-empty. This schema is the whole of that floor: a concept carrying only `type` is fully conformant. Section numbers cite OKF v0.2: https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md#11-conformance',+ 'The OKF v0.2 conformance floor. A bundle is conformant when every non-reserved .md file contains a parseable YAML frontmatter block whose `type` is non-empty. This schema is the whole of that floor: a concept carrying only `type` is fully conformant. Section numbers cite OKF v0.2: https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/ad30107c31c06aec8a7d5636e0d1058118604e6f/SPEC.md#11-conformance',type: 'object',required: ['type'],properties: {@@ -22,7 +22,7 @@ export const OKF_RECOMMENDED_SCHEMA: Record<string, unknown> = {$schema: 'http://json-schema.org/draft-07/schema#',title: 'OKF v0.2 — recommended frontmatter',description:- 'Shapes for the OKF v0.2 recommended keys. Every key here is optional, and nothing is constrained beyond the shape OKF states: declaring a key pins its YAML type when present (so `tags` written as a comma-separated string warns) and advertises it to agents at read time. Section numbers cite OKF v0.2: https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md#41-frontmatter',+ 'Shapes for the OKF v0.2 recommended keys. Every key here is optional, and nothing is constrained beyond the shape OKF states: declaring a key pins its YAML type when present (so `tags` written as a comma-separated string warns) and advertises it to agents at read time. Section numbers cite OKF v0.2: https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/ad30107c31c06aec8a7d5636e0d1058118604e6f/SPEC.md#41-frontmatter',type: 'object',properties: {title: {@@ -60,7 +60,7 @@ export const OKF_PROVENANCE_SCHEMA: Record<string, unknown> = {$schema: 'http://json-schema.org/draft-07/schema#',title: 'OKF v0.2 — provenance, trust, and lifecycle frontmatter',description:- 'The optional OKF v0.2 families that make "where did this come from", "how much should I trust it", and "is it still current" answerable from frontmatter alone. Every key is optional, and absence carries meaning rather than being an error: a concept with no `verified` is unverified, and a consumer must not reject it. Only `sources[].resource` and `generated.by` are required-when-their-parent-is-present, because those are the two fields OKF marks REQUIRED in this family; every other field is described but not mandated, so nothing else is enforced. Section numbers cite OKF v0.2: https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md#5-provenance-trust-and-lifecycle',+ 'The optional OKF v0.2 families that make "where did this come from", "how much should I trust it", and "is it still current" answerable from frontmatter alone. Every key is optional, and absence carries meaning rather than being an error: a concept with no `verified` is unverified, and a consumer must not reject it. Only `sources[].resource` and `generated.by` are required-when-their-parent-is-present, because those are the two fields OKF marks REQUIRED in this family; every other field is described but not mandated, so nothing else is enforced. Section numbers cite OKF v0.2: https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/ad30107c31c06aec8a7d5636e0d1058118604e6f/SPEC.md#5-provenance-trust-and-lifecycle',type: 'object',properties: {sources: {@@ -97,9 +97,9 @@ export const OKF_PROVENANCE_SCHEMA: Record<string, unknown> = {},last_modified: {type: 'string',- format: 'date',+ format: 'date-time',description:- 'Optional credibility signal — a recency signal: when the source itself last changed, as `YYYY-MM-DD`. Distinct from `generated.at`, which records when the concept was written. OKF v0.2 §5.1.',+ 'Optional credibility signal — a recency signal: when the source itself last changed, as an ISO 8601 datetime with an explicit UTC offset (`2026-06-15T00:00:00Z`). Distinct from `generated.at`, which records when the concept was written. OKF v0.2 §5, §5.1.',},usage_window: {type: 'object',@@ -108,15 +108,15 @@ export const OKF_PROVENANCE_SCHEMA: Record<string, unknown> = {properties: {from: {type: 'string',- format: 'date',+ format: 'date-time',description:- "Start of the window framing this entry's `usage_count`, as `YYYY-MM-DD`. OKF v0.2 §5.1.",+ "Start of the window framing this entry's `usage_count`, as an ISO 8601 datetime with an explicit UTC offset (`2026-06-01T00:00:00Z`). OKF v0.2 §5, §5.1.",},to: {type: 'string',- format: 'date',+ format: 'date-time',description:- "End of the window framing this entry's `usage_count`, as `YYYY-MM-DD`. OKF v0.2 §5.1.",+ "End of the window framing this entry's `usage_count`, as an ISO 8601 datetime with an explicit UTC offset (`2026-06-30T00:00:00Z`). OKF v0.2 §5, §5.1.",},},},@@ -126,17 +126,19 @@ export const OKF_PROVENANCE_SCHEMA: Record<string, unknown> = {usage_window: {type: 'object',description:- 'Written once as a sibling of `sources`, this frames every `usage_count` in the list with a `{ from, to }` date range. A single entry may carry its own `usage_window` to override it. OKF v0.2 §5.1.',+ 'Written once as a sibling of `sources`, this frames every `usage_count` in the list with a `{ from, to }` range. A single entry may carry its own `usage_window` to override it. OKF v0.2 §5, §5.1.',properties: {from: {type: 'string',- format: 'date',- description: 'Start of the shared usage window, as `YYYY-MM-DD`. OKF v0.2 §5.1.',+ format: 'date-time',+ description:+ 'Start of the shared usage window, as an ISO 8601 datetime with an explicit UTC offset (`2026-06-01T00:00:00Z`). OKF v0.2 §5, §5.1.',},to: {type: 'string',- format: 'date',- description: 'End of the shared usage window, as `YYYY-MM-DD`. OKF v0.2 §5.1.',+ format: 'date-time',+ description:+ 'End of the shared usage window, as an ISO 8601 datetime with an explicit UTC offset (`2026-06-30T00:00:00Z`). OKF v0.2 §5, §5.1.',},},},@@ -155,7 +157,7 @@ export const OKF_PROVENANCE_SCHEMA: Record<string, unknown> = {type: 'string',format: 'date-time',description:- "An ISO 8601 datetime marking the content's last meaningful change. Consumers use it to tell a recent edit from a stale fact. Supersedes v0.1's top-level `timestamp`. OKF v0.2 §5.2, §13.1.",+ "An ISO 8601 datetime with an explicit UTC offset (`2026-06-30T14:00:00Z`) marking the content's last meaningful change. Consumers use it to tell a recent edit from a stale fact. Supersedes v0.1's top-level `timestamp`. OKF v0.2 §5, §5.2, §13.1.",},},},@@ -175,7 +177,8 @@ export const OKF_PROVENANCE_SCHEMA: Record<string, unknown> = {at: {type: 'string',format: 'date-time',- description: 'ISO 8601 datetime of the verification event. OKF v0.2 §5.2.',+ description:+ 'An ISO 8601 datetime with an explicit UTC offset (`2026-07-01T09:00:00Z`) recording when the verification event happened. OKF v0.2 §5, §5.2.',},},},@@ -194,7 +197,8 @@ export const OKF_PROVENANCE_SCHEMA: Record<string, unknown> = {at: {type: 'string',format: 'date-time',- description: 'ISO 8601 datetime of the verification event. OKF v0.2 §5.2.',+ description:+ 'An ISO 8601 datetime with an explicit UTC offset (`2026-07-01T09:00:00Z`) recording when the verification event happened. OKF v0.2 §5, §5.2.',},},},@@ -208,9 +212,9 @@ export const OKF_PROVENANCE_SCHEMA: Record<string, unknown> = {},stale_after: {type: 'string',- format: 'date',+ format: 'date-time',description:- 'An absolute date, `YYYY-MM-DD`: the concept is stale when `today >= stale_after`. Absolute rather than a relative TTL so staleness stays a plain date comparison with no reference to when the concept was read. A date in the past is a freshness signal for consumers, not a violation. OKF v0.2 §5.5, §10.5.',+ 'An absolute instant, an ISO 8601 datetime with an explicit UTC offset (`2026-12-31T00:00:00Z`): the concept is stale when `now >= stale_after`. Absolute rather than a relative TTL so staleness stays a plain comparison with no reference to when the concept was read. An instant in the past is a freshness signal for consumers, not a violation. OKF v0.2 §5, §5.5, §10.5.',},},};@@ -219,7 +223,7 @@ export const OKF_ATTESTED_COMPUTATION_SCHEMA: Record<string, unknown> = {$schema: 'http://json-schema.org/draft-07/schema#',title: 'OKF v0.2 — Attested Computation frontmatter',description:- 'Shapes for the OKF v0.2 computation keys, which turn a concept into a sanctioned way to compute a value so a consumer can confirm the agent ran the blessed computation instead of improvising its own. Provenance answers "where did this claim come from"; attestation answers "was this number produced the way we said it must be". This file also carries the one value-shaped rule in the pack: `runtime` is the single key OKF marks REQUIRED here, and only when `type` is `Attested Computation`. Ordinary concepts never match that condition and are unaffected, and no other key in the family is mandated. OKF records the computation and the means to check it and executes nothing itself; receipts and verdicts are runtime artifacts that are never stored in the bundle. Section numbers cite OKF v0.2: https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md#10-attested-computations-concept',+ 'Shapes for the OKF v0.2 computation keys, which turn a concept into a sanctioned way to compute a value so a consumer can confirm the agent ran the blessed computation instead of improvising its own. Provenance answers "where did this claim come from"; attestation answers "was this number produced the way we said it must be". This file also carries the one value-shaped rule in the pack: `runtime` is the single key OKF marks REQUIRED here, and only when `type` is `Attested Computation`. Ordinary concepts never match that condition and are unaffected, and no other key in the family is mandated. OKF records the computation and the means to check it and executes nothing itself; receipts and verdicts are runtime artifacts that are never stored in the bundle. Section numbers cite OKF v0.2: https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/ad30107c31c06aec8a7d5636e0d1058118604e6f/SPEC.md#10-attested-computations-concept',type: 'object',if: {required: ['type'],@@ -313,7 +317,7 @@ export const OKF_RESERVED_INDEX_SCHEMA: Record<string, unknown> = {$schema: 'http://json-schema.org/draft-07/schema#',title: 'OKF v0.2 — index files carry no frontmatter',description:- "`index.md` is a reserved filename at any level of the hierarchy and must not be used for a concept document. Index files contain no frontmatter, with exactly one exception — a bundle-root `index.md` may carry `okf_version` — which the scope carves out with a `!index` exclusion rather than a keyword here. `maxProperties: 0` is the mechanism rather than the boolean schema `false`, because a document with no frontmatter block validates as `{}` and `false` would reject that too, flagging the very documents that are correct. `log.md` is deliberately NOT covered: §9 constrains a log's date headings, ordering, and prose entries but never its frontmatter, and OKF's own reference bundle ships a `log.md` carrying `type` and `title`. Section numbers cite OKF v0.2: https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md#8-index-files",+ "`index.md` is a reserved filename at any level of the hierarchy and must not be used for a concept document. Index files contain no frontmatter, with exactly one exception — a bundle-root `index.md` may carry `okf_version` — which the scope carves out with a `!index` exclusion rather than a keyword here. `maxProperties: 0` is the mechanism rather than the boolean schema `false`, because a document with no frontmatter block validates as `{}` and `false` would reject that too, flagging the very documents that are correct. `log.md` is deliberately NOT covered: §9 constrains a log's date headings, ordering, and prose entries but never its frontmatter, and OKF's own reference bundle ships a `log.md` carrying `type` and `title`. Section numbers cite OKF v0.2: https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/ad30107c31c06aec8a7d5636e0d1058118604e6f/SPEC.md#8-index-files",type: 'object',maxProperties: 0,};@@ -322,7 +326,7 @@ export const OKF_ROOT_INDEX_SCHEMA: Record<string, unknown> = {$schema: 'http://json-schema.org/draft-07/schema#',title: 'OKF v0.2 — bundle-root index.md',description:- "The bundle-root `index.md` is the only index file OKF permits frontmatter in, and `okf_version` is the key it names there. OKF states the declaration as a MAY, so it is not required here. Nor is the frontmatter closed to other keys: §8 grants the exception for `okf_version` specifically, but §11 tells consumers not to reject a bundle over unknown additional keys, and that ambiguity is resolved in favor of the looser reading. The one thing pinned is the value's shape, because a YAML float is provably lossy where a version string is not. Section numbers cite OKF v0.2: https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md#12-versioning",+ "The bundle-root `index.md` is the only index file OKF permits frontmatter in, and `okf_version` is the key it names there. OKF states the declaration as a MAY, so it is not required here. Nor is the frontmatter closed to other keys: §8 grants the exception for `okf_version` specifically, but §11 tells consumers not to reject a bundle over unknown additional keys, and that ambiguity is resolved in favor of the looser reading. The one thing pinned is the value's shape, because a YAML float is provably lossy where a version string is not. Section numbers cite OKF v0.2: https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/ad30107c31c06aec8a7d5636e0d1058118604e6f/SPEC.md#12-versioning",type: 'object',properties: {okf_version: {diff --git a/packages/server/assets/skills/packs/okf/SKILL.md b/packages/server/assets/skills/packs/okf/SKILL.mdindex c2284de22..107658eff 100644--- a/packages/server/assets/skills/packs/okf/SKILL.md+++ b/packages/server/assets/skills/packs/okf/SKILL.md@@ -11,7 +11,7 @@ metadata:---# Open Knowledge Format (OKF)-[OKF v0.2](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md) is a portable format for agent-readable knowledge: Markdown files, YAML frontmatter, and standard links. The `/open-knowledge` skill governs tool use; this skill covers OKF semantics.+[OKF v0.2](https://github.com/GoogleCloudPlatform/open-knowledge-format/blob/main/SPEC.md) is a portable format for agent-readable knowledge: Markdown files, YAML frontmatter, and standard links. The `/open-knowledge` skill governs tool use; this skill covers OKF semantics.## Core rules@@ -31,6 +31,7 @@ metadata:- Use `title`, `description`, `resource`, and `tags` only when they add real information.- Record provenance in `sources`. Join claim-level citations with matching `sources[].id` and Markdown footnotes.- Keep authorship and verification separate: `generated` says who produced content; `verified` says who confirmed it. Use exact lowercase `human:` and `process:` prefixes when applicable.+- Write every provenance timestamp as an ISO 8601 datetime with an explicit UTC offset (`stale_after: 2026-12-31T00:00:00Z`), never a bare date and never an offsetless time. This covers `generated.at`, `verified[].at`, `stale_after`, `sources[].last_modified`, and both `usage_window` bounds. A `log.md` entry heading is different: it stays a plain `YYYY-MM-DD` date.- Treat `status: deprecated` and expired `stale_after` values as trust signals, not validation errors.- For `type: Attested Computation`, follow the declared runtime and parameters. Do not rewrite the sanctioned computation.