alex/headquarter
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(project-map): regenerate .pi-map artifacts across the repo

Browse Source
This commit is contained in:
Developer
2026-06-17 11:31:24 +00:00
parent 0dd5f2317b
commit 93da9b42a2
683 changed files with 5075 additions and 4965 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/archive/2026-05-25-add-config-profiles/specs/config-profiles/.pi-map.md
+6 -6
View File
@@ -1,14 +1,14 @@
# 2026-05-25-add-config-profiles/specs/config-profiles
dir: 2026-05-25-add-config-profiles/specs/config-profiles
# openspec/changes/archive/2026-05-25-add-config-profiles/specs/config-profiles
dir: openspec/changes/archive/2026-05-25-add-config-profiles/specs/config-profiles
index: 2026-05-25-add-config-profiles/specs/config-profiles/.pi-map.index.md
index: openspec/changes/archive/2026-05-25-add-config-profiles/specs/config-profiles/.pi-map.index.md
## role
Defines requirements for a user-owned configuration profile management system supporting scoped compatibility, content storage, ordered includes, resolution layering, and default selection for launch configurations.
Defines specifications for a user-managed configuration profile system enabling scoped, layered, and ordered configuration resolution with default profile selection for launch scenarios.
## files
- spec.md | Defines system requirements for a user-owned config profile management system with scoped compatibility, content storage, ordered includes, resolution layering, and default selection for launch configurations.
- spec.md | Defines system requirements for a user-owned config profile management system with scoped compatibility, ordered includes, layered resolution, and default selection for launch configurations.
## arch
Specification-driven design using layered resolution architecture with profile scoping, content-addressable storage, ordered dependency chains (includes), and precedence-based default selection for launch-time configuration resolution.
Specification-driven requirements document using hierarchical feature decomposition (core concepts → profiles → resolution → includes → defaults → compatibility → lifecycle) with explicit constraint notation and YAML-like examples for behavioral contracts.
## tags
system, spec, defines, requirements, user, owned, config, profile
## symbols