REQUEST INDEXEvery instruction becomes a Request · REQ-[YYYYMMDD]-[N]
| REQUEST | DATE | TYPE | PROJECT | FORMAL REQUEST | STATUS | PRIORITY | ACTIONS |
|---|---|---|---|---|---|---|---|
| REQ-20260721-2 | 2026-07-21 | BUILD | RS//RS//RSC#1 | IN PROGRESS | HIGH | ||
| REQ-20260720-1 | 2026-07-20 | RESEARCH | RS//DF//TFC#1 | IN PROGRESS | HIGH | ||
| REQ-20260718-1 | 2026-07-18 | BUILD | RS//RS//RSC#1 | COMPLETE | NORMAL | ||
| REQ-20260717-2 | 2026-07-17 | BUILD | RS//RS//RSC#1 | COMPLETE | HIGH |
5 requests · page 1 / 2
HOW TO BUILD A REQUESTinvoke /build-req
STEP 1
RAW INPUT
Any instruction from Stefan — formal or informal. Verbatim capture.
STEP 2
CLASSIFY
Match against Request Index (17Kx9dy…). Identify type, scope, priority. If no match — run New Type Protocol.
STEP 3
BUILD CARD
Complete all fields: ID · Formal Request · Key Output · Purpose · Scenario · Deadline. Surface for sign-off.
STEP 4
APPROVE
Stefan confirms. Status → APPROVED. Row written to Project Request Registry. Doc created in Drive.
STEP 5
/build-tasks
Tasks spawned from the approved request. Each task carries the Request Code as its parent FK.
Request Index: 17Kx9dyPTeLUtHUKOaRoLSXFm_gD8sADF2EqG8OrfK9Q · /build-req → /build-tasks → /run-scope → /run-go
REQUEST INDEXfixed taxonomy of request types — grows only when new types are formalised
BUILDBuild or extend a platform, tool, or workflow
RESEARCHRun a SuperBasic Research cycle on a topic or entity
PRODUCECreate a content asset (Clash, article, video)
OUTREACHDraft or send a communication to a contact
ANALYSEInterpret data, signals, or a situation
PLANScope a project, operation, or run