xdrs-core 0.2.14 → 0.2.15

package/.xdrs/{_general → _core}/adrs/index.md

@@ -8,5 +8,5 @@ This index lists all ADRs for the general scope, organized by subject.
 
 Foundational standards, principles, and guidelines.
 
-- [_general-adr-001](principles/001-xdr-standards.md) - **XDR standards** (includes XDR template)
-- [_general-adr-003](principles/003-skill-standards.md) - **Skill standards**
+- [_core-adr-001](principles/001-xdr-standards.md) - **XDR standards** (includes XDR template)
+- [_core-adr-003](principles/003-skill-standards.md) - **Skill standards**

package/.xdrs/{_general → _core}/adrs/principles/001-xdr-standards.md

@@ -1,4 +1,4 @@
-# _general-adr-001: XDR standards
+# _core-adr-001: XDR standards
 
 ## Context and Problem Statement
 
@@ -28,7 +28,7 @@ Provides clear ownership by scope, predictable navigation, and reusable decision
 - Always the following folder structure:
   `.xdrs/[scope]/[type]/[subject]/[number]-[short-title].md`
 - **Scopes:** 
-  - examples: `business-x`, `business-y`, `team-43`, `_general`
+  - examples: `business-x`, `business-y`, `team-43`, `_core`
   - `_local` is a reserved scope for XDRs created locally to a specific project or repository. XDRs in `_local` must not be shared with or propagated to other contexts. This scope must always be placed in the lowest position in `.xdrs/index.md` so that its decisions override or extend any decisions from all higher-positioned scopes.
   - **Types:** `adrs`, `bdrs`, `edrs`
   - there can exist sufixes to the standard scope names (e.g: `business-x-mobileapp`, `business-y-servicedesk`)
@@ -111,7 +111,7 @@ In the end, state explicitly the question that needs to be answered. E.g: "Which
 **Examples:**
 - `.xdrs/business-x/edrs/devops/003-required-development-workflow.md`
 - `.xdrs/business-x/adrs/governance/010-security-and-secrets-management.md`
-- `.xdrs/_general/adrs/devops/001-multi-repo.md`
+- `.xdrs/_core/adrs/devops/001-multi-repo.md`
 
 **XDR ID Examples:**
 - `business-x-adr-001` (not `ADR-business-x-001` or `business-x-adr-1`)

package/.xdrs/{_general → _core}/adrs/principles/003-skill-standards.md

@@ -1,4 +1,4 @@
-# _general-adr-003: Skill standards
+# _core-adr-003: Skill standards
 
 ## Context and Problem Statement
 
