Root Solve · Design Chart

Graphical chart

A coherent visual system pulled from the company mark: electric cyan circuitry, living leaf green, and deep charcoal resolve. Use this page as the visual reference for the Root Solve system, and as a model for the charts we build for your brand.

Cyan tech Leaf growth Sovereign

Effects

Chart effects are optional canvas overlays. Enable with data-rs-effects="growth circuits" on <body>, or call the APIs below. Document-space positions stay put while scrolling and keep simulating off-screen. Respects prefers-reduced-motion.

growth: branches (visible stems) and leaves from viewport borders.
circuits: orthogonal PCB-like traces, pads, vias, and chips.

<body class="rs-circuit" data-rs-effects="growth circuits">
<script src="chart/effects.js?v=11" defer></script>

Color

Typography

Heading 1: Root Solve

Heading 2: Sovereign systems

Heading 3: Solve at the source

Heading 4: No hostages

Heading 5: Clear ownership
Heading 6 · Section label

Body copy uses DM Sans for calm readability. Display faces use Syne: geometric enough for tech, bold enough to carry the brand.

JetBrains Mono covers code, tokens, and technical identifiers.

Inline text

This paragraph shows a link, strong emphasis, italic stress, bold, italic, underline, strikethrough, highlighted insight, fine print, RS, Sovereignty Manifesto, root cause, x = solution, Ctrl + K, inline rs-btn, and build complete. Shipped on . Contact: .

Subscript H2O and superscript E=mc2 for completeness. forty-two as a data value. Own the root, keep the keys.

Blocks

We build sovereign solutions so customers can solve their root problems without being taken hostage by vendors, stacks, or lock-in. Root Solve
/* Chart entry */
@import url("./chart.css");

.button {
  color: var(--rs-cyan);
}

Horizontal rule above separates organic growth from circuit precision.

Lists

Unordered

  • Own your infrastructure
  • Exit without friction
  • Solve the root, not the symptom
    • Diagnose
    • Remediate

Ordered

  1. Map the dependency
  2. Cut the hostage path
  3. Hand back control

Description list

Sovereign
You hold the keys, data, and decision rights.
Root problem
The underlying constraint that keeps resurfacing as tickets and toil.
No hostage
Architecture that lets you leave cleanly when you choose.

Media

Root Solve logo: ape with circuit brain and living foliage
Company mark: bio-cyber intelligence at the root.
Circuit pulse 0:00 / 0:00

Chart audio widget: cyan/leaf track, mono time, wave meter.

Field reel 0:00 / 0:00

Chart video widget: cyan void stage and sovereign control bar. Add an mp4 source when you have footage.

Inline SVG accent:

Tables

Engagement model snapshot
Phase Focus Outcome
Discover Root cause map Shared diagnosis
Build Sovereign path Working system you own
Release Handover Keys, docs, exit plan
No perpetual tether required.

Status matrix

Live service posture (demo data)
Surface Owner SLA Status
Automation APIs Platform 99.5% Healthy
Root Defense edge Security 99.9% Watching
Vendor bridge Integrations 98.0% Degraded
Legacy tether Exit desk — Cut pending

Dense comparison

Hostage risk vs sovereign path · sample scores
Dimension Hosted SaaS Root Solve path Delta
Exit clarity 22 94 +72
Data custody 35 91 +56
Runtime control 18 88 +70
Surprise cost 76 19 −57

Scrollable schedule

Discovery workshop slots
Slot Timezone Room Facilitator Focus Seats
CET Circuit A Ada Root map 8
CET Leaf Lab Grace Exit drill 6
CET Void Deck Alan API agents 10

Forms

Contact form
We reply from a human inbox.

Preferred contact

Buttons

Link as button

Interactive

What does “sovereign” mean here?

You control runtime, data, and exit. We design so leaving is a feature, not a crisis.

How do engagements end?

With documentation, credentials you own, and a path that does not require us.

68%

82

Events

Chart-styled overlays for modal flows and JS-triggered notices. Prefer these over raw alert() / confirm() in product UI.

Modals

Sovereign handover

Keys, runbooks, and exit credentials stay with you. This native <dialog> uses chart chrome and backdrop blur.

  • Runtime under your control
  • No perpetual tether
  • Documented cutover path

Cut the tether?

This demo confirm replaces window.confirm. Choose cancel to keep the bridge, or confirm to schedule the cut.

Name the engagement

JS alerts (toasts)

Stacked notices via RootSolveChart.toast — chart tokens, auto-dismiss, keyboard-safe.

Browser fallbacks

Event log idle.

Alerts & status

Info: discovery workshop scheduled.
Success: handover package delivered.
Warning: single vendor dependency detected.
Danger: lock-in path still open.
Info Ok Warn Danger

Landmarks & sections

Article

Semantic <article> for self-contained pieces.

Updated

Section

Grouped content under a shared heading.

Root Solve

rootsolve.org

Widgets

Reusable campaign widgets for lead-ins and events: a sovereignty scorecard, a root-cause timeline, and a silent booth loop. Same chart language as the rest of the system. Adapt the copy and host them under accounts your customer owns.

Sovereignty scorecard

A short quiz that rates lock-in risk across providers, keys, and exit paths, then invites a prospect to talk.

1 / 4

Who owns the cloud / host accounts today?

Root cause timeline

An interactive before/after story of a recurring outage or debt loop, with a clear sovereign alternative for the audience.

Recurring outage loop

Patch the symptom. Firefight. New vendor tether. Same failure returns next quarter.

Sovereign rebuild

Name the root constraint. Move accounts and keys under you. Document exit. The loop stops regenerating.

Conference booth loop

A silent full-screen reel mixing games, banners, and one CTA for tablets or stand screens.

Root Defense Protect the technical tree. Earn Roots. Clear the wave.
Your keys. Your exit. Sovereign solutions without lock-in, on providers you choose.
Root Router Route workloads to the solution. Skip the sinks.
Talk to Root Solve Share the problem that keeps growing back. Start the conversation. Tell us about your needs