Files
APAW/.architect
NW f01e2064fb feat(evolution): Kilo Code release sync & APAW system hardening (v2026-05-07)
Security & Permissions:
- All 30 agents: task[*]=deny, task[subagent]=deny (cascade prevention)
- orchestrator & release-manager: bash=ask (hardening)
- New .kilo/rules/subagent-security.md with audit rules
- Updated .kilo/rules/global.md with Security & Permissions section
- Updated .kilo/agents/orchestrator.md with Security Enforcement block

Session Management:
- New .kilo/rules/session-persistence.md (checkpoint format, worktree isolation)
- Updated .kilo/rules/branch-strategy.md (worktree per agent)
- pipeline-runner.ts: Checkpoint interface + save/load/resume methods

Plan Persistence:
- Updated .kilo/rules/lead-developer.md (plan handover section)

Per-Agent Reasoning:
- capability-index.yaml: reasoning_effort for all 30 agents (xhigh/high/medium/low)

MCP Cleanup:
- New .kilo/skills/docker-security/SKILL.md (--rm, orphaned process cleanup)

Config Validation:
- Updated .kilo/rules/docker.md (startup checks, commit scoping, location awareness)

Docs:
- README.md: v2026-05-07 evolution badges
- .kilo/EVOLUTION_LOG.md: Entry #6 with full metrics
- .gitignore: ignore dist/ + bun.lock

Gitea: Milestone #66, Issues #91-#98
Architect: 9/9 sections fresh (express project type)
2026-05-08 18:54:08 +01:00
..

📐 Project Architecture Index

Auto-generated navigation file. Updated by architect-indexer on every pipeline run. DO NOT edit manually — changes will be overwritten. Edit source code instead.

Quick Status

Metric Value
Last Indexed pending first run
Index Version 1
Files Tracked 0
Modules 0
Staleness unknown

Navigation

🏗 Architecture

File Description When to Read
architecture/overview.md High-level project architecture, layers, boundaries Before ANY implementation task
architecture/dependency-graph.md Module-to-module dependency graph Before adding cross-module imports

📦 Entities & Data

File Description When to Read
entities/entities.md All domain entities, their fields and relationships Before creating/editing models or DB tables
db-schema/schema.md Database tables, columns, indexes, foreign keys, migrations Before touching any migration or DB query

🌐 API Surface

File Description When to Read
api-surface/endpoints.md All API endpoints, methods, auth, request/response types Before adding/modifying any API endpoint

📏 Conventions

File Description When to Read
conventions/conventions.md Coding style, naming, patterns, forbidden practices Before writing ANY code

🔧 Tech Stack

File Description When to Read
tech-stack/stack.md Languages, frameworks, libraries, versions Before adding dependencies or choosing tools

🗺 Machine-Readable Maps

File Description Used By
maps/file-graph.json File → imports/exports graph architect-indexer, system-analyst, lead-developer
maps/module-graph.json Module → dependencies graph system-analyst, orchestrator for routing

⚙️ Machine Config

File Description Used By
project.json Project metadata (name, type, framework, entry points) orchestrator for routing decisions
state.json Index freshness state (hashes, timestamps, version) orchestrator to detect staleness

How It Works

For Agents

  1. First contact: Orchestrator checks .architect/state.json
  2. Stale or missing: Launch architect-indexer to build/update
  3. Fresh: Read relevant files from .architect/ for context
  4. After changes: architect-indexer incrementally updates affected sections

For Humans

  • Browse any .md file for human-readable documentation
  • Check project.json for quick project facts
  • See state.json for when the index was last updated

Update Triggers

Event Action
New file added/removed Rebuild maps/file-graph.json
New dependency added Update tech-stack/stack.md
Schema migration created Update db-schema/schema.md
New entity/model created Update entities/entities.md
New API endpoint added Update api-surface/endpoints.md
Convention file changed Update conventions/conventions.md
Any structural change Increment version in state.json