TazLab CRISP Program Map

Scope

This page maps the main CRISP workstreams and explains how the design tree relates to the rest of the TazLab ecosystem.

Current Synthesis

CRISP is the structured research and design workbench inside AGENTS.ctx/. It is not an implementation surface. Its purpose is to keep large technical efforts decomposed into explicit parent and child projects so that build work starts from reviewed design rather than agent improvisation.

Main Workstreams

Vault / Hetzner Runtime

  • the dominant current parent is hetzner-vault-platform
  • that tree is explicitly split into foundation, runtime, consumers, historical material, and a reserved future orchestration branch
  • the split makes diagnostic and planning boundaries visible: foundation first, then Vault runtime behavior, then downstream consumer adoption

Memory / Knowledge Systems

  • completed projects document the evolution from older report structures toward the current memory model
  • this workstream explains why TazLab now distinguishes active memory, semantic retrieval, and documentation layers

Blog / Publishing

  • CRISP is also used to design publishing-related changes such as the blog comments project
  • this links the internal design workbench to the external narrative layer in blog-src

Tooling / Council / Internal Systems

  • this workstream covers operator and internal-system projects such as TazPod hardening, pi-council evolution, and OpenClaw integration

Why It Matters

The CRISP tree is one of the clearest representations of planned and completed strategic work across TazLab. It complements the repository map by showing not just which repositories exist, but which bounded initiatives have shaped them and which ones are still planned.

Relationships

Source Basis

  • AGENTS.ctx/crisp/CONTEXT.md
  • AGENTS.ctx/crisp/projects/hetzner-vault-platform/DESIGN.md
  • AGENTS.ctx/crisp/projects/hetzner-vault-platform/30-hetzner-vault-consumers/DESIGN.md