โšก Swarm Architecture

Highlight

--- description: Capture a highlight into the shared swarph timeline + decide the memory it links to. --- You are capturing a HIGHLIGHT into the swarph collaborative timeline โ€” the mesh's shared continuous-learning memory. This writes to a commons every cell reads, so be deliberate but low-friction.

Highlight to capture: $ARGUMENTS (If empty: identify the single most salient, DURABLE learning / decision / event from the recent conversation โ€” the one thing genuinely worth not forgetting. If nothing qualifies, say so and stop โ€” don't manufacture a highlight.)

Steps: 1. Distill to ONE clear line: what was learned/decided/happened + why it matters. 2. Decide the memory (the judgment step):

  • Does it EXTEND an existing memory? โ†’ append the detail to that file; pointer = its name.
  • Genuinely new + durable? โ†’ create a lean new memory file (frontmatter + fact + why); pointer = its name.
  • Ephemeral (no lasting value)? โ†’ no memory file; pointer empty (the timeline line still logs the moment).
3. Log it by running the shared script (deterministic append+commit+push to the shared TIMELINE.md โ€” every cell sees it): SWARPH_CELL="" ~/swarph-timeline/bin/swarph-highlight "" "[[]]" (drop the 2nd arg if no memory.) 4. Confirm in one line: what you logged + the memory (new / extended / none).

Discipline: one highlight, one timeline line, one memory decision. Don't over-produce.