Synapse visual overview kit
These figures explain the current source tree with the official Synapse palette.
They are editable SVG source, with no remote fonts, scripts or embedded runtime.
Desktop and vertical mobile variants share the same responsibilities and claims.
README and architecture figures select the vertical version below 650px with an HTML
picture element.
Keep the files readable in both GitHub and the generated documentation site.
| File | Responsibility and evidence |
|---|---|
memory-foundation.svg | Stable content model: Markdown/Git, derived local search and CLI/MCP access. Suitable for the distribution mirror without newer integration claims. |
governed-memory-loop.svg | Local proposal, exact review, accepted note and separately scoped evidence. The knowledge process contract always queues; other paths follow their configured policy. |
one-core-topology.svg | Current shared core and its interfaces. Retained evidence and operational queue state are distinct from rebuildable search data. |
knowledge-in-context.svg | Synapse as an additive component for Soma and other hosts. Current source adapters are read-only; future authoring-tool adapters are labeled planned. |
retrieval-evidence.svg and mobile variant | Recorded observations from docs/assets/bench/persona-recall.json: 20 fixed questions, six synthetic contexts, 77 to 463 entities, internal macOS arm64 run. The original run’s source commit is unknown. |
Editing and review
Use Indigo #5B3EE0, Paper #F6F4EF and Amber #FFB454 from
the brand guide. Muted colors must retain contrast. Keep labels short,
add a viewBox, descriptive title/description and meaningful alt text at every use.
Pair figures with searchable text so small screens do not depend on image labels alone.
Readers can open an SVG at full size when inspecting dense technical detail.
Change an arrow only when its data flow or responsibility is supported by current source and the linked contract. Keep historical evidence, current capability and planned work separate. Review the source/release boundary before copying a figure into the public artifact repository. Do not imply every record is true, signatures prove current permission, or an absent verification input passed.
The retrieval chart is rendered with Matplotlib from the unchanged JSON observations.
plot-retrieval.py is the reproducible figure generator; it does not run a benchmark.
Run it with an existing Python environment containing Matplotlib:
python assets/branding/overview/plot-retrieval.py
The generator rewrites only retrieval-evidence.svg and its mobile variant in the asset directory. It has no runtime
role, imports no product credentials and downloads no models. Inspect the resulting image
at typical README width before committing it. Do not invent a baseline, smooth the measured
points or omit corpus/sample limitations. To change the data, run and document a new
benchmark separately.
Connection semantics
Declare the view before drawing edges. one-core-topology.svg is a dependency view:
operators and Soma invoke CLI; MCP clients invoke MCP; both interfaces call the same core.
Solid arrows show calls or dependencies, with responses omitted. The narrow layout groups
storage responsibilities without introducing storage-to-storage calls.
governed-memory-loop.svg is a transition view. The review question has a conditional
acceptance edge; other outcomes stay pending. The later-task connector bypasses the evidence
summary because that summary is not a mandatory verification-success stage.
Keep arrowheads attached to actual node ports. Do not merge independent clients into an unlabeled bus. Give a shared junction a visible dot, and preserve the same relationships when reflowing a figure for mobile. Color supports the product identity; it does not grant permission or establish knowledge truth.
The historical PNG in brand/images/retrieval-quality.png is now a raster export of the
canonical retrieval SVG. Its HTML preview embeds the same SVG so it cannot silently drift
through separately positioned chart coordinates. See the source repository’s brand/README.md
for the export command.
knowledge-in-context.svg labels host calls, owned-content operations and incoming adapter
evidence separately. Read-only adapters do not receive a write-back edge. The foundation
illustration is a conceptual content-availability flow, not a dependency or deployment
diagram. Its left-to-right order does not mean SQLite calls a CLI process.