dsh-department 0.1.0 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +13 -0
- package/README.md +260 -228
- package/README.ru.md +287 -0
- package/client.js +339 -105
- package/package.json +3 -3
- package/README.en.md +0 -50
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,18 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.2
|
|
4
|
+
- Исправлено: русские переводы новых ключей (в т.ч. имя офиса в сайдбаре — «ИИ-отдел»).
|
|
5
|
+
- Проверка паритета словарей ru/en (226/226).
|
|
6
|
+
|
|
7
|
+
|
|
8
|
+
## 0.1.1
|
|
9
|
+
- Полная локализация интерфейса ru/en: карточка задачи, вкладки, стадии, события,
|
|
10
|
+
аудит, документы, роли, бюджет, офис, схема проекта, графики, формы.
|
|
11
|
+
- Переключатель языка EN/RU в шапке доски, выбор сохраняется.
|
|
12
|
+
- `dept_start release=true` — шаблон подготовки к релизу.
|
|
13
|
+
- GitHub Actions CI, docs/PUBLISHING.md.
|
|
14
|
+
|
|
15
|
+
|
|
3
16
|
## 0.1.0
|
|
4
17
|
|
|
5
18
|
- Первый публичный релиз: доска задач, карточка задачи, офис, гейты, git, бюджет, роли.
|
package/README.md
CHANGED
|
@@ -1,256 +1,288 @@
|
|
|
1
|
-
# dsh-department —
|
|
1
|
+
# dsh-department — AI development department for DeepSeek Harness
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
концепцию → ТЗ → план → этапы, а внутри этапа — реализацию, тесты, независимое ревью и
|
|
5
|
-
коммит с тегом. Человек утверждает только концепцию и ТЗ, остальное отдел решает сам
|
|
6
|
-
по политике автономии.
|
|
3
|
+
**English** · [Русский](README.ru.md)
|
|
7
4
|
|
|
8
|
-
|
|
5
|
+

|
|
6
|
+

|
|
7
|
+

