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

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
+1 -1
View File
@@ -2,7 +2,7 @@
dir: .stoneforge
## role
Internal configuration and state tracking directory for the Stoneforge application
Infrastructure configuration and metadata storage for the Stoneforge tool
## parent
index: ./.pi-map.index.md
map: ./.pi-map.md
+6 -6
View File
@@ -4,15 +4,15 @@ dir: .stoneforge
index: .stoneforge/.pi-map.index.md
## role
Internal configuration and state tracking directory for the Stoneforge application
Infrastructure configuration and metadata storage for the Stoneforge tool
## files
- .dashboard-opened | Stores timestamp and identifier data for tracking when a dashboard was opened
- .gitignore | Specifies files and patterns for Git to ignore in version control
- config.yaml | Configuration file for the Stoneforge application defining database, sync, playbook, identity, merge, workflow, and agent settings.
- .dashboard-opened | Stores timestamp metadata for tracking when a dashboard was opened
- .gitignore | Specifies files and patterns for Git to ignore in the repository | dep: git
- config.yaml | YAML configuration file defining settings for the Stoneforge tool, including database, sync, playbooks, identity, merge, workflow, and agent permissions.
## arch
Simple dot-directory pattern storing metadata (.dashboard-opened), version control exclusions (.gitignore), and hierarchical YAML configuration (config.yaml) with domain-separated settings
Dot-directory pattern for tool-specific state, using YAML for hierarchical configuration and dotfiles for ephemeral runtime metadata
## tags
config, stores, timestamp, identifier, data, tracking, dashboard, was
git, config, stores, timestamp, metadata, tracking, dashboard, was
## symbols
-
## workflows
+1 -1
View File
@@ -2,7 +2,7 @@
dir: .stoneforge/sync
## role
Persists distributed task execution state by storing dependency graphs and ephemeral worker agent records for a collaborative workflow system.
Provides persistent storage for entity relationships and AI worker agent records in a synchronization system.
## parent
index: .stoneforge/.pi-map.index.md
map: .stoneforge/.pi-map.md
+5 -5
View File
@@ -4,14 +4,14 @@ dir: .stoneforge/sync
index: .stoneforge/sync/.pi-map.index.md
## role
Persists distributed task execution state by storing dependency graphs and ephemeral worker agent records for a collaborative workflow system.
Provides persistent storage for entity relationships and AI worker agent records in a synchronization system.
## files
- dependencies.jsonl | Stores a sequence of dependency relationships between entities in JSON Lines format, tracking parent-child, blocking, and reply relationships with timestamps and creators.
- elements.jsonl | Stores JSONL records of ephemeral worker agents with their session history, worktree assignments, and lifecycle metadata for a distributed task execution system.
- dependencies.jsonl | Stores dependency relationships between entities in JSONL format, including parent-child, blocking, and reply-to relationships with timestamps and creators.
- elements.jsonl | Stores JSONL-formatted entity records for AI worker agents with their session histories and metadata in a data persistence file.
## arch
Event-sourced JSONL append-only logs with entity-relationship modeling (parent-child, blocking, reply) and session-based worker lifecycle tracking.
Append-only JSONL document store with separate files for dependency graph edges (dependencies.jsonl) and entity nodes (elements.jsonl), using a log-structured data pattern for time-ordered, immutable record keeping.
## tags
stores, relationships, dependencies, elements, sequence, dependency, entities, json
stores, relationships, jsonl, dependencies, elements, dependency, entities, format
## symbols
-
## workflows