@@ -39,7 +39,7 @@ Quick test:
 ```
 
 Examples:
-- `.xdrs/_general/adrs/principles/skills/001-code-review/SKILL.md`
+- `.xdrs/_core/adrs/principles/skills/001-code-review/SKILL.md`
 - `.xdrs/business-x/edrs/devops/skills/001-ci-pipeline-debug/SKILL.md`
 - `.xdrs/_local/adrs/principles/skills/001-my-nice-skill/SKILL.md`
 
@@ -108,4 +108,4 @@ skills-ref validate .xdrs/[scope]/[type]/[subject]/skills/[number]-[skill-name]
 - [agentskills specification](https://agentskills.io/specification)
 - [agentskills/agentskills repository](https://github.com/agentskills/agentskills)
 - [skills-ref validation library](https://github.com/agentskills/agentskills/tree/main/skills-ref)
-- [_general-adr-001 - XDR standards](001-xdr-standards.md)
+- [_core-adr-001 - XDR standards](001-xdr-standards.md)

package/.xdrs/{_general → _core}/adrs/principles/skills/001-xdr-lint/SKILL.md

@@ -105,6 +105,6 @@ produces structured findings report.
 
 ## References
 
-- [_general-adr-001 - XDR standards](../../001-xdr-standards.md)
-- [_general-adr-003 - Skill standards](../../003-skill-standards.md)
+- [_core-adr-001 - XDR standards](../../001-xdr-standards.md)
+- [_core-adr-003 - Skill standards](../../003-skill-standards.md)
 

package/.xdrs/{_general → _core}/edrs/index.md

@@ -6,5 +6,5 @@ General engineering decisions covering cross-business standards and practices. A
 
 Foundational standards, principles, and guidelines.
 
-- [_general-edr-001](principles/001-coding-agent-behavior.md) - **AI coding agent behavior**
+- [_core-edr-001](principles/001-coding-agent-behavior.md) - **AI coding agent behavior**
 

package/.xdrs/{_general → _core}/edrs/principles/001-coding-agent-behavior.md

@@ -1,4 +1,4 @@
-# _general-edr-001: AI coding agent behavior
+# _core-edr-001: AI coding agent behavior
 
 ## Context and Problem Statement
 
@@ -17,7 +17,7 @@ Clear behavior standards ensure consistency through EDR compliance, maintain cod
 **Mandatory behaviors for AI coding agents:**
 
 1. **Always consult XDRs before making implementation decisions**
-   - Follow coding agent behavior and decision hierarchy rules in [.xdrs/_general/edrs/principles/001-coding-agent-behavior.md](.xdrs/_general/edrs/principles/001-coding-agent-behavior.md)
+   - Follow coding agent behavior and decision hierarchy rules in [.xdrs/_core/edrs/principles/001-coding-agent-behavior.md](.xdrs/_core/edrs/principles/001-coding-agent-behavior.md)
    - Search for XDRs in [.xdrs/index.md](.xdrs/index.md) during design, plan and implementation steps
    - Follow XDRs as the source of truth for all decisions and procedures
 

package/.xdrs/index.md

@@ -6,24 +6,19 @@ This index points to all type- and scope-specific XDR indexes. XDRs (Decision Re
 
 XDRs in scopes listed last override the ones listed first
 
-### ADRs - general
+### _core
 
-General architectural decisions covering cross-business standards and practices.
+Decisions about how XDRs work
+[View general ADRs Index](_core/adrs/index.md)
 
-[View general ADRs Index](_general/adrs/index.md)
-
-### EDRs - general
-
-General engineering decisions covering cross-business standards and practices.
-
-[View general EDRs Index](_general/edrs/index.md)
+Decisions about how XDRs work
+[View general EDRs Index](_core/edrs/index.md)
 
 ---
 
-### EDRs - agentkit
+### agentkit
 
 General engineering decisions from agentkit scope
-
 [View agentkit EDRs Index](agentkit/edrs/index.md)
 
 ---

package/AGENTS.md

@@ -3,9 +3,9 @@
 **Purpose:** This file is intentionally brief. All project decisions and working instructions are captured as XDRs.
 
 1. **Always consult XDRs before making implementation decisions**
-   - Follow coding agent behavior and decision hierarchy rules in [.xdrs/_general/edrs/principles/001-coding-agent-behavior.md](.xdrs/_general/edrs/principles/001-coding-agent-behavior.md)
-   - Search for XDRs in [.xdrs/index.md](.xdrs/index.md) during design, plan and implementation steps
-   - Follow XDRs as the source of truth for all decisions and procedures
+   - You MUST follow coding agent behavior and decision hierarchy rules in [.xdrs/_core/edrs/principles/001-coding-agent-behavior.md](.xdrs/_core/edrs/principles/001-coding-agent-behavior.md)
+   - You MUST search and follow XDRs in [.xdrs/index.md](.xdrs/index.md) during design, plan, implementation, test and review steps
+   - You MUST follow XDRs as the source of truth for all decisions and procedures
 
 2. **Verify all work with build, tests and linting before completion**
    - Always run `make build`, `make lint-fix` and `make test` at the end of the implementation

package/README.md

@@ -28,7 +28,7 @@ This project defines a standard for organizing XDRs that satisfies the following
 
 ### Multi-scope support
 
-Different teams at different organizational levels make decisions that apply to different audiences. XDRs are organized by scope (e.g. `_general`, `business-x`, `business-y-mobileapp`) so that each team owns its own decision space. Scopes can extend or override decisions from broader scopes, with explicit precedence rules: scopes listed later in an index override those listed earlier.
+Different teams at different organizational levels make decisions that apply to different audiences. XDRs are organized by scope (e.g. `_core`, `business-x`, `business-y-mobileapp`) so that each team owns its own decision space. Scopes can extend or override decisions from broader scopes, with explicit precedence rules: scopes listed later in an index override those listed earlier.
 
 ### Subject grouping
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "xdrs-core",
-  "version": "0.2.14",
+  "version": "0.2.15",
   "description": "A standard way to organize Decision Records (XDRs) across scopes, subjects, and teams so that AI agents can reliably query and follow them.",
   "repository": {
     "type": "git",
@@ -20,7 +20,7 @@
     "bin/npmdata.js"
   ],
   "dependencies": {
-    "npmdata": "^0.13.4"
+    "npmdata": "^0.14.0"
   },
   "npmdata": {
     "sets": [