OpenYantra
Brand Identity & Design Manual
v2.13
Version
11
Chapters
MIT
License
DNA: Teenage Engineering + Sarvam AI
Scroll
01 / Brand Foundation

Why OpenYantra exists.

A personal AI memory system built on one principle: the human is always in control. Every design decision flows from this.

01
Personal Cognition Ledger
OpenYantra is not enterprise software. It is a daily personal tool that captures ideas instantly, preserves long-term context, and allows multiple AI agents to share one memory while keeping the human fully in control of their data.
02
Local-First, Always
All memory lives on your machine in a file you can open, read, and edit in any spreadsheet application. No cloud, no accounts, no vendor lock-in. Your cognitive history belongs to you.
03
Simple Over Clever
If a feature introduces unnecessary complexity it is rejected. Simplicity is not a style choice -- it is an architectural constraint enforced at every layer of the system.
Source 01
Teenage Engineering
Utilitarian grid. Exposed structure. Bold flat single-function colors. Monospaced type. Playful deconstructivism. Every element serves a purpose. Inspired by post-Bauhaus Ulm School, Dieter Rams, and physical instrument UI panels.
Source 02
Sarvam AI
Blue-to-orange spectrum as foundational language. Colors operate as continuous transitions, not fixed blocks. Mandala-derived geometric construction logic. Contemporary letterforms. Grounded, modern, rooted in Indian design heritage.
Technical
Precise, deterministic language. No vague promises. Every claim is implementable.
Direct
Short sentences. Imperative verbs. No filler. Copy reads like a CLI command.
Human
Not cold. The system serves one person. Language is warm without being corporate.
Transparent
Audit trails visible. Architecture explained. No black boxes in language or code.
03 / Color System

The Spectrum.

Five functional accent colors derived from the TE-Sarvam fusion. Each maps to a role in the architecture. Three neutrals for surfaces, four for text hierarchy.

