christopher/Local-LLC
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add ML and QA Engineer documentation and workflows

Browse Source 
- Introduced ML Engineer role with detailed responsibilities, success metrics, and workflow documentation.
- Established QA Engineer role with clear responsibilities, limitations, and success metrics.
- Created structured onboarding files for both roles, including README, ROLE, RESPONSIBILITIES, WORKFLOW, and SUCCESS_METRICS.
- Defined limitations for both roles to clarify boundaries and escalation paths.
- Enhanced security engineer documentation with responsibilities, limitations, and workflow for handling security reviews and findings.
This commit is contained in:
Christopher Clendening
2026-07-30 14:02:50 -04:00
parent 6405f84a2c
commit 038442d4fd
65 changed files with 2592 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+16 -7
View File
@@ -41,13 +41,22 @@ Local-LLC/
├── memory/ company-wide memory: architecture, lessons, terminology
├── projects/ one folder per real project, following templates/PROJECT.md
└── employees/
└── project-manager/ full reference role — read this before building the rest
├── project-manager/ full reference role — read this before building the rest
├── architect/ technical direction, ADRs, disagreement resolution
├── backend/ server-side / API / data-layer implementation
├── frontend/ user-facing interface implementation
├── ml/ model training, evaluation, ML infrastructure
├── qa/ independent verification; standing reject authority
├── security/ security review; standing merge-hold authority
├── devops/ CI/CD (ACT Runner), deployment pipelines
└── documentation/ keeps this repo and project docs accurate over time
```
Additional `employees/<role>/` folders (architect, backend, frontend, ml, qa, security,
devops, documentation) will be added following the same pattern as `project-manager/`.
`project-manager/` exists first because every other role's work arrives through Plane, which
the Project Manager owns operationally.
Every `employees/<role>/` folder follows the same eight-file pattern established by
`project-manager/` (`README.md`, `ROLE.md`, `RESPONSIBILITIES.md`, `LIMITATIONS.md`,
`WORKFLOW.md`, `PROMPT.md`, `MEMORY.md`, `SUCCESS_METRICS.md`) — `project-manager/` was built
first because every other role's work arrives through Plane, which the Project Manager owns
operationally.
## What's real right now
@@ -65,8 +74,8 @@ This repo is versioned like software, not written once and frozen:
| Version | Milestone |
|---|---|
| **v0.1 — current** | Organization defined: all 14 root policy docs, 8 templates, the decision log, company memory seed files, and the Project Manager role fully built as the reference pattern |
| v0.2 | Remaining employee roles fleshed out (Architect, Backend, Frontend, ML, QA, Security, DevOps, Documentation) |
| v0.1 | Organization defined: all 14 root policy docs, 8 templates, the decision log, company memory seed files, and the Project Manager role built as the reference pattern |
| **v0.2 — current** | All nine employee roles fully built out (Project Manager, Architect, Backend, Frontend, ML, QA, Security, DevOps, Documentation) |
| v0.3 | Plane deployed and wired to the workflow described in PLANE.md |
| v0.4 | Gitea/ACT Runner placeholders replaced with real instance details |
| v0.5 | First real project run end-to-end through the full sprint lifecycle |