|
|
9
8
|
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
файлы и история действий.
|
|
15
|
-
- **Схема проекта**: файлы и связи импортов по группам (папкам), drill-down до файла.
|
|
16
|
-
- **Бюджет**: расход токенов по сессиям, стоимость по ценам за 1M, лимит задачи.
|
|
17
|
-
- **Отчётность**: `dept_report` — этап, гейты, кто чем занят, открытые вопросы.
|
|
18
|
-
- **Вопросы к человеку** (`dept_ask` / `dept_answer`) — отдел не останавливается.
|
|
19
|
-
- **Поправки ТЗ** (`dept_amend`): с подписью человека или автономно (с лимитом).
|
|
20
|
-
- **Повторы по циклу** «данные → анализ → план → изменения → тесты»; повтор без анализа
|
|
21
|
-
блокируется, повторяющийся провал переводит этап в `blocked`.
|
|
22
|
-
- **Git**: коммит этапа, тег, push ветки и тегов; коммит заблокирован без свежих гейтов.
|
|
9
|
+
The plugin turns DeepSeek Harness into a **development department**: a task goes through
|
|
10
|
+
analysis → concept → specification → plan → stages, and inside each stage — implementation,
|
|
11
|
+
tests, independent review and a tagged commit. The human approves only the concept and the
|
|
12
|
+
specification; everything else the department decides itself under the autonomy policy.
|
|
23
13
|
|
|
24
|
-
##
|
|
14
|
+
## Screenshots
|
|
25
15
|
|
|
26
|
-
|
|
16
|
+
| Department panel (EN) | Office: working |
|
|
17
|
+
|---|---|
|
|
18
|
+
|  |  |
|
|
19
|
+
|
|
20
|
+
| Paused: everyone in the lounge | 16 characters |
|
|
21
|
+
|---|---|
|
|
22
|
+
|  |  |
|
|
23
|
+
|
|
24
|
+
## Features
|
|
25
|
+
|
|
26
|
+
- **Task board** across projects: stage, progress, gates, last event.
|
|
27
|
+
- **Task card** with tabs: overview, documents, questions, audit, events, corrections,
|
|
28
|
+
roles, budget, git; approval buttons, answers, amendments.
|
|
29
|
+
- **Department office**: who is working, at which desk, what they do; click — project,
|
|
30
|
+
task, files and action history.
|
|
31
|
+
- **Project blueprint**: files and import edges grouped by folders, drill-down to a file.
|
|
32
|
+
- **Budget**: token usage per session, cost by price per 1M, task limit.
|
|
33
|
+
- **Reporting**: `dept_report` — stage, gates, who is busy, open questions.
|
|
34
|
+
- **Questions to the human** (`dept_ask` / `dept_answer`) — the department does not stop.
|
|
35
|
+
- **Spec amendments** (`dept_amend`): human-signed or autonomous (with a limit).
|
|
36
|
+
- **Retries** by the loop data → analysis → plan → changes → tests; retry without analysis
|
|
37
|
+
is blocked; a repeated failure moves the stage to `blocked`.
|
|
38
|
+
- **Git**: stage commit, tag, push branch and tags; commit is blocked without fresh gates.
|
|
39
|
+
|
|
40
|
+
## Install
|
|
41
|
+
|
|
42
|
+
The plugin is installed into a DSH profile as a local (`link:`) package or from the registry:
|
|
27
43
|
|
|
28
44
|
```bash
|
|
29
45
|
dsh plugin add link:/path/to/dsh-department
|
|
46
|
+
# or from npm:
|
|
47
|
+
dsh plugin add dsh-department
|
|
30
48
|
```
|
|
31
49
|
|
|
32
|
-
|
|
33
|
-
|
|
50
|
+
Then enable the `dsh-department` bundle in the plugin manager and reload the tab.
|
|
51
|
+
The sidebar shows “Department”, the main window shows the board, office and blueprint.
|
|
34
52
|
|
|
35
|
-
##
|
|
53
|
+
## Model tools
|
|
36
54
|
|
|
37
|
-
|
|
|
55
|
+
| Tool | Purpose |
|
|
38
56
|
|---|---|
|
|
39
|
-
| `dept_start` |
|
|
40
|
-
| `dept_status` |
|
|
41
|
-
| `dept_stage` |
|
|
42
|
-
| `dept_approve` |
|
|
43
|
-
| `dept_gate` |
|
|
44
|
-
| `dept_verify` |
|
|
45
|
-
| `dept_commit` |
|
|
46
|
-
| `dept_amend` |
|
|
47
|
-
| `dept_ask` |
|
|
48
|
-
| `dept_answer` |
|
|
49
|
-
| `dept_report` |
|
|
50
|
-
| `dept_health` |
|
|
51
|
-
| `dept_modules` |
|
|
52
|
-
| `dept_art` |
|
|
53
|
-
| `dept_pixelize` | PNG/JPEG →
|
|
54
|
-
| `dept_compose` |
|
|
55
|
-
| `dept_roles` |
|
|
56
|
-
| `dept_bug` |
|
|
57
|
-
| `dept_browse` |
|
|
58
|
-
| `dept_gui` |
|
|
57
|
+
| `dept_start` | create a task: state, branch, task.md |
|
|
58
|
+
| `dept_status` | task state and summary |
|
|
59
|
+
| `dept_stage` | stage transition (except approvals) |
|
|
60
|
+
| `dept_approve` | human approval of concept/spec |
|
|
61
|
+
| `dept_gate` | tests gate (exit code) or review gate (PASS/FAIL) |
|
|
62
|
+
| `dept_verify` | audit: state ↔ artifacts ↔ git |
|
|
63
|
+
| `dept_commit` | stage commit, tag, push |
|
|
64
|
+
| `dept_amend` | document amendment (human-signed or `autonomous`) |
|
|
65
|
+
| `dept_ask` | question to the human without stopping work |
|
|
66
|
+
| `dept_answer` | human answer to a question |
|
|
67
|
+
| `dept_report` | department status report |
|
|
68
|
+
| `dept_health` | “is the department alive”: working / idle / waiting for human / ready to commit |
|
|
69
|
+
| `dept_modules` | module plan and file ownership for parallel work |
|
|
70
|
+
| `dept_art` | draw a pixel sprite and save a PNG |
|
|
71
|
+
| `dept_pixelize` | PNG/JPEG → pixel grid + palette + sprite (for redrawing from a reference) |
|
|
72
|
+
| `dept_compose` | compose a large PNG from small sprites (canvas, background, layers) |
|
|
73
|
+
| `dept_roles` | roles and models (researcher, designer, artist, senior-coder, supervisor, beta-tester, ...) |
|
|
74
|
+
| `dept_bug` | beta-tester bug report (steps, expected/actual, severity) |
|
|
75
|
+
| `dept_browse` | browser: open localhost/file, clicks, typing, screenshot into evidence |
|
|
76
|
+
| `dept_gui` | native app: command, env, timeout, output, screenshot via hook/command |
|
|
59
77
|
|
|
60
78
|
## HTTP API
|
|
61
79
|
|
|
62
|
-
|
|
|
80
|
+
| Route | Method | Purpose |
|
|
63
81
|
|---|---|---|
|
|
64
|
-
| `/api/department/tasks` | GET |
|
|
65
|
-
| `/api/department/task?root=&taskId=` | GET |
|
|
66
|
-
| `/api/department/activity` | GET |
|
|
67
|
-
| `/api/department/approve` | POST |
|
|
68
|
-
| `/api/department/answer` | POST |
|
|
69
|
-
| `/api/department/amend` | POST |
|
|
70
|
-
| `/api/department/budget?root=&taskId=` | GET/POST |
|
|
71
|
-
| `/api/department/blueprint?root=` | GET |
|
|
72
|
-
| `/api/department/asset?name=` | GET |
|
|
73
|
-
|
|
74
|
-
##
|
|
75
|
-
|
|
76
|
-
1.
|
|
77
|
-
2.
|
|
78
|
-
3.
|
|
79
|
-
4.
|
|
80
|
-
5.
|
|
81
|
-
|
|
82
|
-
6.
|
|
83
|
-
|
|
84
|
-
##
|
|
85
|
-
|
|
86
|
-
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
-
|
|
90
|
-
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
-
|
|
94
|
-
|
|
95
|
-
##
|
|
96
|
-
|
|
97
|
-
-
|
|
98
|
-
|
|
99
|
-
-
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
- `waiting_human`
|
|
103
|
-
-
|
|
104
|
-
|
|
105
|
-
-
|
|
106
|
-
|
|
107
|
-
##
|
|
108
|
-
|
|
109
|
-
-
|
|
110
|
-
`stalled` →
|
|
111
|
-
`ready_to_commit` →
|
|
112
|
-
-
|
|
113
|
-
- `supervisor`
|
|
114
|
-
- `researcher`
|
|
115
|
-
-
|
|
116
|
-
`senior-coder`
|
|
117
|
-
|
|
118
|
-
##
|
|
119
|
-
|
|
120
|
-
-
|
|
121
|
-
-
|
|
122
|
-
|
|
123
|
-
`
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
- `dept_start release=true` —
|
|
145
|
-
(
|
|
146
|
-
-
|
|
147
|
-
-
|
|
148
|
-
`CHANGELOG.md`,
|
|
149
|
-
-
|
|
150
|
-
-
|
|
151
|
-
-
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
##
|
|
157
|
-
|
|
158
|
-
-
|
|
159
|
-
|
|
160
|
-
-
|
|
161
|
-
|
|
162
|
-
-
|
|
163
|
-
- Markdown
|
|
164
|
-
|
|
165
|
-
-
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
|
|
169
|
-
##
|
|
170
|
-
|
|
171
|
-
-
|
|
172
|
-
-
|
|
173
|
-
|
|
174
|
-
-
|
|
175
|
-
|
|
176
|
-
##
|
|
177
|
-
|
|
178
|
-
- `dept_pause` (
|
|
179
|
-
|
|
180
|
-
-
|
|
181
|
-
- `paused=false` (
|
|
182
|
-
|
|
183
|
-
-
|
|
184
|
-
|
|
185
|
-
##
|
|
186
|
-
|
|
187
|
-
|
|
188
|
-
|
|
189
|
-
-
|
|
190
|
-
|
|
191
|
-
-
|
|
192
|
-
|
|
193
|
-
|
|
194
|
-
|
|
195
|
-
|
|
196
|
-
|
|
197
|
-
|
|
198
|
-
|
|
199
|
-
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
|
|
206
|
-
|
|
207
|
-
|
|
208
|
-
|
|
209
|
-
|
|
210
|
-
|
|
211
|
-
|
|
212
|
-
|
|
213
|
-
|
|
214
|
-
|
|
82
|
+
| `/api/department/tasks` | GET | tasks across projects |
|
|
83
|
+
| `/api/department/task?root=&taskId=` | GET | task card |
|
|
84
|
+
| `/api/department/activity` | GET | live agent activity |
|
|
85
|
+
| `/api/department/approve` | POST | approve a document |
|
|
86
|
+
| `/api/department/answer` | POST | answer a question |
|
|
87
|
+
| `/api/department/amend` | POST | sign an amendment |
|
|
88
|
+
| `/api/department/budget?root=&taskId=` | GET/POST | budget and prices |
|
|
89
|
+
| `/api/department/blueprint?root=` | GET | project blueprint |
|
|
90
|
+
| `/api/department/asset?name=` | GET | office assets |
|
|
91
|
+
|
|
92
|
+
## Process rules
|
|
93
|
+
|
|
94
|
+
1. Stages: `analysis → concept → concept_review → spec → spec_review → executing → done`.
|
|
95
|
+
2. Approvals are human-only (`dept_approve`); the stage moves only through them.
|
|
96
|
+
3. Each stage is closed by a commit tagged `stage-N`; the tag is pushed with the branch.
|
|
97
|
+
4. Gates reset after a commit: a previous stage's pass does not carry over.
|
|
98
|
+
5. A test failure writes `stages/NN/failure.md`; retry is forbidden until “Analysis” and
|
|
99
|
+
“Plan” are filled in.
|
|
100
|
+
6. Autonomous amendments — at most 5 per task, then escalate to the human.
|
|
101
|
+
|
|
102
|
+
## Working together on concept and spec
|
|
103
|
+
|
|
104
|
+
- Each specialist writes their section via `dept_section` (designer — style, artist — what
|
|
105
|
+
to draw, researcher — data and statistics, tester — verification strategy, architect —
|
|
106
|
+
decisions, analyst — requirements).
|
|
107
|
+
- The architect frames contested decisions as ideas (`dept_ideas`): 2–3 options.
|
|
108
|
+
- Specialists review ideas (`dept_critique`): `approve`/`reject` and severity. A hard reject
|
|
109
|
+
(`high`) kills the idea; two approvals without hard criticism accept it. A rejected idea is
|
|
110
|
+
not taken into work — the architect proposes a new one.
|
|
111
|
+
- The researcher can collect statistics and facts on the internet.
|
|
112
|
+
|
|
113
|
+
## Autonomy (goal instead of a timer)
|
|
114
|
+
|
|
115
|
+
- The manager creates a goal: “bring the task to done by plan.md” and does not close it until
|
|
116
|
+
the end. DSH drives the rounds itself — no timer needed.
|
|
117
|
+
- Each round: `dept_health` → if `stalled`, find the cause and call a specialist:
|
|
118
|
+
data — researcher, visuals — designer, images — artist, conflict — supervisor,
|
|
119
|
+
architecture — architect, integration fixes — senior-coder.
|
|
120
|
+
- `waiting_human` does not stop the work: the team decides, the memo waits for the human.
|
|
121
|
+
- Protection from empty rounds: if 2–3 rounds bring no new events — record `blocked` and a
|
|
122
|
+
memo instead of spinning.
|
|
123
|
+
- When a task is done — move to the next one; when all are closed — a party (office banner).
|
|
124
|
+
|
|
125
|
+
## Autonomy
|
|
126
|
+
|
|
127
|
+
- The manager calls `dept_health` after every step and does not stop:
|
|
128
|
+
`stalled` → next plan step, `waiting_human` → decides tactically itself,
|
|
129
|
+
`ready_to_commit` → verify and commit.
|
|
130
|
+
- For long tasks a goal is created so rounds run without human involvement.
|
|
131
|
+
- `supervisor` analyses stagnation and decides as a customer would.
|
|
132
|
+
- `researcher` searches the web, `designer` picks visuals, `artist` draws via `dept_art`.
|
|
133
|
+
- Parallel work: `dept_modules` assigns files to modules, coders do not overlap,
|
|
134
|
+
`senior-coder` assembles and assigns follow-ups.
|
|
135
|
+
|
|
136
|
+
## Testing
|
|
137
|
+
|
|
138
|
+
- **Tester** — automated checks: tests, invariants, exit code. This is the stage gate.
|
|
139
|
+
- **Beta-tester** — plays/works as a user: walks scenarios, catches confusing places,
|
|
140
|
+
broken flows, visual bugs; files a bug report via `dept_bug` (steps, expected/actual,
|
|
141
|
+
severity, evidence). For games/UI it uses `dept_browse`: opens the page, clicks, types and
|
|
142
|
+
attaches a screenshot to the report.
|
|
143
|
+
- Before a release the manager runs a beta test and triages bugs: critical — into work,
|
|
144
|
+
the rest — into the backlog.
|
|
145
|
+
|
|
146
|
+
### Native applications (C++/Qt)
|
|
147
|
+
|
|
148
|
+
- `dept_gui` runs a program with arguments/env and a timeout, captures the output.
|
|
149
|
+
- Screenshot: either the app saves a frame itself by flag (`--screenshot file.png`,
|
|
150
|
+
`QWidget::grab()` / `QQuickWindow::grabWindow()`), or an external command
|
|
151
|
+
(`import -window root shot.png` under Xvfb).
|
|
152
|
+
- Recommended for Qt: a test hook `--scenario`/`--selftest` that walks a scenario and saves
|
|
153
|
+
screenshots; then the beta test is deterministic and works in CI.
|
|
154
|
+
- Interactive GUI automation (mouse clicks) needs Xvfb/xdotool; the current environment does
|
|
155
|
+
not have them, so the bet is on application hooks and Qt Test.
|
|
156
|
+
|
|
157
|
+
## Release preparation (a standard phase)
|
|
158
|
+
|
|
159
|
+
The office does not only build the product but also ships it. A release is not a one-off
|
|
160
|
+
request but a phase after `done`:
|
|
161
|
+
|
|
162
|
+
- `dept_start release=true` — the task brief gets the `templates/release.md` template
|
|
163
|
+
(package, user documentation, QA checklist, changelog, version, tag, handover);
|
|
164
|
+
- artifact: `release/<product>-<version>/` + `.zip`;
|
|
165
|
+
- documentation: `README.md` (run, controls), `MANUAL-QA.md` (manual testing),
|
|
166
|
+
`CHANGELOG.md`, known limitations;
|
|
167
|
+
- verification: project tests, `dept_verify`, beta test by the checklist (`dept_bug`);
|
|
168
|
+
- commit: `dept_commit` with tag `v<version>`, tag pushed to remote;
|
|
169
|
+
- report: where to get it, how to run, what to check by hand.
|
|
170
|
+
|
|
171
|
+
Release acceptance criterion: the human takes the artifact and runs it without hints; the
|
|
172
|
+
documentation answers “how to run”, “what it can do”, “what is limited”.
|
|
173
|
+
|
|
174
|
+
## Document library and event log
|
|
175
|
+
|
|
176
|
+
- The “Documents” tab is like mail: on the left a list of documents (search by title, filter
|
|
177
|
+
by type, sort by date), on the right the content.
|
|
178
|
+
- Types: memo, stage report, review, bug report, specialist section, rework plan, spec,
|
|
179
|
+
concept, plan, backlog.
|
|
180
|
+
- The “Events” tab — list on the left, details of the selected event on the right.
|
|
181
|
+
- Markdown in documents is rendered as markup: headings, lists, tables, inline code and code
|
|
182
|
+
blocks with highlighting (JS/TS/C++/Python keywords).
|
|
183
|
+
- Memos waiting for a decision are marked “REQUIRES DECISION” and raised to the top of the
|
|
184
|
+
list; the board shows a “✍ N” badge on the task, the office shows a yellow marker above the
|
|
185
|
+
manager, the card header shows the memo count.
|
|
186
|
+
|
|
187
|
+
## Goals
|
|
188
|
+
|
|
189
|
+
- Before `update_goal` always call `get_goal` and use the current revision.
|
|
190
|
+
- A `stale goal ref` error means the revision has already changed: re-read `get_goal` and
|
|
191
|
+
retry once with the new revision — do not guess.
|
|
192
|
+
- Pausing the department does not pause the goal: the goal lives separately (that is DSH).
|
|
193
|
+
|
|
194
|
+
## Pause and resume
|
|
195
|
+
|
|
196
|
+
- `dept_pause` (or the button in the card) — the task is paused: gates, commit and amendments
|
|
197
|
+
are blocked, no tokens are spent, the state stays on disk.
|
|
198
|
+
- The watchdog does not wake a paused task.
|
|
199
|
+
- `paused=false` (human signature) — work continues from the same place, including after a
|
|
200
|
+
server shutdown/startup.
|
|
201
|
+
- The office shows the pause: a “department paused” banner and the manager sits in the lounge.
|
|
202
|
+
|
|
203
|
+
## Multilingual UI
|
|
204
|
+
|
|
205
|
+
The panel interface is **Russian and English**:
|
|
206
|
+
|
|
207
|
+
- an **EN/RU** button in the board header; the choice is remembered (`localStorage['dept-lang']`);
|
|
208
|
+
- by default — the browser language, falling back to Russian;
|
|
209
|
+
- translated: navigation, task card, tabs, stages, events, audit, document types, roles,
|
|
210
|
+
budget, office, project blueprint, charts.
|
|
211
|
+
- **Document content** is written by agents in the task language — it is not UI strings; the
|
|
212
|
+
documentation language is set in the brief (`lang` in task.md) or in the prompt.
|
|
213
|
+
|
|
214
|
+
Dictionary: `LOCALES` in `client.js` (ru/en), `dot.case` keys, `{n}` interpolation.
|
|
215
|
+
Roadmap — `docs/I18N.md`.
|
|
216
|
+
|
|
217
|
+
## Incoming-data watchdog
|
|
218
|
+
|
|
219
|
+
- Every 5 minutes the plugin checks department tasks: new corrections (`new`), answers to
|
|
220
|
+
questions (`answered`), remarks on memos (`changes_requested`).
|
|
221
|
+
- If new data appears, it collects a package and wakes the manager (`followup`), once per new
|
|
222
|
+
item; it does not resend the same thing.
|
|
223
|
+
- If the manager is busy, the watchdog waits for the next check.
|
|
224
|
+
- **Anti-stall**: if the task is active (not paused/done/blocked), the agent is idle, and the
|
|
225
|
+
last event is older than 15 minutes — the watchdog wakes the manager with a hint
|
|
226
|
+
(dept_verify/commit or the next step). At most once per 30 minutes per task.
|
|
227
|
+
|
|
228
|
+
## Corrections
|
|
229
|
+
|
|
230
|
+
- The “Corrections” tab is a letter to the manager: what it relates to (concept/spec/plan/
|
|
231
|
+
code/data/interface), subject and text. It is stored in the correction history.
|
|
232
|
+
- `dept_correction` — the manager sees the list, takes it into work (`in_progress`), gathers
|
|
233
|
+
specialists for analysis and closes it (`done`) with a summary.
|
|
234
|
+
- Corrections are used to update the concept, spec and plan (`dept_amend`, `dept_section`).
|
|
235
|
+
|
|
236
|
+
## Questions and memos
|
|
237
|
+
|
|
238
|
+
A question to the human does not stop the work:
|
|
239
|
+
|
|
240
|
+
1. `dept_ask` — the question is recorded, the department continues.
|
|
241
|
+
2. `dept_propose` — the supervisor proposes solution options.
|
|
242
|
+
3. `dept_critique` — specialists critique; the accepted decision is recorded.
|
|
243
|
+
4. `dept_memo` — a memo: question, options, criticism, team decision
|
|
244
|
+
(file `docs/department/<task>/memos/<question>.md`).
|
|
245
|
+
5. `dept_review` — the human approves (`approve`) or writes remarks (`changes`).
|
|
246
|
+
6. `dept_rework` — the architect prepares a rework plan from the remarks
|
|
215
247
|
(`docs/department/<task>/rework/<question>.md`).
|
|
216
248
|
|
|
217
|
-
##
|
|
249
|
+
## Multi-project
|
|
218
250
|
|
|
219
|
-
-
|
|
220
|
-
-
|
|
221
|
-
|
|
222
|
-
-
|
|
223
|
-
|
|
224
|
-
-
|
|
251
|
+
- The “Projects” tab — aggregates by root: tasks, stages, budget, last event.
|
|
252
|
+
- Each root is a separate department: tasks are created via `dept_start root=...`, the board
|
|
253
|
+
shows all projects, filtering by project.
|
|
254
|
+
- For parallel work inside a project: `dept_modules` (file ownership) + `dept_worktree`
|
|
255
|
+
(isolated directories per module), merging — senior-coder.
|
|
256
|
+
- The limit of concurrent coders is the role's `maxInstances`.
|
|
225
257
|
|
|
226
|
-
##
|
|
258
|
+
## Artist and references
|
|
227
259
|
|
|
228
|
-
- `dept_art`
|
|
229
|
-
(
|
|
230
|
-
- `dept_pixelize`
|
|
231
|
-
(2–64
|
|
232
|
-
|
|
233
|
-
-
|
|
260
|
+
- `dept_art` draws on a character grid: input — `rows` (character = pixel) and `palette`
|
|
261
|
+
(character → #rrggbb), output — PNG (RGBA), scale 1–16.
|
|
262
|
+
- `dept_pixelize` takes PNG/JPEG/WebP, downsizes to a grid (4–96), quantizes to a palette
|
|
263
|
+
(2–64 colors or a given one), saves a PNG and returns `rows` + `palette` — the artist edits
|
|
264
|
+
pixels by hand to get a similar but own sprite.
|
|
265
|
+
- A reference is for style (palette, proportions), not for copying someone else's graphics.
|
|
234
266
|
|
|
235
|
-
###
|
|
267
|
+
### The artist works slowly
|
|
236
268
|
|
|
237
|
-
-
|
|
238
|
-
|
|
239
|
-
-
|
|
240
|
-
-
|
|
241
|
-
-
|
|
242
|
-
|
|
269
|
+
- Speed is not a criterion: quality matters more. The artist draws in parts:
|
|
270
|
+
reference/palette → base shapes → details → check → composition.
|
|
271
|
+
- Each step is a separate checkpoint file (`assets/...png`) that can be reviewed.
|
|
272
|
+
- A large picture is not drawn in one piece: small sprites + `dept_compose`.
|
|
273
|
+
- Role: `reasoning: high`, up to 6 attempts; the manager splits the task into elements
|
|
274
|
+
instead of telling the artist “draw everything”.
|
|
243
275
|
|
|
244
|
-
##
|
|
276
|
+
## Limitations
|
|
245
277
|
|
|
246
|
-
-
|
|
247
|
-
-
|
|
248
|
-
-
|
|
249
|
-
|
|
250
|
-
-
|
|
251
|
-
|
|
252
|
-
-
|
|
278
|
+
- The office and the blueprint are visualizations of session data; the art is simple.
|
|
279
|
+
- The blueprint builds only static imports (JS/TS/C/C++/Python).
|
|
280
|
+
- Each role has a limit of concurrent instances (`maxInstances`), the coder defaults to 2:
|
|
281
|
+
the manager cannot run more coders than allowed.
|
|
282
|
+
- Roles can be enabled/disabled (except manager/coder/tester); `beta-tester` is disabled by
|
|
283
|
+
default — launching apps and screenshot streams is resource-heavy.
|
|
284
|
+
- The budget counts the usage reported by model adapters; prices are set manually.
|
|
253
285
|
|
|
254
|
-
##
|
|
286
|
+
## License
|
|
255
287
|
|
|
256
|
-
MIT.
|
|
288
|
+
MIT. Office assets (`assets/`) are original and/or CC0; third-party packs are not included.
|