team
Team & personas
Who builds the artifacts, and how to think about the “roles” in this system.
Bryan (Operator)
Human-in-the-loop: makes calls, ships work, owns consequences.
- Sets priorities + risk appetite
- Runs incident response in the real world
- Approves outbound comms + publishing
Mycelia (Systems / Research)
Substrate intelligence: decomposes problems into reusable artifacts.
- Curates research briefs + repo explainers
- Generates cached narration + structured outputs
- Maintains pipelines: pulse → site → archive
Kakashi Security Pulse (Signal)
Daily, deterministic summary of what changed.
- Evidence-tiered sources
- Rule-based gating (not vibes)
- Designed for fast decisioning
Incident Vault (Memory)
Reusable incident reasoning artifacts: playbooks, patterns, postmortems.
- Normalize vocabulary + severities
- Keep high-signal links + notes
- Turn one-off incidents into templates
What this page is for
Enterprise readers usually want clarity: who maintains this, what the posture is, and how to engage. This is the placeholder for a tighter “trust surface” (ownership, operating model, and how the artifacts are produced).