Repository navigation
Synergy Map
Getting Started Easy Mode · Current visual guide · Current 4K film · Media release
The newest engineering companion connects the complete workflow: 49 main blocks, 120 directed connections and 92 vector icon instances on a native 7680 × 4320 canvas. Follow inputs through selected context, coordination, specialist roles, actual tools, evidence, acceptance and delivery, then follow feedback into the next session.
| Format | Use |
|---|---|
| Interactive ZIP package | Download, extract, then open SYSTEMX-Synergy-Map.html in a browser. The package keeps relative links, sources and font notices together. |
| Native 8K PNG | Full-resolution overview for large displays and large-format reference. Zoom for dense text. |
| Editable SVG | Selectable text, embedded fonts, original geometric icons and identified edges. |
| Standalone HTML download | Download and open locally. GitHub serves it as an attachment; the wiki does not execute it. |
| Block and connection reading guide | Every block's inputs/outputs and the full connection ledger. |
| Deep reference and fixed questions | System explanation and the complete public question catalogs. |
| Graph JSON and source catalog | Nodes, edges, routes, public definitions and hashes of the reviewed sources. |
| Publication manifest and checksums | Exact published artifact identities. |
The offline viewer lets you select a block to highlight direct inputs/outputs, read each connection's meaning, inspect its folder and command route, and open source links pinned to the reviewed revision. Search, a keyboard block selector, zoom controls and three worked routes make the dense poster easier to explore. Source links are outbound links selected by the reader.
| Stage | What it connects | Selected records or tools |
|---|---|---|
| Signals and inputs | Human objective, code, references, private/large inputs, host/account facts, observations and revised acceptance | Original request, selected Git checkout, approved sources and DATA |
| Scope and shared records | Explicit root/child scope, entry instructions, context, plan, ledger, current focus and memory |
START-HERE.md, GLOBAL/CONTEXT.md, PLAN/MASTER-PLAN.md, WORK/TASKS.json, WORK/FOCUS.json, MEMORY/PROJECT.md
|
| Agent 0 control | Coordination, dependencies, packets, ROOT planning, roster, Agenda/access review, observation deltas and checkpoints |
root roster, task-ready, task-packet, agenda status, root delta
|
| Specialist roles | X, Y, Z, Alpha, Beta, Agent1 and native/numeric workers |
EVENTS/, AGENTS/, REVIEWS/, AUTOBOT/, AGENTB/, SECURITY/AGENT1/
|
| Tools and processing | Direct CLI, read-only stdio, selected provider execution, configured checks, credentials, data and Git/PR/deployment | Reviewed launcher, installed provider, task worktree and actual host commands |
| Evidence and decisions | Source identity, check/artifact proof, actual rights/readback, reviews, findings, events and owner acceptance | Original commands/results, revisions, hashes and canonical acceptance |
| Delivery and feedback | Accepted implementation, generated status, workbook view, approved exports, delivery proof, lifecycle and next context | Generated views, selected local/ XLSX, approved output target and checkpoint |
Record paths are relative to the selected .SYSTEMX root unless stated
otherwise. A named child uses its own Projects/NAME/.SYSTEMXP records and
shares reviewed outer defaults. TASK-ID, Y-ID, R-ID and PATH are
placeholders requiring actual selected-scope values.
| Type | Appearance | Meaning |
|---|---|---|
| Local data / CLI | Solid cyan | Implemented local reads, record flow and reviewed CLI changes |
| Generated view | Solid green | Derived projection of canonical records |
| Reference / context | Dotted violet | Selected reference data, retained observations or context |
| Selected external action | Dashed amber | Explicitly selected host/provider action or actual readback |
| Review / acceptance | Solid white | Evidence review and the recorded acceptance boundary |
| Rework / next delta | Dashed coral | Remaining gap, correction or next bounded action |
Color supports labeled types; the text ledger names every edge's type and meaning. The 120 directed edges comprise 32 local, 7 generated, 26 reference, 22 external, 28 review and 5 rework connections.
- A bounded code change: request → scope/context → Agent 0 → assignment → selected Agent Y provider → project checks → evidence → review → owner acceptance → separate delivery/readback → observations → checkpoint.
- First-run security and credentials: actual host/consumer → scope → Agent1 questions → reviewed access intent → separately authorized credential handling → findings/evidence → owner decision → checkpoint.
- Research/private data to approved output: selected sources and authorized payloads → context → Alpha references → actual host processing → checks/provenance → review → accepted export → explicit publication/readback.
A highlighted route describes information and responsibility. Commands execute only through the selected tools and authorized workflow.
The reference includes all ten AUTOBOT functions, 400 Agent1 questions across twenty security domains, 100 Agent Z questions, twenty provider/navigation targets, twenty default-deny Access Matrix role/instance rows, ten Agenda definitions, ten security event buckets and forty-three hashed public sources.
The AUTOBOT functions are Design, Soul, Memory, Rules, Research, Brand, Media, Tokens, Data and Archive. Tokens concerns CSS/design tokens, fonts and themes. Context efficiency comes from bounded packets, selected references and reuse of unchanged evidence. The question catalogs require actual evidence; listing them does not perform an assessment.
Canonical local task changes use validation, the cooperating CLI lock and
atomic JSON replacement, then regenerate CURRENT.md and six status views.
Plans, events, reviews, memory and external task lists retain their distinct
responsibilities.
Agenda/Access JSON is canonical. The stock XLSX has five sheets; a guarded
selected-scope export creates a six-sheet view under ignored local/.
agenda workbook-check detects stale data. Reviewed intent remains separate
from actual OS, GitHub, cloud and provider authorization.
ROOT uses explicit mappings and retained observations with revision, original
time and evidence. root delta compares those saved records. The chosen host
or connector performs an actual external observation or change. Missing, stale
and unavailable surfaces remain visible gaps.
The host-owned read-only JSON-lines session is explicitly started. Its seven fixed methods use 16 KiB input lines, 512 KiB responses and at most 64 requests per session. Native MCP/ACP adapters and provider sign-in remain separate implementation and host concerns.
This edition examines template 1.11.0-beta.4 at source
3db12866e552a3cdc190d0a23c8f89a87ba3d3b9. Geometry, text, icons and
connectors were rendered directly at native 8K. It is a separate publication
from the twelve beta.3-provenance template SVGs and the original white/blue
master shown in the current film.
All 49 blocks are connected, directed edges have valid endpoints, and worked routes follow actual edges. All 43 cited hashes matched. Fourteen DOM checks covered navigation, routes, search, catalog coverage and zoom/reset. The raster and enlarged sections were visually inspected with width guards and embedded font fallback. Native browser visual verification was unavailable during production; this is not full accessibility or cross-browser acceptance.
Software remains 1.11.0-beta.4, Python package metadata 1.11.0b4, and the white paper edition 2.2. Historical media retain their identities. For a first project, continue with Getting Started Easy Mode.