Experiment & Demo Layer

5 Labs — Hands-On Agent Engineering

Small, explainable, reusable demos for each core capability. Each lab is designed to teach one pattern through practice.

💭

Memory Lab

ready

Show how a project evolves when rules, build commands, and prior learnings become persistent assets.

Demo Flow
01Memory entry creation and 3-layer architecture demo
02Memory update and contradiction resolution
03Memory lookup and verification against codebase
04autoDream-style consolidation simulation
Prerequisites
Understanding of MEMORY.md index pattern
Familiarity with topic file structure
Governance Notes

Memory must be treated as hints, not truth. Always verify against actual project state before acting.

🪝

Hook Lab

ready

Show how standards become execution checkpoints rather than documentation that gets ignored.

Demo Flow
01Pre-edit warning hook (prevent changes to protected files)
02Post-edit lint/test hook (auto-run validation)
03Pre-publish validation hook (check V5.3 compliance)
04Policy block demo (reject non-compliant operations)
Prerequisites
Understanding of lifecycle events
Basic shell scripting
Governance Notes

Hooks enforce standards automatically. The leak was caused by a missing hook-equivalent check in the build pipeline.

Skill Lab

ready

Show how repeatable workflows are packaged and reused across projects and roles.

Demo Flow
01Create a reusable skill (SKILL.md format)
02Invoke skill from natural language
03Edit and version a skill
04Skill library management view
Prerequisites
Understanding of skill packaging format
Familiarity with prompt templates
Governance Notes

Skills should be reviewed before distribution. Version control and rollback capability required.

🎯

Subagent Lab

ready

Show decomposition of complex tasks into specialist roles with clear accountability.

Demo Flow
01Fork mode: independent parallel research
02Teammate mode: collaborative writing with shared context
03Advisor pattern: quality oversight of worker output
04Multi-agent pipeline: research → write → review → deploy
Prerequisites
Understanding of Fork/Teammate/Worktree models
Familiarity with mailbox communication
Governance Notes

Explicit ban on lazy delegation. Coordinator must read actual findings, not just summaries.

🌙

NightOps Lab

ready

Demonstrate unattended nightly operational patterns that remain governable and auditable.

Demo Flow
01Nightly summary generation from daily logs
02Work queue processing with priority sorting
03Morning brief compilation
04Retry and recovery logic with failure budgets
Prerequisites
Understanding of KAIROS daemon architecture
Familiarity with append-only logging
Governance Notes

15-second blocking budget per action. Actions exceeding budget must be deferred. All operations append-only logged.