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, Asana card 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 behaviour. |
| 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 | Asana Usage with Kiluth API | How Kiluth uses Asana with the Kiluth API: OAuth, rule actions, and Evaluate Task. Asana card rules (dependency chain, actionable title with Definition of Done, no PII) for consistent evaluation by the API and by people. |
| 6 | Bug Report Guideline | How Kiluth reports and tracks bugs in Asana: one card per bug batch (e.g. UAT round), each bug as a subtask. Required fields: evidence, steps to reproduce, expected vs actual. Consistent format for UAT, QA, and production bugs. |