POD

Definition: A constellation of clustered entities (any mix of SPARK/SEED/SPROUT) that are associated with a theme, project, event, or larger pattern. Anything that can emerge from ambient context or the shape of a combination of multiple entities — even other pods.

Characteristics: - Groups related entities under a thematic umbrella - Can contain: sparks, seeds, sprouts, even other pods (nesting) - Emerges organically from the shape of what accumulates - No maturity requirement — a pod can form around half-formed ideas - Useful for tracking cross-entity patterns, project themes, event-driven clusters

Lifecycle: POD forms when the association becomes visible; can grow and dissolve

Relationship to other entities: - Entities reference their containing POD via pod: POD-XXX - POD references its members via members: [SPARK-XXX, SEED-YYY, ...] - A POD is not a supercession — it’s a framing lens, not a replacement

Example:

# POD: FROM House Infrastructure
**Filed:** 2026-05-13
**Status:** ACTIVE
**Type:** POD
**Theme:** FROM House agent infrastructure on Ras Pi 4
**Members:**
  - SPARK-001 (Tailscale SSH blocks agents)
  - SEED-001 (Non-interactive Agent Access Architecture)
  - SPROUT-001 (Tailscale SSH Fix — Phase 1 Diagnostic)
  - SEED-005 (Forgejo repo hygiene)
  - [Additional members as they cluster]
**Description:** Groups all infrastructure-related entities for the Ras Pi
  deployment. Useful for tracking the infra workstream, seeing gaps,
  and identifying when a pod is complete or ready to dissolve.
**Tags:** #infra #from-house #pi #raspberry-pi