xdrs-core 0.56.0 → 0.56.1

package/.xdrs/_core/adrs/index.md

@@ -29,6 +29,7 @@ Foundational standards, principles, and guidelines.
 - [_core-adr-policy-021](principles/021-skill-bundling.md) - **Skill bundling** — Optional per-skill Makefile mechanism to stage a self-contained dist/ output for standalone distribution
 - [_core-adr-policy-022](principles/022-scope-activation.md) - **Scope activation** — How installed scopes are listed in the root index, activated, narrowed, or disabled, and when they become read-only
 - [_core-adr-policy-023](principles/023-skill-runtime-standards.md) - **Skill runtime standards** — How skills place work files under .tmp, halt, ask for clarification, and cap generated content
+- [_core-adr-policy-024](principles/024-sync-date-frontmatter.md) - **Sync date frontmatter** — Optional `sync-date` field recording when an element was last verified or reconciled with other entities
 
 ## Skills
 

package/.xdrs/_core/adrs/principles/001-xdrs-standards.md

@@ -91,6 +91,7 @@ ADR and EDR share the same six technical subject names (see [`_core-adr-policy-0
     - `apply-to` (required): Declares in which contexts — teams, systems, codebases, or environments — the decisions in this scope are relevant. Max 30 words.
     - `valid-from` (required): ISO date (YYYY-MM-DD) from which this scope became active.
     - `metadata` (optional): Arbitrary key-value map for additional scope metadata.
+    - `sync-date` (optional, opt-in): see `_core-adr-policy-024`.
     - `follows` (optional): Core scope names whose Policies apply as mandatory governance conventions to this scope, beyond `_core`. Last-listed takes precedence on conflicts (e.g., `follows: myarea-core, shared-standards`). A missing scope MUST be fixed in local scopes and makes external scopes READ-ONLY (see `_core-adr-policy-022.06-read-only-dependencies`).
     - `extends` (optional): Scope names whose **policy documents** (decision records only — not skills, articles, research, or initiatives) are inherited by this scope as if they were authored here. Any scope type except `_local` and `_core` may be referenced. Last-listed extended scope takes precedence on conflicts; the extending scope's own policies always take highest precedence. Depth-first transitive resolution applies: if A extends [B, C] and B extends [D], the effective precedence order is D < B < C < A. `extends:` and `follows:` MUST reference disjoint scope sets. A missing scope MUST be fixed in local scopes and makes external scopes READ-ONLY (see `_core-adr-policy-022.06-read-only-dependencies`). When an extending scope's policy overrides an inherited policy on the same topic, a `## Conflicts` section MUST document the override. Extended scopes are still linked in the root index; tag them `extends-only` to apply them only via `extends:` (see `_core-adr-policy-022.01-root-index-completeness`). `extends:` takes precedence over root index ordering for conflict resolution between the scopes involved; root index ordering is the fallback for all other scope pairs. See `_core-adr-policy-010` Section D (rules 27–35) and Section E (rule 36) for full normative rules.
     - `extends-only` (optional): See `_core-adr-policy-022.07-extends-only-field`.

package/.xdrs/_core/adrs/principles/002-policy-standards.md

@@ -31,6 +31,7 @@ Policy documents are the authoritative source of truth for their scope, type, an
 | `valid-from` | Yes | ISO date (`YYYY-MM-DD`) indicating from when this decision MUST be enforced. Before this date it SHOULD be used everywhere possible, but compliance is not enforced during reviews until after this date. Defaults to the date the Policy was created. When updating an existing Policy whose `valid-from` date has already passed, preserve the original date—it MUST NOT be updated to the current date. The historical date shows when the policy was originally enabled and is important for understanding policy evolution. |
 | `license` | No | SPDX license expression (e.g. `MIT`, `Apache-2.0`, `CC-BY-4.0`). Indicates the license under which the document content is shared. If omitted, the license is governed by the repository or package defaults. |
 | `metadata` | No | Arbitrary key-value map for additional properties not defined by this spec. |
+| `sync-date` | No | ISO date (`YYYY-MM-DD`) of the last verification or reconciliation of the Policy with other entities. Opt-in, never added by default, and MUST NOT appear in Policies of `compiled` scopes. See [`_core-adr-policy-024`](024-sync-date-frontmatter.md). |
 | `freeze-reference` | No | Boolean (`true` or `false`, defaults to `false`). When `true`, the policy MUST NOT be renamed, renumbered, or moved because external parties reference it by its current identity (path, number, name, heading). Reference-identity issues are intentionally exempt. See rule [`01-freeze-reference-exemption`](#01-freeze-reference-exemption). |
 
   - Minimal example:
@@ -116,6 +117,7 @@ description: [What this decision is about and when to use it]
 apply-to: [Required. Contexts this decision applies to, <40 words. Use "All scopes" when broadly applicable.]
 valid-from: [Required. ISO date YYYY-MM-DD from when enforcement begins. Defaults to creation date.]
 license: [Optional. SPDX license expression]
+sync-date: [Optional, opt-in. ISO date of the last verification with other entities; see _core-adr-policy-024]
 metadata:
   [optional-key]: [optional-value]
 ---

package/.xdrs/_core/adrs/principles/003-skill-standards.md

@@ -104,6 +104,7 @@ metadata:                 # required
   author: <team-or-person>       # required
   version: "1.0.0"                # required: full semantic versioning
   updated: YYYY-MM-DD              # required: date of the last material content change
+  sync-date: YYYY-MM-DD            # optional, opt-in: date of the last verification with other entities (see _core-adr-policy-024)
 ---
 
 ## Overview
@@ -163,6 +164,7 @@ Rules:
 - The `name` field MUST match the folder name exactly (e.g., `code-review`). This keeps skill identifiers simple and aligned with the filesystem hierarchy.
 - The directory name and the `name:` field MUST contain only lowercase alphanumeric characters and hyphens (e.g., `code-review`, `2fa-setup`).
 - `metadata` is REQUIRED. `metadata.version` MUST use full semantic versioning (`MAJOR.MINOR.PATCH`, e.g. `1.0.0`), consistent with [`_core-adr-policy-005`](005-semantic-versioning-for-xdrs-packages.md); `metadata.author` MUST be non-empty; `metadata.updated` MUST be an ISO `YYYY-MM-DD` date, refreshed whenever the skill's content materially changes.
+- `metadata.sync-date` is OPTIONAL and follows [`_core-adr-policy-024`](024-sync-date-frontmatter.md); it is distinct from `metadata.updated`, which records content changes only.
 - `description` SHOULD stay near 250 characters when the activation trigger can be stated that tightly, even though the hard cap remains 1024 characters — it is loaded into context on every activation scan.
 - `## Overview` SHOULD state the task objective, expected outcome, and relevant prerequisites or tools when they matter, and MUST contain nested subsections, in order, for `### Inputs`, `### Outputs`, `### Halt Conditions`, then the optional `### User Interaction` and `### Runtime Requirements`.
 - `### Inputs` MUST contain `#### Required` (the bare minimum needed to invoke the skill) then `#### Optional` (helpful extra context), in that order.

package/.xdrs/_core/adrs/principles/004-article-standards.md

@@ -42,6 +42,7 @@ Articles are Markdown documents placed inside a subject folder alongside policie
 - For diagram format preferences and non-Markdown asset rules, see [`_core-adr-policy-020`](020-media-and-asset-standards.md). Articles SHOULD use diagrams to illustrate concepts, overviews, and relationships; draw.io SHOULD be used for conceptual and relationship diagrams (e.g., component maps, context views, architecture overviews) when Mermaid cannot adequately express them.
 - File names MUST be lowercase.
 - MUST NOT use emojis in article content.
+- An article MAY start with a frontmatter block containing only `sync-date`, per [`_core-adr-policy-024`](024-sync-date-frontmatter.md); the title line follows the block.
 
 **Folder layout**
 
@@ -71,6 +72,10 @@ Examples:
 All articles MUST follow this template:
 
 ```markdown
+---
+sync-date: [Optional, opt-in. ISO date of the last verification with other entities; see _core-adr-policy-024. When absent, omit the whole frontmatter block.]
+---
+
 # [scope]-[type]-article-[number]: [Short Title]
 
 <!-- If this article is part of a series, add the line below (omit otherwise): -->

package/.xdrs/_core/adrs/principles/006-research-standards.md

@@ -46,6 +46,7 @@ Research documents are Markdown files placed inside a subject folder alongside p
 - `## Conclusion` MUST summarize the main findings, practical takeaway, applicability boundaries, and important open questions. It MUST stay under 400 words.
 - `## References` MUST list all cited literature, websites, tutorials, documentation, discussions, or related artifacts.
 - In general, research SHOULD roughly follow the proportion `Introduction : Methods : Results : Discussion ≈ 3 : 5 : 6 : 4`.
+- A research document MAY start with a frontmatter block containing only `sync-date`, per [`_core-adr-policy-024`](024-sync-date-frontmatter.md); the title line follows the block.
 - Be strict about the goal of each section. Avoid duplicating the same material across sections and prefer clarity over rhetorical flourishes.
 - Research documents SHOULD stay under 5000 words total. They MAY exceed that only when the `## Introduction` explicitly states that the study will be lengthy because a very detailed analysis is required.
 - Research documents SHOULD link in `## References` to the Policies, skills, articles, discussions, and external references relevant to the subject or that later cite the work.
@@ -83,6 +84,10 @@ Examples:
 All research documents MUST follow this template:
 
 ```markdown
+---
+sync-date: [Optional, opt-in. ISO date of the last verification with other entities; see _core-adr-policy-024. When absent, omit the whole frontmatter block.]
+---
+
 # [scope]-[type]-research-[number]: [Short Title]
 
 ## Abstract

package/.xdrs/_core/adrs/principles/007-initiative-standards.md

@@ -34,6 +34,7 @@ Initiatives are Markdown documents placed inside a subject folder alongside poli
 - Initiatives MUST include an `Expected end date:` field in ISO format (YYYY-MM-DD) inside the `## Proposed Solution` section.
 - File names MUST be lowercase.
 - MUST NOT use emojis in initiative content.
+- An initiative MAY start with a frontmatter block containing only `sync-date`, per [`_core-adr-policy-024`](024-sync-date-frontmatter.md); the title line follows the block.
 - For diagram format preferences and non-Markdown asset rules, see [`_core-adr-policy-020`](020-media-and-asset-standards.md).
 
 **Folder layout**
@@ -63,6 +64,10 @@ Examples:
 All initiatives MUST follow this template:
 
 ```markdown
+---
+sync-date: [Optional, opt-in. ISO date of the last verification with other entities; see _core-adr-policy-024. When absent, omit the whole frontmatter block.]
+---
+
 # [scope]-[type]-initiative-[number]: [Short Title]
 
 ## Executive Summary

package/.xdrs/_core/adrs/principles/010-scope-governance.md

@@ -83,7 +83,7 @@ A scope-type definition policy MAY declare a parent scope type by including a ru
 
 A `scope-type` value in a scope `index.md` is valid if and only if a policy file whose name ends with `{scope-type}-scope-type` exists in the `principles` subject of any `core`-type scope in the workspace. When `scope-type` is an array, this applies to every element.
 
-When a scope declares a `scope-type` but any corresponding `{scope-type}-scope-type.md` policy is absent from the workspace or defined only in a `disabled` scope, the scope MUST be treated as READ-ONLY (see `_core-adr-policy-022.06-read-only-dependencies`). Missing or disabled-only types MUST be fixed in local scopes.
+When a scope declares a `scope-type` but any corresponding `{scope-type}-scope-type.md` policy is absent from the workspace or defined only in a `disabled` scope, the scope MUST be treated as READ-ONLY (see `_core-adr-policy-022.06-read-only-dependencies`). Missing or disabled-only types MUST be fixed in local scopes, unless the scope is itself disabled.
 
 #### 11-def-scope-type-must-be-structured
 
@@ -213,7 +213,7 @@ A scope `extends:` declaration MUST NOT reference the declaring scope itself. To
 
 #### 32-extends-mandatory-presence
 
-Every scope listed in a scope's `extends:` field MUST exist in the workspace with an accessible `index.md`. If any referenced scope is absent or its `index.md` cannot be read, the extending scope MUST be fixed when local and is READ-ONLY when external (`_core-adr-policy-022.06-read-only-dependencies`).
+Every scope listed in a scope's `extends:` field MUST exist in the workspace with an accessible `index.md`. If any referenced scope is absent or its `index.md` cannot be read, the extending scope MUST be fixed when local and is READ-ONLY when external, unless it is itself disabled (`_core-adr-policy-022.06-read-only-dependencies`).
 
 #### 33-extends-content-precedence
 

package/.xdrs/_core/adrs/principles/011-core-scope-type.md

@@ -65,7 +65,7 @@ A `core`-type scope MAY be distributed to consumers alongside the companion cons
 
 #### 08-unavailable-core-read-only
 
-A `-core` scope referenced via `follows:` in a companion scope's `index.md` may not be present in the workspace of a consumer of that companion scope. When the referenced `-core` scope is absent or tagged `disabled` in the root index, the companion scope MUST be treated as READ-ONLY (see `_core-adr-policy-022.06-read-only-dependencies`): content in it MUST NOT be added, changed, or removed. The scope lacks the meta governance that defines how its content MUST be authored, and modifications without those standards would produce non-compliant content. Tools and agents MUST NOT propose or apply changes to a READ-ONLY scope and MUST surface the read-only status to the user when the scope is accessed.
+A `-core` scope referenced via `follows:` in a companion scope's `index.md` may not be present in the workspace of a consumer of that companion scope. When the referenced `-core` scope is absent or tagged `disabled` in the root index, the companion scope MUST be treated as READ-ONLY, unless the companion scope is itself tagged `disabled` (see `_core-adr-policy-022.06-read-only-dependencies`): content in it MUST NOT be added, changed, or removed. The scope lacks the meta governance that defines how its content MUST be authored, and modifications without those standards would produce non-compliant content. Tools and agents MUST NOT propose or apply changes to a READ-ONLY scope and MUST surface the read-only status to the user when the scope is accessed.
 
 #### 09-distribution-advisable
 

package/.xdrs/_core/adrs/principles/019-compiled-scope-type.md

@@ -141,9 +141,14 @@ An exception MUST be documented in a dedicated `[type]/principles/NNN-direct-sou
 
 This rule governs reasoning and usage, not the document-link graph. Independently of this rule, and regardless of whether a `NNN-direct-source-usage.md` policy exists, no document MAY hyperlink directly into `.assets/sources/`; that restriction is enforced mechanically and addresses a separate, structural concern.
 
+#### 15-scope-sync-date
+
+Compilation tools and agents MUST maintain `sync-date` in the scope `index.md` as defined in [`_core-adr-policy-024.07-compiled-scopes`](024-sync-date-frontmatter.md), setting it only after lint and review pass for the cycle.
+
 ## References
 
 - [_core-adr-policy-008 - Policy structured standards](008-policy-structured-standards.md) — numbered rule format required for all policies in compiled scopes
 - [_core-adr-policy-010 - Scope governance](010-scope-governance.md) — scope-type definition convention and local meta-policy mechanism
 - [_core-adr-policy-002 - Policy standards](002-policy-standards.md) — policy document format and frontmatter requirements
 - [_core-adr-policy-001 - XDRS standards](001-xdrs-standards.md) — scope structure and `scope-type` field definition
+- [_core-adr-policy-024 - Sync date frontmatter](024-sync-date-frontmatter.md) — `sync-date` field set on the scope index after each completed compilation

package/.xdrs/_core/adrs/principles/022-scope-activation.md

@@ -39,12 +39,14 @@ Policies of a scope tagged `extends-only` MUST be applied only through the `exte
 
 #### 05-disabled
 
-All content of a scope tagged `disabled` MUST be ignored by agents: its policies, skills, articles, research, and initiatives are not applied, and nothing is inherited from it through `extends:` or `follows:`. The scope is still validated and MAY be edited; a disabled local scope follows rule 06 like any other local scope. Skills of a disabled scope that are symlinked into `.agents/skills` (see `_core-adr-policy-018`) stay loaded by tools and MUST be removed by the consumer.
+All content of a scope tagged `disabled` MUST be ignored by agents: its policies, skills, articles, research, and initiatives are not applied, and nothing is inherited from it through `extends:` or `follows:`. The scope is still validated and MAY be edited; a disabled scope is exempt from the dependency causes of rule 06. Skills of a disabled scope that are symlinked into `.agents/skills` (see `_core-adr-policy-018`) stay loaded by tools and MUST be removed by the consumer.
 
 #### 06-read-only-dependencies
 
 A scope MUST be treated as READ-ONLY when a scope it follows or extends, or the scope that defines one of its scope types (including parent types), is missing, disabled, or invalid, or when it is an external scope and its own `index.md` is invalid. Content in a READ-ONLY scope MUST NOT be added, changed, or removed.
 
+A scope tagged `disabled` is treated as not present, so it is exempt from every dependency cause above, whether the scope is local or external: it MAY follow or extend disabled, missing, or invalid scopes, or use a scope type defined only in disabled scopes. An enabled scope keeps all causes: it cannot extend or follow a disabled scope because it needs access to that scope. The exemption does not propagate along `extends:` chains.
+
 - **Local scope** (not tracked in `.filedist.lock`, including `_local` and disabled scopes): a read-only local scope is frozen and cannot be maintained, so each cause is invalid and MUST be fixed.
 - **External scope** (tracked in `.filedist.lock`): the scope is READ-ONLY; agents MUST tell the user when they skip a change because of it, naming the cause and fix.
 

package/.xdrs/_core/adrs/principles/024-sync-date-frontmatter.md

@@ -0,0 +1,76 @@
+---
+name: _core-adr-policy-024-sync-date-frontmatter
+description: Defines the optional `sync-date` frontmatter field that records when an XDRS element was last verified, checked, reconciled or aligned with other entities, internal or external. Use when a document depends on information that degrades over time, when adding or updating `sync-date`, or when a mechanism needs a refresh hint.
+apply-to: All XDRS elements (Policies, skills, articles, research, initiatives, scope indexes) and every tool, skill or agent that syncs them
+valid-from: 2026-11-04
+---
+
+# _core-adr-policy-024: Sync date frontmatter
+
+## Context and Problem Statement
+
+Some XDRS elements hold content whose quality degrades over time unless it is periodically checked against other entities: other scopes, external sources, APIs, URLs, scripts or people. Version control records when a file changed, but not when its content was last verified, nor that a verification ended with a decision to change nothing.
+
+How should an element declare when it was last checked or reconciled, so that humans, tools and agents can decide when a refresh is worth doing?
+
+## Decision Outcome
+
+**An optional, opt-in `sync-date` frontmatter field holding the date of the last sync**
+
+The field is a refresh hint. It is not a status, not a change date, and carries no enforcement semantics.
+
+### Details
+
+#### 01-sync-date-meaning
+
+`sync-date` MUST contain the ISO date (`YYYY-MM-DD`) on which the element content was last verified, checked, reconciled or aligned with one or more other entities. The other entity MAY be internal (another scope, element or review) or external (an API, URL, repository, script, skill or person). A sync that ended with no change, or with a deliberate decision to change nothing, still counts and MUST update the date.
+
+#### 02-not-a-change-date
+
+`sync-date` MUST NOT be used as a last-modified date or to record content changes, which are already available from version control. It MUST NOT be updated when the content was edited without any verification against another entity.
+
+#### 03-opt-in
+
+`sync-date` is OPTIONAL and MUST NOT be added by default. It MUST be added only when a compiled scope requires it (rule 07), or when the user or a skill explicitly requests it for a specific sync purpose.
+
+#### 04-purpose-check
+
+Before adding `sync-date`, the author or agent MUST identify the concrete sync process that will use it (for example a periodic review, a source re-sync, or a cross-scope reconciliation). When no such process exists, the field MUST NOT be added. An existing `sync-date` that no process uses SHOULD be removed.
+
+#### 05-placement-and-format
+
+The value MUST be an unquoted ISO date. Placement per element:
+
+| Element | Placement |
+|---|---|
+| Policy, scope `index.md` | Top-level frontmatter field `sync-date` |
+| Article, research, initiative | Top-level `sync-date` in an optional frontmatter block placed before the title line; the block MUST contain no other field |
+| Skill (`SKILL.md`) | Nested field `metadata.sync-date`, keeping the top-level frontmatter compatible with the agentskills spec |
+
+Slide presentations MUST NOT carry `sync-date`.
+
+Example:
+
+```yaml
+---
+sync-date: 2026-11-04
+---
+```
+
+#### 06-who-updates
+
+The date MUST be updated by whoever performs the sync (human, tool or agent), only after the sync completed. A failed or partial sync MUST NOT update it.
+
+#### 07-compiled-scopes
+
+In a scope declaring `scope-type: compiled`, `sync-date` MUST be present only in the scope `index.md`, never in individual Policies. Compilation tools and agents MUST set it to the current date at the end of every completed compilation or re-sync cycle, including cycles where no source content changed and no Policy was modified. It MUST NOT be updated when the cycle was skipped because every source was still within its re-sync period. Placing it only in the scope index avoids touching every Policy when nothing changed.
+
+#### 08-consumers
+
+Mechanisms that refresh or check content (compilation, reviews, scheduled syncs, scripts) SHOULD read `sync-date` as a hint to prioritize or skip refreshes, and MUST NOT treat a missing `sync-date` as an error. How old a date must be before a refresh is worthwhile is decided by each mechanism.
+
+## References
+
+- [_core-adr-policy-002 - Policy standards](002-policy-standards.md) - Policy frontmatter fields
+- [_core-adr-policy-003 - Skill standards](003-skill-standards.md) - SKILL.md frontmatter and metadata
+- [_core-adr-policy-019 - Compiled scope type](019-compiled-scope-type.md) - Compilation and re-sync process

package/.xdrs/_core/adrs/principles/skills/compile-scope/SKILL.md

@@ -4,8 +4,8 @@ description: >
   Compiles or updates any scope declaring `scope-type: compiled` from its configured external sources. Reads compilation meta-policies to discover sources, fetches content (git clone, local copy, or web scrape), plans policy changes, migrates policies one at a time with structured format, `## Source` sections, and `**compilation-note:**` markers, then runs lint and review. Documents source inconsistencies without inventing fixes. Activate when the user asks to compile, update, sync, refresh, or recompile a compiled scope.
 metadata:
   author: flaviostutz
-  version: "1.3.0"
-  updated: 2026-10-08
+  version: "1.4.0"
+  updated: 2026-11-04
 ---
 
 ## Overview
@@ -31,6 +31,7 @@ Performs a full compilation cycle for any scope declaring `scope-type: compiled`
 #### Changes
 
 - Policy files created, updated, or removed.
+- Scope `index.md` `sync-date` refreshed.
 
 ### Halt Conditions
 
@@ -107,7 +108,7 @@ Keep every question and intermediate message <100 words and the final summary <1
 For each TODO item marked CREATE or UPDATE, in sequence:
 
 1. **Write the policy file** (<2600 words, per `_core-adr-policy-002`) following `_core-adr-policy-019` and `_core-adr-policy-008`:
-   - Use standard policy frontmatter: `name`, `description`, `apply-to` (<40 words), `valid-from`. Generate these from the source text; they are exempt from the no-invented-content rule per policy-019 rule 05.
+   - Use standard policy frontmatter: `name`, `description`, `apply-to` (<40 words), `valid-from`. Generate these from the source text; they are exempt from the no-invented-content rule per policy-019 rule 05. Do NOT add `sync-date` to compiled policies; it lives only in the scope `index.md` (`_core-adr-policy-024.07-compiled-scopes`).
    - Use structured numbered rule blocks for all claims (per `_core-adr-policy-008`).
    - Transcribe source content faithfully. Do NOT invent, infer beyond what the source states, or fill gaps. Preserve ambiguities as-is.
 
@@ -169,6 +170,7 @@ After writing each policy:
 3. If storage is `temporary`: do not copy any bulk staged content into `.assets/sources/[name]/`; only `source.md` lives there.
 4. For every source processed in this run, update `.assets/sources/[name]/source.md`'s `last-compilation-timestamp` to the current time — this step only runs after Phase 6 (Lint) and Phase 7 (Review) both pass for the policies depending on that source.
 5. If a source's `Source storage` setting changed since its last run, reconcile per `_core-adr-policy-019` rule 12: switching to `temporary` removes previously persisted bulk content (keeping `source.md`); switching away from `temporary` begins persisting bulk content from this run onward.
+6. After lint and review pass for the cycle, set `sync-date` in the scope `index.md` frontmatter to today's date (`YYYY-MM-DD`), adding the field when absent, even when no source changed and no policy was modified (`_core-adr-policy-024.07-compiled-scopes`). Skip this step when the run halted or ended at the Phase 1 no-op.
 
 ### Phase 10: Report
 

package/.xdrs/_core/adrs/principles/skills/write-article/SKILL.md

@@ -4,8 +4,8 @@ description: >
    Creates a new article document following XDRS article standards: selects scope, type, subject, and number; then writes a focused synthetic text that combines and links multiple Policies, Research documents, and Skills around a topic. Activate this skill when the user asks to create, add, or write a new article, guide, or overview document within an XDRS project.
 metadata:
   author: flaviostutz
-  version: "1.1.0"
-  updated: 2026-09-24
+  version: "1.1.1"
+  updated: 2026-11-04
 ---
 
 ## Overview
@@ -103,7 +103,7 @@ If the article spans more than one subject, place it in `principles`.
 
 ### Phase 5: Write the Article
 
-Use the mandatory template from `004-article-standards`:
+Use the mandatory template from `004-article-standards`. Omit the optional `sync-date` frontmatter unless the user explicitly asks for it for a specific sync purpose (`_core-adr-policy-024`):
 
 ```
 # [scope]-[type]-article-[number]: [Short Title]

package/.xdrs/_core/adrs/principles/skills/write-initiative/SKILL.md

@@ -6,8 +6,8 @@ description: >
   Activate this skill when the user asks to create, add, or write an initiative, plan, project plan, roadmap, or execution plan within an XDRS project.
 metadata:
   author: flaviostutz
-  version: "1.1.0"
-  updated: 2026-09-24
+  version: "1.1.1"
+  updated: 2026-11-04
 ---
 
 ## Overview
@@ -93,7 +93,7 @@ Consult `001-xdrs-standards` while making each choice in this phase. The summari
 
 ### Phase 5: Write the Initiative
 
-Use the mandatory template from `007-initiative-standards`:
+Use the mandatory template from `007-initiative-standards`. Omit the optional `sync-date` frontmatter unless the user explicitly asks for it for a specific sync purpose (`_core-adr-policy-024`):
 
 ```markdown
 # [scope]-[type]-initiative-[number]: [Short Title]

package/.xdrs/_core/adrs/principles/skills/write-policy/SKILL.md

@@ -5,8 +5,8 @@ description: >
   Activate this skill when the user asks to create, add, or write a new Policy (ADR, BDR, or EDR).
 metadata:
   author: flaviostutz
-  version: "1.2.0"
-  updated: 2026-09-30
+  version: "1.2.1"
+  updated: 2026-11-04
 ---
 
 ## Overview
@@ -107,7 +107,7 @@ Choose a title that clearly states the question this Policy answers, not the ans
 
 ### Phase 6: Write the First Draft
 
-Use the mandatory template from `002-policy-standards`:
+Use the mandatory template from `002-policy-standards`. Omit the optional `sync-date` field unless the user explicitly asks for it for a specific sync purpose (`_core-adr-policy-024`); never add it to Policies of `compiled` scopes:
 
 **Check if the decision requires a structured set of rules:**
 If the decision defines strong rules or policies that must be stated explicitly, or if other documents, skills, or agents have a clear need to reference individual rules, you MUST apply the structured rule format from `_core-adr-policy-008-policy-structured-standards`. This means:

package/.xdrs/_core/adrs/principles/skills/write-research/SKILL.md

@@ -6,8 +6,8 @@ description: >
   Activate this skill when the user asks to create, add, or write a research document that backs a decision.
 metadata:
   author: flaviostutz
-  version: "1.5.0"
-  updated: 2026-09-24
+  version: "1.5.1"
+  updated: 2026-11-04
 ---
 
 ## Overview
@@ -124,7 +124,7 @@ If the results contain competing interpretations or the intended audience for th
 
 ### Phase 7: Write the Research Document
 
-Use the mandatory template from `006-research-standards`:
+Use the mandatory template from `006-research-standards`. Omit the optional `sync-date` frontmatter unless the user explicitly asks for it for a specific sync purpose (`_core-adr-policy-024`):
 
 ```markdown
 # [scope]-[type]-research-[number]: [Short Title]

package/.xdrs/_core/adrs/principles/skills/write-skill/SKILL.md

@@ -6,8 +6,8 @@ description: >
   Activate this skill when the user asks to create, add, or write a new skill, agent skill, or SKILL.md file.
 metadata:
   author: flaviostutz
-  version: "1.3.0"
-  updated: 2026-10-08
+  version: "1.3.1"
+  updated: 2026-11-04
 ---
 
 ## Overview
@@ -90,7 +90,7 @@ Quick test:
 
 ### Phase 4: Write the SKILL.md
 
-Use the mandatory agentskills format:
+Use the mandatory agentskills format. Omit the optional `metadata.sync-date` unless the user explicitly asks for it for a specific sync purpose (`_core-adr-policy-024`):
 
 ```
 ---

package/README.md

@@ -190,7 +190,7 @@ Scopes tagged `disabled` MUST be ignored; `extends-only` scopes apply only via e
 ```
 
 - `extends-only`: the scope's policies apply only through scopes that list it in `extends:`.
-- `disabled`: the scope is ignored; scopes that follow, extend or take their type from it become READ-ONLY.
+- `disabled`: the scope is ignored; enabled scopes that follow, extend or take their type from it become READ-ONLY, while a disabled scope may depend on other disabled scopes freely.
 - Scope authors declare `extends-only: true` in the scope `index.md` frontmatter when the scope is meant only to be extended; lint requires the root index tag to match.
 - The root index belongs to the consumer: packages ship it unmanaged so tags survive reinstalls.
 
@@ -217,6 +217,7 @@ The folder layout, file naming, and document format are designed so that AI agen
 - The canonical index per scope and type lists all XDRS elements with short descriptions, enabling agents to identify relevant records without reading every file.
 - The root index at `.xdrs/index.md` provides a single entry point for discovery.
 - Policy metadata gives agents a first-pass filter: check `valid-from` for the convergence date, then check `apply-to`, and finally the decision text itself to confirm the decision should be used in the current context. All documents present in the collection are considered active.
+- An optional, opt-in `sync-date` frontmatter field records when an element was last verified or reconciled against external entities (even if nothing changed). It is never added by default; compiled scopes set it in their scope index on every compile. See [_core-adr-policy-024](.xdrs/_core/adrs/principles/024-sync-date-frontmatter.md).
 - Decisions cross-reference each other by Policy ID rather than duplicating content, keeping individual files concise.
 - Subject folders reduce the search space when a query maps to a known domain.
 

package/lib/lint.js

@@ -32,9 +32,10 @@ const SOURCE_SNAPSHOT_DIR_NAME = 'sources';
 const SOURCE_TRACKING_FILE_NAME = 'source.md';
 const SKILL_PACKAGE_OPTIONAL_DIRS = new Set(['scripts', 'references', RESOURCE_DIR_NAME, 'dist']);
 
-const POLICY_ALLOWED_FRONTMATTER_KEYS = new Set(['name', 'description', 'apply-to', 'valid-from', 'license', 'metadata', 'freeze-reference']);
+const POLICY_ALLOWED_FRONTMATTER_KEYS = new Set(['name', 'description', 'apply-to', 'valid-from', 'license', 'metadata', 'freeze-reference', 'sync-date']);
 const SKILL_ALLOWED_FRONTMATTER_KEYS = new Set(['name', 'description', 'license', 'metadata']);
-const SCOPE_INDEX_ALLOWED_FRONTMATTER_KEYS = new Set(['scope-type', 'name', 'description', 'apply-to', 'valid-from', 'license', 'metadata', 'follows', 'extends', 'extends-only']);
+const SCOPE_INDEX_ALLOWED_FRONTMATTER_KEYS = new Set(['scope-type', 'name', 'description', 'apply-to', 'valid-from', 'license', 'metadata', 'follows', 'extends', 'extends-only', 'sync-date']);
+const SYNC_DATE_ONLY_FRONTMATTER_KEYS = new Set(['sync-date']);
 const IMAGE_EXTENSIONS = new Set(['.png', '.jpg', '.jpeg', '.gif', '.svg', '.webp', '.bmp']);
 const SLIDE_FILE_RE = /^.+-slides(?:-[a-z0-9-]+)?\.md$/;
 const SLIDE_MAX_NAME_LENGTH = 64;
@@ -238,8 +239,11 @@ function lintWorkspace(targetPath, options = {}) {
   // Populated during lintScopeIndexFrontmatter: scopeName -> [extendedScopeNames...]
   const extendsRelationships = new Map();
 
+  // A disabled scope is treated as not present, so it is exempt from dependency checks (_core-adr-policy-022.06)
+  const disabledScopes = new Set([...activation].filter(([, entry]) => entry.tag === 'disabled').map(([name]) => name));
+
   for (const scopeEntry of scopeEntries) {
-    lintScopeDirectory(xdrsRoot, scopeEntry.name, errors, actualTypeIndexes, ignoreExternal, effectiveExternalScopes, knownScopeTypes, extendsRelationships, externalScopes);
+    lintScopeDirectory(xdrsRoot, scopeEntry.name, errors, actualTypeIndexes, ignoreExternal, effectiveExternalScopes, knownScopeTypes, extendsRelationships, externalScopes, disabledScopes);
   }
 
   // Detect cycles in extends: chains (DFS)
@@ -434,7 +438,7 @@ function readScopeMeta(scopeIndexPath) {
 function lintLocalReadOnlyDependencies(xdrsRoot, scopeMeta, activation, externalScopes, knownScopeTypes, scopeTypeDefiningScopes, errors) {
   const isDisabled = (scopeName) => (activation.get(scopeName) || {}).tag === 'disabled';
   for (const [scopeName, meta] of scopeMeta) {
-    if (!meta || externalScopes.has(scopeName)) continue;
+    if (!meta || externalScopes.has(scopeName) || isDisabled(scopeName)) continue;
     const causes = [];
     for (const [field, targets] of [['follows', meta.follows], ['extends', meta.extends]]) {
       for (const target of targets) {
@@ -576,8 +580,9 @@ function deriveScopeNameListEntries(block, lineMatch, inlineValue) {
   return parseYamlListItems(block, lineMatch).filter(Boolean);
 }
 
-function lintScopeIndexFrontmatter(scopeIndexPath, scopeName, errors, xdrsRoot, knownScopeTypes = new Map(), extendsRelationships = new Map(), externalScopes = new Set()) {
+function lintScopeIndexFrontmatter(scopeIndexPath, scopeName, errors, xdrsRoot, knownScopeTypes = new Map(), extendsRelationships = new Map(), externalScopes = new Set(), disabledScopes = new Set()) {
   const isExternal = externalScopes.has(scopeName);
+  const skipMissingDependencies = isExternal || disabledScopes.has(scopeName);
   const content = fs.readFileSync(scopeIndexPath, 'utf8');
   const fmMatch = content.match(/^---\r?\n([\s\S]*?)\r?\n---(?:\r?\n|$)/);
   if (!fmMatch) {
@@ -638,7 +643,7 @@ function lintScopeIndexFrontmatter(scopeIndexPath, scopeName, errors, xdrsRoot,
   for (const st of scopeTypes) {
     if (st === '_local') continue;
     if (!knownScopeTypes.has(st)) {
-      if (!isExternal) {
+      if (!skipMissingDependencies) {
         errors.push(`Scope index scope-type "${st}" has no corresponding ${st}-scope-type policy in the principles of any scope: ${toDisplayPath(scopeIndexPath)} [_core-adr-policy-010.10-def-valid-iff-policy-exists]`);
       }
       continue;
@@ -728,6 +733,9 @@ function lintScopeIndexFrontmatter(scopeIndexPath, scopeName, errors, xdrsRoot,
   } else if (!isIsoDate(fm.validFrom)) {
     errors.push(`Scope index frontmatter valid-from must be a valid ISO date YYYY-MM-DD: ${toDisplayPath(scopeIndexPath)} [_core-adr-policy-001]`);
   }
+  if (fm.syncDate !== undefined && !isIsoDate(fm.syncDate)) {
+    errors.push(`Scope index frontmatter sync-date must be a valid ISO date YYYY-MM-DD: ${toDisplayPath(scopeIndexPath)} [_core-adr-policy-024.05-placement-and-format]`);
+  }
 
   let followsEntries = [];
   const followsLineMatch = block.match(/^follows:[ \t]*(.*)/m);
@@ -759,8 +767,8 @@ function lintScopeIndexFrontmatter(scopeIndexPath, scopeName, errors, xdrsRoot,
           }
           const followedIndexPath = path.join(xdrsRoot, entry, 'index.md');
           if (!existsFile(followedIndexPath)) {
-            // A missing dependency of an external scope makes it READ-ONLY (_core-adr-policy-022.06); lint does not report it.
-            if (!isExternal) {
+            // A missing dependency of an external scope makes it READ-ONLY and a disabled scope is exempt (_core-adr-policy-022.06); lint does not report it.
+            if (!skipMissingDependencies) {
               errors.push(`Scope index frontmatter follows references scope "${entry}" which does not exist in the workspace: ${toDisplayPath(scopeIndexPath)} [_core-adr-policy-001]`);
             }
           } else {
@@ -816,7 +824,7 @@ function lintScopeIndexFrontmatter(scopeIndexPath, scopeName, errors, xdrsRoot,
           continue;
         }
         if (!existsFile(path.join(xdrsRoot, entry, 'index.md'))) {
-          if (!isExternal) {
+          if (!skipMissingDependencies) {
             errors.push(`Scope index frontmatter extends references scope "${entry}" which does not exist in the workspace: ${toDisplayPath(scopeIndexPath)} [_core-adr-policy-010.32-extends-mandatory-presence]`);
           }
         }
@@ -829,7 +837,7 @@ function lintScopeIndexFrontmatter(scopeIndexPath, scopeName, errors, xdrsRoot,
 }
 
 
-function lintScopeDirectory(xdrsRoot, scopeName, errors, actualTypeIndexes, ignoreExternal, externalScopes, knownScopeTypes = new Map(), extendsRelationships = new Map(), trackedExternalScopes = new Set()) {
+function lintScopeDirectory(xdrsRoot, scopeName, errors, actualTypeIndexes, ignoreExternal, externalScopes, knownScopeTypes = new Map(), extendsRelationships = new Map(), trackedExternalScopes = new Set(), disabledScopes = new Set()) {
   const scopePath = path.join(xdrsRoot, scopeName);
 
   if (ignoreExternal && externalScopes.has(scopeName)) {
@@ -888,7 +896,7 @@ function lintScopeDirectory(xdrsRoot, scopeName, errors, actualTypeIndexes, igno
     errors.push(`Missing required scope index: ${toDisplayPath(scopeIndexPath)} [_core-adr-policy-001]`);
   } else {
     lintScopeIndex(scopeIndexPath, xdrsRoot, scopeName, typeIndexesInScope, errors, externalScopes);
-    lintScopeIndexFrontmatter(scopeIndexPath, scopeName, errors, xdrsRoot, knownScopeTypes, extendsRelationships, trackedExternalScopes);
+    lintScopeIndexFrontmatter(scopeIndexPath, scopeName, errors, xdrsRoot, knownScopeTypes, extendsRelationships, trackedExternalScopes, disabledScopes);
   }
   lintLocalMetaPolicies(xdrsRoot, scopeName, errors, isCompiledScope);
 }
@@ -1122,7 +1130,7 @@ function lintXdrsElementFile(xdrsRoot, scopeName, typeName, subjectName, filePat
 
   const expectedName = extractExpectedXdrsNameFromHeading(firstLine)
     || `${scopeName}-${TYPE_TO_ID[typeName]}-${number}-${match[2]}`;
-  lintXdrsElementFrontmatter(content, expectedName, filePath, errors, freezeReference);
+  lintXdrsElementFrontmatter(content, expectedName, filePath, errors, freezeReference, isCompiledScope);
   if (enforceStructured) {
     validateStructuredFormatContent(content, filePath, errors, '_core-adr-policy-010.12-def-core-scope-policies-must-be-structured');
   } else if (isCompiledScope) {
@@ -1166,7 +1174,7 @@ function slugifyTitle(title) {
     .replace(/--+/g, '-');
 }
 
-function lintXdrsElementFrontmatter(content, expectedName, filePath, errors, freezeReference = false) {
+function lintXdrsElementFrontmatter(content, expectedName, filePath, errors, freezeReference = false, isCompiledScope = false) {
   const fm = extractFrontmatter(content);
   if (!fm.present) {
     errors.push(`Policy must start with a YAML frontmatter block: ${toDisplayPath(filePath)} [_core-adr-policy-002]`);
@@ -1210,6 +1218,34 @@ function lintXdrsElementFrontmatter(content, expectedName, filePath, errors, fre
       errors.push(`Policy frontmatter has unknown field "${key}": ${toDisplayPath(filePath)} [_core-adr-policy-002]`);
     }
   }
+  if (fm.syncDate !== undefined) {
+    if (isCompiledScope) {
+      errors.push(`Policy frontmatter must not include sync-date in a compiled scope (it belongs in the scope index): ${toDisplayPath(filePath)} [_core-adr-policy-024.07-compiled-scopes]`);
+    } else if (!isIsoDate(fm.syncDate)) {
+      errors.push(`Policy frontmatter sync-date must be a valid ISO date YYYY-MM-DD: ${toDisplayPath(filePath)} [_core-adr-policy-024.05-placement-and-format]`);
+    }
+  }
+}
+
+/**
+ * Validates the optional frontmatter block of articles, research and initiatives: it may only
+ * contain a valid `sync-date` (_core-adr-policy-024.05-placement-and-format).
+ */
+function lintSyncDateOnlyFrontmatter(content, filePath, docType, policyId, errors) {
+  const fm = extractFrontmatter(content);
+  if (!fm.present) {
+    return;
+  }
+  for (const key of fm.topLevelKeys) {
+    if (!SYNC_DATE_ONLY_FRONTMATTER_KEYS.has(key)) {
+      errors.push(`${docType} frontmatter has unknown field "${key}" (only sync-date is allowed): ${toDisplayPath(filePath)} [${policyId}]`);
+    }
+  }
+  if (fm.syncDate === undefined) {
+    errors.push(`${docType} frontmatter must include a sync-date field when present: ${toDisplayPath(filePath)} [${policyId}]`);
+  } else if (!isIsoDate(fm.syncDate)) {
+    errors.push(`${docType} frontmatter sync-date must be a valid ISO date YYYY-MM-DD: ${toDisplayPath(filePath)} [_core-adr-policy-024.05-placement-and-format]`);
+  }
 }
 
 function lintSkillsDirectory(xdrsRoot, scopeName, skillsPath, errors, externalScopes = new Set()) {
@@ -1346,6 +1382,10 @@ function lintSkillMetadata(metadata, skillFilePath, errors) {
   } else if (!isIsoDate(fields.updated)) {
     errors.push(`SKILL.md frontmatter metadata.updated must be a valid ISO date YYYY-MM-DD: ${toDisplayPath(skillFilePath)} [_core-adr-policy-003]`);
   }
+
+  if (fields['sync-date'] !== undefined && !isIsoDate(fields['sync-date'])) {
+    errors.push(`SKILL.md frontmatter metadata.sync-date must be a valid ISO date YYYY-MM-DD: ${toDisplayPath(skillFilePath)} [_core-adr-policy-024.05-placement-and-format]`);
+  }
 }
 
 /**
@@ -1715,10 +1755,11 @@ function lintArticlesDirectory(xdrsRoot, scopeName, typeName, subjectName, artic
     const content = fs.readFileSync(entryPath, 'utf8');
     const typeId = TYPE_TO_ID[typeName].split('-')[0]; // 'adr', 'bdr', or 'edr'
     const expectedHeader = `# ${scopeName}-${typeId}-article-${number}:`;
-    const firstLine = firstNonEmptyLine(content);
+    const firstLine = firstNonEmptyLine(stripFrontmatter(content));
     if (!firstLine.startsWith(expectedHeader)) {
       errors.push(`Article title must start with "${expectedHeader}": ${toDisplayPath(entryPath)} [_core-adr-policy-004]`);
     }
+    lintSyncDateOnlyFrontmatter(content, entryPath, 'Article', '_core-adr-policy-004', errors);
 
     lintRequiredSections(content, entryPath, ARTICLE_REQUIRED_SECTIONS, 'Article', errors);
     lintNoEmojis(content, entryPath, 'Article', errors);
@@ -1770,10 +1811,11 @@ function lintResearchDirectory(xdrsRoot, scopeName, typeName, subjectName, resea
     const content = fs.readFileSync(entryPath, 'utf8');
     const typeId = TYPE_TO_ID[typeName].split('-')[0]; // 'adr', 'bdr', or 'edr'
     const expectedHeader = `# ${scopeName}-${typeId}-research-${number}:`;
-    const firstLine = firstNonEmptyLine(content);
+    const firstLine = firstNonEmptyLine(stripFrontmatter(content));
     if (!firstLine.startsWith(expectedHeader)) {
       errors.push(`Research title must start with "${expectedHeader}": ${toDisplayPath(entryPath)} [_core-adr-policy-006]`);
     }
+    lintSyncDateOnlyFrontmatter(content, entryPath, 'Research', '_core-adr-policy-006', errors);
 
     lintRequiredSections(content, entryPath, RESEARCH_REQUIRED_SECTIONS, 'Research', errors);
     lintResearchIntroductionQuestion(content, entryPath, errors);
@@ -1827,10 +1869,11 @@ function lintInitiativesDirectory(xdrsRoot, scopeName, typeName, subjectName, in
     const content = fs.readFileSync(entryPath, 'utf8');
     const typeId = TYPE_TO_ID[typeName].split('-')[0]; // 'adr', 'bdr', or 'edr'
     const expectedHeader = `# ${scopeName}-${typeId}-initiative-${number}:`;
-    const firstLine = firstNonEmptyLine(content);
+    const firstLine = firstNonEmptyLine(stripFrontmatter(content));
     if (!firstLine.startsWith(expectedHeader)) {
       errors.push(`Initiative title must start with "${expectedHeader}": ${toDisplayPath(entryPath)} [_core-adr-policy-007]`);
     }
+    lintSyncDateOnlyFrontmatter(content, entryPath, 'Initiative', '_core-adr-policy-007', errors);
 
     lintRequiredSections(content, entryPath, INITIATIVE_REQUIRED_SECTIONS, 'Initiative', errors);
     lintInitiativeExpectedEndDate(content, entryPath, errors);
@@ -2381,6 +2424,7 @@ function extractFrontmatter(content) {
   const nameMatch = block.match(/^name:\s*(.+)$/m);
   const validFromMatch = block.match(/^valid-from:\s*(.+)$/m);
   const appliedToMatch = block.match(/^apply-to:\s*(.+)$/m);
+  const syncDateMatch = block.match(/^sync-date:[ \t]*(.*)$/m);
   const topLevelKeys = [];
   for (const line of block.split('\n')) {
     const keyMatch = line.match(/^([a-zA-Z][a-zA-Z0-9_-]*):\s*/);
@@ -2396,6 +2440,7 @@ function extractFrontmatter(content) {
     descriptionText,
     validFrom: validFromMatch ? validFromMatch[1].trim() : undefined,
     appliedTo: appliedToMatch ? appliedToMatch[1].trim() : undefined,
+    syncDate: syncDateMatch ? syncDateMatch[1].trim() : undefined,
     freezeReference: freezeReferenceMatch ? freezeReferenceMatch[1].trim() === 'true' : false,
     metadata,
     topLevelKeys,

package/lib/lint.test.js

@@ -5905,16 +5905,147 @@ test('reports a local scope whose type is defined only in a disabled scope as fr
   expect(activationErrors(result)).toContain('Local scope "shop" is frozen (read-only) because scope type "widget" is defined only in disabled scope(s) "widgets-core"');
 });
 
-test('reports missing dependencies of a disabled local scope as errors [022.05]', () => {
+test('does not report missing dependencies of a disabled scope [022.06]', () => {
   const workspaceRoot = createWorkspace('activation-disabled-local-missing-deps', {
     '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope myteam](myteam/index.md) `disabled`', ACTIVATION_LEGEND]),
     ...scopeFiles('myteam', 'follows: ghost-core\nextends: ghost-lib\n', 'phantom'),
     ...coreWithScopeTypes(['standard']),
   });
   const errors = lintWorkspace(workspaceRoot, { ignoreExternal: false }).errors.join('\n');
-  expect(errors).toContain('follows references scope "ghost-core" which does not exist in the workspace');
-  expect(errors).toContain('ghost-lib');
-  expect(errors).toContain('phantom');
+  expect(errors).not.toContain('ghost-core');
+  expect(errors).not.toContain('ghost-lib');
+  expect(errors).not.toContain('phantom');
+});
+
+test('does not report a disabled scope extending a disabled scope [022.06]', () => {
+  const workspaceRoot = createWorkspace('activation-disabled-extends-disabled', {
+    '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope lib](lib/index.md) `disabled`', '[View scope mid](mid/index.md) `disabled`', ACTIVATION_LEGEND]),
+    ...scopeFiles('lib'),
+    ...scopeFiles('mid', 'extends: lib\n'),
+  });
+  const result = lintWorkspace(workspaceRoot, { ignoreExternal: false });
+  expect(activationErrors(result)).toBe('');
+  expect(result.errors.join('\n')).not.toContain('frozen');
+});
+
+test('does not report a disabled scope following a disabled core scope [022.06]', () => {
+  const workspaceRoot = createWorkspace('activation-disabled-follows-disabled', {
+    '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope area-core](area-core/index.md) `disabled`', '[View scope myteam](myteam/index.md) `disabled`', ACTIVATION_LEGEND]),
+    ...scopeFiles('area-core', '', 'core'),
+    ...scopeFiles('myteam', 'follows: area-core\n'),
+  });
+  expect(activationErrors(lintWorkspace(workspaceRoot, { ignoreExternal: false }))).toBe('');
+});
+
+test('does not report a disabled scope whose type is defined only in a disabled scope [022.06]', () => {
+  const workspaceRoot = createWorkspace('activation-disabled-type-in-disabled', {
+    '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope widgets-core](widgets-core/index.md) `disabled`', '[View scope shop](shop/index.md) `disabled`', ACTIVATION_LEGEND]),
+    '.xdrs/widgets-core/index.md': scopeIndexWith('widgets-core', '', 'core'),
+    '.xdrs/widgets-core/adrs/index.md': teamAdrIndex(['- [001-widget-scope-type](principles/001-widget-scope-type.md) - Widget type']),
+    '.xdrs/widgets-core/adrs/principles/001-widget-scope-type.md': structuredScopeTypePolicy('widgets-core', '001', 'widget'),
+    ...scopeFiles('shop', '', 'widget'),
+    ...coreWithScopeTypes(['standard']),
+  });
+  expect(activationErrors(lintWorkspace(workspaceRoot, { ignoreExternal: false }))).toBe('');
+});
+
+test('does not report a disabled scope extending a scope with an invalid index [022.06]', () => {
+  const workspaceRoot = createWorkspace('activation-disabled-extends-invalid', {
+    '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope lib](lib/index.md)', '[View scope mid](mid/index.md) `disabled`', ACTIVATION_LEGEND]),
+    ...scopeFiles('lib'),
+    '.xdrs/lib/index.md': '# lib without frontmatter\n',
+    ...scopeFiles('mid', 'extends: lib\n'),
+  });
+  expect(activationErrors(lintWorkspace(workspaceRoot, { ignoreExternal: false }))).not.toContain('Local scope "mid" is frozen');
+});
+
+test('does not report a disabled external scope extending a disabled or missing scope [022.06]', () => {
+  const workspaceRoot = createWorkspace('activation-disabled-external-extends', {
+    '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope lib](lib/index.md) `disabled`', '[View scope vendor](vendor/index.md) `disabled`', ACTIVATION_LEGEND]),
+    ...scopeFiles('lib'),
+    ...scopeFiles('vendor', 'extends: lib, ghost-lib\n'),
+    '.filedist.lock': '.xdrs/vendor/index.md|some-package|1.0.0\n',
+  });
+  expect(activationErrors(lintWorkspace(workspaceRoot, { ignoreExternal: false }))).toBe('');
+});
+
+test('does not report a disabled scope with extends-only: true extending a disabled scope [022.06]', () => {
+  const workspaceRoot = createWorkspace('activation-disabled-extends-only-field', {
+    '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope lib](lib/index.md) `disabled`', '[View scope mid](mid/index.md) `disabled`', ACTIVATION_LEGEND]),
+    ...scopeFiles('lib'),
+    ...scopeFiles('mid', 'extends: lib\nextends-only: true\n'),
+  });
+  expect(activationErrors(lintWorkspace(workspaceRoot, { ignoreExternal: false }))).toBe('');
+});
+
+test('reports only the enabled extender in the chain enabled -> disabled -> disabled [022.06]', () => {
+  const workspaceRoot = createWorkspace('activation-chain-enabled-disabled-disabled', {
+    '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope lib](lib/index.md) `disabled`', '[View scope mid](mid/index.md) `disabled`', '[View scope myteam](myteam/index.md)', ACTIVATION_LEGEND]),
+    ...scopeFiles('lib'),
+    ...scopeFiles('mid', 'extends: lib\n'),
+    ...scopeFiles('myteam', 'extends: mid\n'),
+  });
+  const errors = activationErrors(lintWorkspace(workspaceRoot, { ignoreExternal: false }));
+  expect(errors).toContain('Local scope "myteam" is frozen (read-only) because extends: scope "mid" is tagged `disabled`');
+  expect(errors).not.toContain('Local scope "mid"');
+});
+
+test('reports only the direct extender in the chain enabled -> enabled -> disabled [022.06]', () => {
+  const workspaceRoot = createWorkspace('activation-chain-enabled-enabled-disabled', {
+    '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope lib](lib/index.md) `disabled`', '[View scope mid](mid/index.md)', '[View scope myteam](myteam/index.md)', ACTIVATION_LEGEND]),
+    ...scopeFiles('lib'),
+    ...scopeFiles('mid', 'extends: lib\n'),
+    ...scopeFiles('myteam', 'extends: mid\n'),
+  });
+  const errors = activationErrors(lintWorkspace(workspaceRoot, { ignoreExternal: false }));
+  expect(errors).toContain('Local scope "mid" is frozen (read-only) because extends: scope "lib" is tagged `disabled`');
+  expect(errors).not.toContain('Local scope "myteam"');
+});
+
+test('still reports an enabled scope extending a missing scope [010.32]', () => {
+  const workspaceRoot = createWorkspace('activation-enabled-extends-missing', {
+    '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope myteam](myteam/index.md)']),
+    ...scopeFiles('myteam', 'extends: ghost-lib\n'),
+  });
+  const errors = lintWorkspace(workspaceRoot, { ignoreExternal: false }).errors.join('\n');
+  expect(errors).toContain('extends references scope "ghost-lib" which does not exist in the workspace');
+});
+
+test('still reports extends cycles and self-extends in disabled scopes [010.30, 010.31]', () => {
+  const workspaceRoot = createWorkspace('activation-disabled-structural', {
+    '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope a](a/index.md) `disabled`', '[View scope b](b/index.md) `disabled`', '[View scope c](c/index.md) `disabled`', ACTIVATION_LEGEND]),
+    ...scopeFiles('a', 'extends: b\n'),
+    ...scopeFiles('b', 'extends: a\n'),
+    ...scopeFiles('c', 'extends: c\n'),
+  });
+  const errors = lintWorkspace(workspaceRoot, { ignoreExternal: false }).errors.join('\n');
+  expect(errors).toContain('Circular extends chain detected');
+  expect(errors).toContain('must not reference the scope itself');
+});
+
+test('still reports a disabled scope following a non-core scope [001]', () => {
+  const workspaceRoot = createWorkspace('activation-disabled-follows-non-core', {
+    '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope lib](lib/index.md)', '[View scope mid](mid/index.md) `disabled`', ACTIVATION_LEGEND]),
+    ...scopeFiles('lib'),
+    ...scopeFiles('mid', 'follows: lib\n'),
+  });
+  const errors = lintWorkspace(workspaceRoot, { ignoreExternal: false }).errors.join('\n');
+  expect(errors).toContain('follows references scope "lib" which is not a core-type scope');
+});
+
+test('reports an enabled scope type defined only in a disabled scope as frozen while a disabled user is exempt [022.06]', () => {
+  const workspaceRoot = createWorkspace('activation-type-enabled-vs-disabled-user', {
+    '.xdrs/index.md': rootIndex(['[_core](_core/index.md)', '[View scope widgets-core](widgets-core/index.md) `disabled`', '[View scope shop](shop/index.md)', '[View scope kiosk](kiosk/index.md) `disabled`', ACTIVATION_LEGEND]),
+    '.xdrs/widgets-core/index.md': scopeIndexWith('widgets-core', '', 'core'),
+    '.xdrs/widgets-core/adrs/index.md': teamAdrIndex(['- [001-widget-scope-type](principles/001-widget-scope-type.md) - Widget type']),
+    '.xdrs/widgets-core/adrs/principles/001-widget-scope-type.md': structuredScopeTypePolicy('widgets-core', '001', 'widget'),
+    ...scopeFiles('shop', '', 'widget'),
+    ...scopeFiles('kiosk', '', 'widget'),
+    ...coreWithScopeTypes(['standard']),
+  });
+  const errors = activationErrors(lintWorkspace(workspaceRoot, { ignoreExternal: false }));
+  expect(errors).toContain('Local scope "shop" is frozen (read-only)');
+  expect(errors).not.toContain('Local scope "kiosk"');
 });
 
 test('prints frozen local scopes as errors and never prints warning or READ-ONLY lines [022.06]', () => {
@@ -6048,3 +6179,161 @@ test('accepts compiled combined with a non-core type [011.10]', () => {
   const result = lintWorkspace(workspaceRoot, { ignoreExternal: false });
   expect(result.errors.join('\n')).not.toContain('011.10');
 });
+
+// ---------------------------------------------------------------------------
+// sync-date frontmatter (_core-adr-policy-024)
+// ---------------------------------------------------------------------------
+
+const SYNC_DATE_ERRORS = (result) => result.errors.filter((e) => e.includes('sync-date')).join('\n');
+
+function syncDatePolicy(extraFrontmatter) {
+  return [
+    '---',
+    'name: _local-adr-policy-001-main',
+    'description: Test XDRS element',
+    'apply-to: All scopes',
+    'valid-from: 2026-01-01',
+    ...extraFrontmatter,
+    '---',
+    '',
+    '# _local-adr-policy-001: Main decision',
+    '',
+    '## Context and Problem Statement',
+    '',
+    'Test body.',
+    '',
+    '## Decision Outcome',
+    '',
+    'Test decision outcome.',
+    ''
+  ].join('\n');
+}
+
+test('accepts a valid sync-date in Policy frontmatter', () => {
+  const workspaceRoot = createWorkspace('syncd-policy-valid', {
+    '.xdrs/index.md': rootIndex(),
+    '.xdrs/_local/adrs/index.md': localAdrIndex(['- [001-main](principles/001-main.md) - Main decision']),
+    '.xdrs/_local/adrs/principles/001-main.md': syncDatePolicy(['sync-date: 2026-11-04']),
+  });
+
+  const result = lintWorkspace(workspaceRoot);
+
+  expect(SYNC_DATE_ERRORS(result)).toBe('');
+  expect(result.errors.join('\n')).not.toContain('unknown field');
+});
+
+test('reports invalid and empty sync-date in Policy frontmatter', () => {
+  for (const [name, value] of [['syncd-policy-invalid', 'sync-date: yesterday'], ['syncd-policy-empty', 'sync-date:'], ['syncd-policy-quoted', 'sync-date: "2026-11-04"']]) {
+    const workspaceRoot = createWorkspace(name, {
+      '.xdrs/index.md': rootIndex(),
+      '.xdrs/_local/adrs/index.md': localAdrIndex(['- [001-main](principles/001-main.md) - Main decision']),
+      '.xdrs/_local/adrs/principles/001-main.md': syncDatePolicy([value]),
+    });
+
+    const result = lintWorkspace(workspaceRoot);
+
+    expect(SYNC_DATE_ERRORS(result)).toContain('Policy frontmatter sync-date must be a valid ISO date YYYY-MM-DD');
+  }
+});
+
+test('reports sync-date in a Policy of a compiled scope', () => {
+  const policy = validCompiledPolicy().replace('valid-from: 2026-01-01\n', 'valid-from: 2026-01-01\nsync-date: 2026-11-04\n');
+  const workspaceRoot = createWorkspace('syncd-compiled-policy', {
+    '.xdrs/index.md': rootIndex(['[my-compiled](my-compiled/index.md)']),
+    '.xdrs/my-compiled/index.md': compiledScopeIndex(),
+    '.xdrs/my-compiled/adrs/index.md': compiledAdrIndex(['- [001-a01](principles/001-a01.md) - A01']),
+    '.xdrs/my-compiled/adrs/principles/001-a01.md': policy,
+  });
+
+  const result = lintWorkspace(workspaceRoot);
+
+  expect(SYNC_DATE_ERRORS(result)).toContain('024.07-compiled-scopes');
+});
+
+test('accepts sync-date in the scope index of a compiled scope', () => {
+  const workspaceRoot = createWorkspace('syncd-compiled-scope-index', {
+    '.xdrs/index.md': rootIndex(['[my-compiled](my-compiled/index.md)']),
+    '.xdrs/my-compiled/index.md': compiledScopeIndex().replace('valid-from: 2026-01-01\n', 'valid-from: 2026-01-01\nsync-date: 2026-11-04\n'),
+    '.xdrs/my-compiled/adrs/index.md': compiledAdrIndex(['- [001-a01](principles/001-a01.md) - A01']),
+    '.xdrs/my-compiled/adrs/principles/001-a01.md': validCompiledPolicy(),
+  });
+
+  const result = lintWorkspace(workspaceRoot);
+
+  expect(SYNC_DATE_ERRORS(result)).toBe('');
+  expect(result.errors.join('\n')).not.toContain('unknown field');
+});
+
+test('reports invalid sync-date in scope index frontmatter', () => {
+  const workspaceRoot = createWorkspace('syncd-scope-index-invalid', {
+    '.xdrs/index.md': rootIndex(['[myteam](myteam/index.md)']),
+    '.xdrs/myteam/index.md': '---\nscope-type: standard\nname: myteam\ndescription: Team.\napply-to: Test team\nvalid-from: 2026-01-01\nsync-date: 2026-13-45\n---\n\n# myteam Scope Overview\n\n[ADRs](adrs/index.md)\n',
+    '.xdrs/myteam/adrs/index.md': teamAdrIndex(['- [001-team](principles/001-team.md) - Team decision']),
+    '.xdrs/myteam/adrs/principles/001-team.md': teamXdrDocument('Team decision.'),
+  });
+
+  const result = lintWorkspace(workspaceRoot, { ignoreExternal: false });
+
+  expect(SYNC_DATE_ERRORS(result)).toContain('Scope index frontmatter sync-date must be a valid ISO date YYYY-MM-DD');
+});
+
+test('validates metadata.sync-date in SKILL.md frontmatter', () => {
+  const skillWith = (syncDate) => fullSkillDocument().replace(
+    'description: Test skill document\n---',
+    `description: Test skill document\nmetadata:\n  version: "1.0.0"\n  author: test\n  updated: 2026-11-04\n  sync-date: ${syncDate}\n---`
+  );
+  const build = (name, syncDate) => createWorkspace(name, {
+    '.xdrs/index.md': rootIndex(),
+    '.xdrs/_local/adrs/index.md': localAdrIndex(['- [check-links](principles/skills/check-links/SKILL.md) - Check links']),
+    '.xdrs/_local/adrs/principles/skills/check-links/SKILL.md': skillWith(syncDate),
+  });
+
+  const valid = lintWorkspace(build('syncd-skill-valid', '2026-11-04'));
+  const invalid = lintWorkspace(build('syncd-skill-invalid', 'soon'));
+
+  expect(SYNC_DATE_ERRORS(valid)).toBe('');
+  expect(SYNC_DATE_ERRORS(invalid)).toContain('SKILL.md frontmatter metadata.sync-date must be a valid ISO date YYYY-MM-DD');
+});
+
+test('accepts sync-date-only frontmatter in article, research and initiative documents', () => {
+  const fm = '---\nsync-date: 2026-11-04\n---\n\n';
+  const workspaceRoot = createWorkspace('syncd-docs-valid', {
+    '.xdrs/index.md': rootIndex(),
+    '.xdrs/_local/adrs/index.md': localAdrIndex([
+      '- [001-guide](principles/articles/001-guide.md) - Guide',
+      '- [001-study](principles/researches/001-study.md) - Study',
+      '- [001-myinitiative](principles/initiatives/001-myinitiative.md) - My initiative',
+    ]),
+    '.xdrs/_local/adrs/principles/articles/001-guide.md': fm + articleDocument('Body.'),
+    '.xdrs/_local/adrs/principles/researches/001-study.md': fm + researchDocument('Context.', 'Question: Is this right?'),
+    '.xdrs/_local/adrs/principles/initiatives/001-myinitiative.md': fm + initiativeDocument('Body.'),
+  });
+
+  const result = lintWorkspace(workspaceRoot);
+
+  expect(SYNC_DATE_ERRORS(result)).toBe('');
+  expect(result.errors.join('\n')).not.toContain('title must start with');
+  expect(result.errors.join('\n')).not.toContain('frontmatter');
+});
+
+test('reports unknown, missing and invalid frontmatter fields in article, research and initiative documents', () => {
+  const workspaceRoot = createWorkspace('syncd-docs-invalid', {
+    '.xdrs/index.md': rootIndex(),
+    '.xdrs/_local/adrs/index.md': localAdrIndex([
+      '- [001-guide](principles/articles/001-guide.md) - Guide',
+      '- [001-study](principles/researches/001-study.md) - Study',
+      '- [001-myinitiative](principles/initiatives/001-myinitiative.md) - My initiative',
+    ]),
+    '.xdrs/_local/adrs/principles/articles/001-guide.md': '---\nsync-date: 2026-11-04\nauthor: me\n---\n\n' + articleDocument('Body.'),
+    '.xdrs/_local/adrs/principles/researches/001-study.md': '---\nsync-date: never\n---\n\n' + researchDocument('Context.', 'Question: Is this right?'),
+    '.xdrs/_local/adrs/principles/initiatives/001-myinitiative.md': '---\nauthor: me\n---\n\n' + initiativeDocument('Body.'),
+  });
+
+  const result = lintWorkspace(workspaceRoot);
+  const errors = result.errors.join('\n');
+
+  expect(errors).toContain('Article frontmatter has unknown field "author" (only sync-date is allowed)');
+  expect(errors).toContain('Research frontmatter sync-date must be a valid ISO date YYYY-MM-DD');
+  expect(errors).toContain('Initiative frontmatter has unknown field "author" (only sync-date is allowed)');
+  expect(errors).toContain('Initiative frontmatter must include a sync-date field when present');
+});

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "xdrs-core",
-  "version": "0.56.0",
+  "version": "0.56.1",
   "description": "XDRS (eXtensible Decision Record System): a framework to structure, compile and distribute Architectural (ADR), Business (BDR), and Engineering (EDR) decision records contents so that AI agents and humans can reliably find and use them with hierarchical scopes and controlled rollout in the format of distributable versioned packages.",
   "repository": {
     "type": "git",