Yantra Blue
#1C6FFF
Primary / Nav
Chitragupta Indigo
#5535E0
Writer / Hash
Ledger Coral
#E84520
Alert / Prompt
Sanchitta Amber
#F5A000
Queue / Command
Vidya Green
#1AA167
Status OK
Ink
#0A0A0B
BG Base
Surface
#111113
Card / Panel
Surface 2
#161618
Hover State
Dim
#242228
Borders / Rules
Muted
#524F58
Labels / Meta
Parchment
#E8E5DE
Body Text
Primary Gradient
linear-gradient(135deg, #1C6FFF 0%, #5535E0 32%, #E84520 66%, #F5A000 100%)
Used on the logo mark, primary CTAs, and the top page bar. Direction: 135deg. 4 stops matching the 4 cardinal node colors.
Horizontal Gradient
linear-gradient(90deg, #1C6FFF 0%, #5535E0 32%, #E84520 66%, #F5A000 100%)
Used on chapter top bars, section dividers, and horizontal accent strips. Always left-to-right directional.
Context
Blue
Indigo
Coral
Amber
Green
04 / Typography

IBM Plex Mono.

A single typeface family across the entire system. IBM Plex Mono for UI, code, labels, and headings. IBM Plex Sans (Light only) for body copy and descriptions.

Display
OpenYantra
48px / -0.025em
300
Heading 1
Personal Cognition Ledger
32px / -0.02em
300
Heading 2
Chitrapat.ods
22px / 0.02em
500
UI / Panel
Memory State -- Active
14px / 0.04em
500
Body
A local-first personal memory system for AI agents. One human, one file, full auditability and transparency.
14px / 1.7
Sans 300
Label
Single Writer Rule -- LedgerAgent
10px / 0.2em
400 caps
Micro
SHA-256 · v2.13.0 · MIT
9px / 0.18em
400 caps
Code / CLI
$ yantra inbox "idea"
13px / 0.02em
400
Headings + Labels
Write Queue
Sanchitta -- Active
Mono display weight 300 for headings. Mono caps 400 for labels. Never mix sans and mono at the same hierarchy level.
UI + Body
Chitrapat.ods -- Memory State
247 records across 4 memory types. Last write 4 minutes ago by Chitragupta.
IBM Plex Sans 300 for paragraphs and descriptions only. All interactive elements remain in Plex Mono.
05 / Iconography & Geometry

Mandala Language.

All geometry is derived from the mandala construction principle. Circles, radial lines, and petal arcs at multiples of 45 degrees. No arbitrary curves.

Rule 01
Circle-Based
All primary forms derive from circles. Squares and rectangles are used only for UI containers and text blocks.
Rule 02
45° Increments
Radial lines rotate in 45° increments. 8 cardinal directions: N, NE, E, SE, S, SW, W, NW.
Rule 03
Concentric Rings
Nested circles at proportional radii encode system layers: outer boundary, ledger, inner domain, center core.
Identity
SessionLog
Inbox
Tasks
Goals
Beliefs
People
OpenLoops
06 / Web UI Design

Desktop Interface.

The yantra UI browser interface. Dark-first, grid-based, instrument panel aesthetic. Fast, inspectable, correctable.

localhost:7432 -- yantra ui
OpenYantra
Memory
Overview
SessionLog
OpenLoops
Tasks
Beliefs
Agents
Chitragupta
VidyaKosha
AgentConfig
System
Ledger
Health
Chitrapat.ods
Memory Overview
Refresh
+ Inbox
247
Records
12
Open Loops
489
Ledger Entries
4
Agents Active
Memory Distribution Live
Episodic
247
Semantic
133
Prospective
89
Beliefs
41
Recent Sessions
async write batching
VidyaKosha4m ago
refactor BM25 index
VidyaKosha2h ago
OpenLoops review
Karma1d ago
07 / Mobile UI Design

Mobile Screens.

The yantra mobile companion. Capture ideas instantly, review open loops, and check memory health from your phone. Dark-first, thumb-reachable navigation.

Home
9:41●●●
OpenYantra
247
Records
12
Loops
OK
Health
489
Ledger
Quick Capture
Capture an idea...
Recent
async write batching
4m ago
refactor BM25 index
2h ago
Home
Loops
Memory
Health
Open Loops
9:41●●●
Open Loops
12 unresolved
refactor VidyaKosha BM25
14 days -- Critical
write async batch docs
7 days -- High
add SHA-256 tests
3 days -- Medium
review AgentConfig schema
1 day -- Low
explore embedding support
Open -- No deadline
Home
Loops
Memory
Health
Memory View
9:41●●●
Memory
Chitrapat.ods -- 1.2MB
Episodic
247
Semantic
133
Prospect.
89
Recent Records
async write batching
#a3f9d2c1
Signed
refactor BM25 scoring
#b9e124a0
Signed
Home
Loops
Memory
Health
Health
9:41●●●
System Health
All systems nominal
Chitrapat.ods
1.2MB -- Readable
OK
Ledger
489 entries -- Valid
OK
Signatures
SHA-256 -- All valid
OK
WriteQueue
0 pending
OK
Chitragupta
Last write: 4m ago
OK
Home
Loops
Memory
Health
08 / CLI Design

Terminal Interface.

The primary interface. Every command is short, predictable, scriptable. The color theme maps each syntax role to a specific palette token.

Syntax Roles
PROMPT $
#E84520 Ledger Coral
COMMAND yantra
#F5A000 Sanchitta Amber
ARG / PATH inbox
#1C6FFF Yantra Blue
STRING "value"
#1AA167 Vidya Green
HASH #a3f9d2c1
#5535E0 Chitragupta Indigo
FLAG --since
#7A7682 Subtle
STATUS OK / Error
Green / Coral
yantra -- zsh
$yantra inbox "async write batching idea"
Queued WriteID: #a3f9d2c1 → Sanchitta
$yantra loops
12 open loops found
Oldest: "refactor VidyaKosha" -- 14 days
$yantra health
Chitrapat.ods OK -- 1.2MB
Ledger: 489 entries -- Sigs: valid
$yantra recall "BM25" --top 3
3 records -- Relevance: 0.94, 0.87, 0.71
$
09 / UI Components

Component Library.

Reusable UI components for yantra ui and the web interface. All built from design tokens, all using IBM Plex Mono.

Local-First
LedgerAgent
Open Loop
WriteQueue
Signed
v2.13.0
Memory
Ledger
Loops
Agents
Tab panel content -- Memory distribution and record browser.
Chitrapat.ods -- Memory State Active
Episodic
247
Semantic
133
Prospective
89
12
Loops
4
Agents
3
Inbox
OK
Health
Chitragupta
LedgerAgent -- sole writer to Chitrapat.ods. SHA-256 signs every record.
Write
VidyaKosha
Retrieval -- BM25/TF-IDF memory search and context surfacing.
Read
Inbox Agent
Capture -- receives raw inputs from the user and queues to Sanchitta.
Queue
10 / Brand Assets

Ready-Made Assets.

OG card, README banners, and social formats. All sized to spec, all using the full color system.

OpenYantra
Local-first personal cognition ledger for AI agents. One human. One file. Full auditability.
Local-First
Single Writer
SHA-256 Audit
Open Source
github.com/revanthlevaka/OpenYantra
MIT -- v2.13.0
OpenYantra
Personal Cognition Ledger -- local-first AI memory
1
File
12
Sheets
MIT
License
11 / Usage Rules

Do & Don't.

These rules protect the coherence of the OpenYantra brand. They are enforced at both the design and architecture level.

✓ Do
Use variant A (Gradient Dark) as the primary lockup on all dark backgrounds.
Maintain minimum clear space equal to the diameter of one cardinal node dot on all sides.
Scale the mark uniformly, never stretch or distort.
Use variant F (Mono White) on photographic or complex backgrounds.
Use variant E on light-colored backgrounds only.
✗ Don't
Never rotate the mark. The cardinal nodes have fixed directional meaning.
Never recolor individual mark elements. The gradient must remain intact.
Never add drop shadows, glows, or effects to the wordmark.
Never place the gradient variant on a similarly colored gradient background.
Never use the mark below 16px without switching to the favicon-optimized version.
✓ Do
Use Coral (#E84520) exclusively for the CLI prompt symbol and error states.
Use Amber (#F5A000) for the CLI command token and queue/write states.
Use Blue (#1C6FFF) as the primary interactive color in the web UI.
Use Green (#1AA167) only for positive status, success, and health indicators.
Always use the full 4-stop gradient on primary CTAs and the logo mark.
✗ Don't
Never use purple or violet outside the defined Indigo (#5535E0) token.
Never use white backgrounds. The system is dark-first at all times.
Never introduce new accent colors. The 5-token palette is fixed.
Never use the gradient as a background fill for text areas or panels.
Never use Coral as a general accent. It signals error or alert exclusively.
✓ Do
Use IBM Plex Mono 300 for all display headings and hero text.
Use IBM Plex Mono with wide tracking (0.14-0.28em) for all uppercase labels.
Use IBM Plex Sans 300 only for body copy and longer descriptive text.
Keep UI element text in IBM Plex Mono at all times.
✗ Don't
Never use Inter, Roboto, or any system UI font. IBM Plex Mono is non-negotiable.
Never use IBM Plex Mono above weight 600.
Never use IBM Plex Sans for headings, labels, or interactive elements.
Never use justified text alignment. Left-aligned only.
✓ Do
Show the single-writer rule visually in all ecosystem diagrams.
Always label Chitrapat.ods as "Source of Truth" in any architecture visualization.
Display SHA-256 hashes in Indigo (#5535E0) to reinforce the Chitragupta association.
Use the write flow diagram (Agent > Sanchitta > Chitragupta > Chitrapat) consistently.
✗ Don't
Never show multiple agents writing directly to Chitrapat in any diagram.
Never represent the system as a database, cloud service, or distributed system.
Never omit the Ledger layer in architecture visualizations.
Never use marketing language that implies multi-user or enterprise capabilities.
OpenYantra
Brand Identity & Design Manual v2.13.0
© 2025 OpenYantra -- MIT License
Built by Revanth Levaka
DNA: Teenage Engineering + Sarvam AI
github.com/revanthlevaka/OpenYantra ↗