alex/headquarter
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
070cd4d5a5db70622b780b953a1c773c2d5602d3
headquarter/openspec/changes/working-copies/.pi-map.md
T
Developer 070cd4d5a5 chore: track all project map and index files 
Add generated .pi-map.md and .pi-map.index.md files across the repository
so the project navigation maps are shared and versioned. These artifacts
are maintained by project_map_init/patch/validate and must be kept in
sync with source edits.

Note: .cache/ remains ignored (added in previous commit).
2026-06-12 13:46:23 +00:00

2.0 KiB
Raw Blame History

openspec/changes/working-copies

dir: openspec/changes/working-copies

index: openspec/changes/working-copies/.pi-map.index.md

role

Defines a workspace-based architecture to replace direct repository mounting/cloning with persistent, shareable git working copies for tool instances.

files

  • design.md | Design document for implementing workspace-based tool instances that replace direct repository mounting with isolated git working copies | dep: FastAPI, SQLAlchemy, Alembic, Docker Compose, Git, React/TypeScript, asyncio subprocess
  • explore.md | Design document proposing "Working Copies" (named "Workspace") as persistent writable clones of repositories to replace direct repo mounting/cloning in tool instances | dep: GitRepository, ToolInstance, Project, User, database, compose generation, filesystem mount system
  • proposal.md | Proposes a new "Workspace" entity to replace the confusing mount/clone mode dichotomy for tool instances, enabling persistent writable repository clones that multiple tools can share.
  • spec.md | Technical specification for implementing persistent workspace-based tool instances that replace mount/clone modes with explicit Git repository workspaces | dep: Git, PostgreSQL, REST API, React/TypeScript frontend, Docker containers, Python backend
  • tasks.md | A project task breakdown document defining a phased implementation plan for adding workspace-based tool instances to a full-stack application, including backend foundation, backend integration, frontend core, and frontend integration PRs with detailed tasks, acceptance criteria, and verification steps. | dep: Alembic, FastAPI, SQLAlchemy, React, TypeScript, Git, Docker Compose, pytest, ruff, ESLint, npm

arch

Design-driven development with layered specification documents (exploration → proposal → design → spec → tasks) transitioning from conceptual "Workspace" entity to phased full-stack implementation across backend and frontend.

tags

workspace, tool, instances, git, design, replace, document, repository

symbols

workflows

dirty

Reference in New Issue View Git Blame Copy Permalink