Christopher Clendening
96b7ff9766
- Create SECURITY.md to outline security policies and practices. - Establish WORKFLOW.md detailing the project lifecycle from planning to retrospective. - Introduce decision log structure in decisions/README.md for tracking architecture decisions. - Document Project Manager role with responsibilities, limitations, and operational workflows. - Implement templates for ADRs, bugs, meetings, projects, retrospectives, RFCs, roadmaps, and sprints. - Set up memory logs for architecture and company-wide lessons learned. - Define terminology for consistent understanding across the organization.
24 lines
1003 B
Markdown
24 lines
1003 B
Markdown
# Projects
|
|
|
|
Each real project the company works on gets its own folder here, following
|
|
[../templates/PROJECT.md](../templates/PROJECT.md), plus its own repository under the
|
|
organization in Gitea (`../GITEA.md`) — this repository (`Local-LLC`) is the operating system,
|
|
not where project code lives.
|
|
|
|
A project folder is created by the Project Manager once its Epic has cleared the Founder's
|
|
approval gate (`../FOUNDER.md`) and the CEO has created the Epic in Plane (`../PLANE.md`) — not
|
|
before. There are no projects yet; this repository is still at the organization-definition
|
|
stage described in `../README.md`'s versioning table (v0.1).
|
|
|
|
## Structure
|
|
|
|
```
|
|
projects/
|
|
└── <project-name>/
|
|
└── PROJECT.md following ../templates/PROJECT.md
|
|
```
|
|
|
|
Keep each project's folder minimal — it's a pointer and a summary, not a duplicate of what
|
|
already lives in Plane (state) or the project's own Gitea repo (code, project-specific docs).
|
|
See the source-of-truth table in `../COMPANY.md`.
|