Owns engineering delivery and technical operations: architecture, development, DevOps, security, deployment, and incident response.
Documents
| Document | Summary | |
|---|---|---|
| 1 | Official Docs Format Guide | Defines the exact format and structure for all Kiluth Official Documents: file location, document structure, content formatting (tables over lists), standard sections, task templates, and cross-reference style. |
| 2 | Engineering Architecture & Data Flow Guideline | Essential engineering architecture and data flow standards: contract-first workflow, layered responsibilities (entry → application → data access), separation of DTOs/entities/storage models, and minimum requirements for validation, observability, security, and testing. |
| 3 | Migrating to the Engineering Architecture Guideline | How to migrate existing systems to the Engineering Architecture Guideline: test-first, incremental approach with baseline → tests/contracts → migrate → sign-off. Migration matrix and contract tests guard behavior. |
| 4 | Go-Live & Incident Response Guideline | Minimum operational playbook for go-live execution and incident response: environment flow (Local → DEV → UAT → Staging → Production), rollback and verification plans, and incident triage → contain → communicate → resolve workflow. |
| 5 | Kiluth Tasks Usage | How Kiluth Tasks is built and how it checks itself: tasks as Markdown files in Git, the task and project file shapes, the automatic checker and its three tests, and the read-only web view. For operators and agents; the rules themselves live in the Task Usage Guideline. |
| 6 | Bug Report Guideline | How Kiluth reports and tracks bugs in Kiluth Tasks: one task per bug, chained to a batch task for the round (e.g. one UAT round). Required fields: evidence, steps to reproduce, expected vs actual. Consistent format for UAT, QA, and production bugs. |
| 7 | Hosting Resource Archival Guideline | How to retire an expired hosting VM: snapshot, clean the deploy controller (before destroying the VM), destroy, clean DNS, flip the registry to Archived. Provider-agnostic flow; vendor-specific steps live in the Technology provider reference runbook. |
| 8 | Kiluth Document Spec | Defines what “Kiluth-styled document” means — the HTML/CSS spec, component vocabulary (cover, TOC, plain/grid/numbered/form tables, single-row callouts, ✓/✕, calendar grid, card stack, signatures), and editorial house rules (no auto-numbering, h1 starts new page, prefer numbered tables over ul/ol, headings stay with content). Any tool that conforms to this spec produces visually consistent Kiluth PDFs. |