Skip to main content

Meaning Lives in Summaries

Why this page exists​

Your portfolio stopped feeling “heavy” the moment you made summaries the control surface.

This is not a slogan. It’s an architectural rule:

Summaries are the representation layer for knowledge.
They are the normalized interface between raw corpora and downstream products.

If you don’t freeze this, the system quietly regresses to “raw chunks everywhere” and everything becomes expensive again: queries, decisions, publishing, even planning.

The control-surface rule​

1) Summaries are the meaning surface​

Raw text is the substrate. Summaries are the operational surface you can route, join, gate, publish, and audit.

  • Raw chunks are high-entropy and expensive to reason over.
  • Summaries are low-entropy and composable.
  • The system’s center of gravity should live at the summary layer.

For document-like sources, that summary layer includes summaries derived from chunk_bus, not just summaries derived from events or sessions.

2) Summaries are the join key across corpora​

Corpora are your what to know. Projects are your what to do.
Summaries are the bridge.

In practice:

  • Corpora ingest → chunk → summarize (plus optional embed/annotate)
  • Downstream projects consume summaries to produce digests, snapshots, posts, decisions, action queues.

This makes summaries the “exchange currency” of the portfolio.

For document-like sources, the canonical summary artifact is a traceable hierarchical synthesis derived from Chunk Bus inputs. The Summary Bus stores both a compatible textual projection (outputs.summary_text) and, when available, a structured hierarchy for downstream reuse.

3) The Summary Bus is a hub, not a leaf​

Treat summary_bus as your main junction:

  • Producers (Role A) output raw truth to chunk_bus / event_bus.
  • Transformers (Role B) convert raw truth → summaries on summary_bus.
  • Publishers (Role C) are mostly consumers of summary_bus (often via digest_bus / snapshot_bus).
  • Governance (Role D) watches all of it and enforces stop rules.

The summary layer covers event summaries, session summaries, and document-oriented summaries produced from deterministic chunk or document selections. Downstream may consume either the textual projection or the structured synthesis surface, but it should still consume summaries rather than raw text.

If the Summary Bus is not a hub, the portfolio becomes raw-data-centric again. A portfolio that routes on summaries stays light. A portfolio that routes on raw text gets slower the more it grows.