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/.pi-map.md
+8 -22
View File
@@ -1,31 +1,17 @@
# .
dir: .
# openspec
dir: openspec
index: ./.pi-map.index.md
## Project Map Protocol
1. Read this protocol and the root `.pi-map.index.md` first.
2. Use `index:` / `map:` references to open relevant directory indexes and maps.
3. Load indexes before rich maps during task-start navigation.
4. Read the local rich map and actual source before editing.
5. Treat non-empty `## dirty` sections in either artifact as stale.
6. If source and generated artifacts disagree, trust source.
7. If map and index disagree, trust neither blindly; verify from source and regenerate the pair.
8. After editing source, run `project_map_patch` for each changed file.
9. Before broad architectural claims or final handoff, run `project_map_validate` when freshness matters.
Trust boundary: index routes, map orients, source decides.
index: openspec/.pi-map.index.md
## role
Defines a living documentation methodology and project configuration for managing software requirements, specifications, and development discipline rules within a Docker-based coding agent platform.
Defines the OpenSpec methodology and project configuration for managing living documentation, requirements, and development workflows.
## files
- README.md | Documents the OpenSpec methodology for managing software requirements, specifications, and task tracking as living documentation within a project repository. | dep: OpenSpec CLI (@fission-ai/openspec), Docker, SQLAlchemy, Alembic, Authentik, React, TypeScript, Tailwind, Traefik, Jinja2, xterm.js, pytest, mypy, ruff, npm
- config.yaml | Configuration file defining project metadata, technology stack, and software development discipline rules for a Docker-based coding agent management platform | dep: FastAPI, React, Vite, PostgreSQL, SQLAlchemy, Redis, Alembic, pytest, Docker Compose, Traefik, Authentik
- README.md | Documents the OpenSpec methodology for managing requirements, specifications, and task tracking as living documentation within the repository | dep: OpenSpec CLI, npx, AGENTS.md
- config.yaml | Configuration file defining a Docker-based development platform project with technology stack, SDD methodology settings, and strict TDD enforcement rules | dep: FastAPI, PostgreSQL, Redis, Alembic, React, Vite, Docker Compose, Traefik, Authentik, pytest, SQLAlchemy
## arch
Documentation-as-code pattern with YAML-based declarative configuration separating project metadata, technology stack definitions, and behavioral rules for automated agent orchestration.
Documentation-as-code pattern with YAML-based configuration enforcing Docker-centric development, strict TDD, and SDD (Specification-Driven Development) methodology.
## tags
software, project, docker, sqlalchemy, alembic, authentik, react, traefik
methodology, readme, config, documents, openspec, managing, requirements, specifications
## symbols
-
## workflows