Visual Reference

This page is the visual companion for the operating corpus. Use it when you need to orient yourself quickly across the company graph, the work graph, the skill system, and the docs site itself.

Quick Index

LayerVisualBest ForSource Material
Organizational topologyOpen SVGSeeing the company divisions and ownership modelTremor Company Appendix, Org Chart
Team / agent hierarchyOpen SVGReading the reporting tree and role rosterTremor Teams Appendix, Tremor Agents Appendix, Expanded Skills Matrix
Project-task-routine hierarchyOpen SVGMapping goals, projects, issues, and routinesProjects, Tasks
Skill system structureOpen SVGReading the skill stack from shared base layer to local Tremor skillsSkills README, Company Ops, Strategy
Docs-site information architectureOpen SVGFinding the right docs section and understanding how operating docs sit beside the main siteDocs Site Review, Docs Style Guide

How To Read This Page

The diagrams are arranged from the widest system boundary to the most navigable surface:
  1. company topology
  2. reporting and role hierarchy
  3. work hierarchy
  4. capability hierarchy
  5. docs-site navigation
If you are trying to answer “where does this belong?”, start with the first two diagrams. If you are trying to answer “what should I read next?”, start with the last one.

Organizational Topology

Organizational topology diagram Tremor is organized as a four-division operating graph: Leadership Cell, Nervous System Division, Sensory Engine Division, and Fidelity and Quality Division. The topology emphasizes ownership boundaries, not just titles. Primary source anchors:

Team And Agent Hierarchy

Team and agent hierarchy diagram This view shows the reporting chain the source corpus uses for delegation, escalation, and role-specific ownership. It is the fastest way to see which roles sit in the leadership cell and which roles are division-owned. Primary source anchors:

Project, Task, And Routine Hierarchy

Project-task-routine hierarchy diagram Use this view when you need to trace work from the company goal into projects, starter tasks, and recurring routines. The delivery project carries the roadmap branches; the studio operations project carries cadence and hygiene work. Primary source anchors:

Skill System Structure

Skill system structure diagram This diagram separates the shared Paperclip skill layer from the Tremor-local skill families. The local catalog is intentionally specific: governance, platform, sensory, product, verification, research, and release hygiene each live in their own lane. Primary source anchors:

Docs-Site Information Architecture

Docs-site information architecture diagram This is the navigation map for the docs site as a whole. It highlights the main top-level sections, then shows where this operating reference sits as an additive companion to the existing Tremor operating cabinet. Primary source anchors:

Use It As A Navigation Aid

When you land on a source page and need to branch outward, follow this order:
  • use the docs-site IA to choose the right section
  • use the work hierarchy to identify the object you are touching
  • use the team hierarchy to find the owner
  • use the skill system to find the smallest useful capability
  • use the topology diagram when you need a broader company view
If you are maintaining the corpus, keep this page updated whenever the org chart, roster, project tree, skill catalog, or docs-site structure changes.