The Three Layers of Digital SanSkrit.

Layer 1

The Compositional Rules

Phonetics & Grammar (Śikṣā & Vyākaraṇa)

1.1 · Visual Phonetics — The Atomic Primitives (Dhātus)

Every icon in Digital SanSkrit derives from irreducible visual phonemes — not arbitrary shapes, but semantic primitives with fixed meaning fields, analogous to Sanskrit roots that carry the core semantic charge.

1.2 · Morphology — Icon Construction (Samāsa)

Digital SanSkrit uses six compound types, each with strict compositional syntax.

1. Avyayībhāva — Adverbial / Modifier Prefix

A small badge (≤20% of base icon area) prepended to alter the base meaning without changing its core identity. Syntax: [Modifier] + [Base]. The base retains identity; the modifier adds modality.

2. Tatpuruṣa — Determinative / Attributive

A base icon qualified by a second icon that narrows its semantic scope. Syntax: [Qualifier] → [Base]. The base is the head; the qualifier specifies. Example: □ + 👤 = user-container.

3. Karmadhāraya — Descriptive / Appositional

Two icons of equal semantic weight fused into a single glyph where both modify each other. Syntax: [A] ≈ [B] with 50% overlap. Example: ⚡ + ○ = active-energy-state.

4. Dvigu — Numerical / Quantitative

A numerical indicator (stroke count, dot count, small numeral) modifying the base. Quantification without changing base identity. Example: ●●● + □ = triple-container.

5. Bahuvrīhi — Exocentric / Relational

The compound refers to something outside both components — a relationship or system property. Syntax: [A] ↔ [B]. Example: ○—○ = dependency. Neither circle is the meaning; the connection is.

6. Āmreḍita — Iterative / Reduplicative

Repetition of the same icon to indicate plurality, intensity, or distribution. Example: ○ ○ ○ = multiple states or distributed nodes.

1.3 · Syntax — Spatial Grammar (Vākya)

How icons relate in space carries grammatical meaning.

1.4 · Semantics — Domain Ontology (Śāstra)

The Principal Designer defines the closed-system ontology — what concepts exist in the high-tech product domain and how they map to icon compounds.

Layer 2

The Training Methodology

Teacher–Student Lineage (Guru-Śiṣya Paramparā)

DesignOps training for Digital SanSkrit follows a graded fluency model — from recognition to composition to grammaticality judgment.

Stage 1 · Devanāgarī Recognition (Weeks 1–2)

Goal: sight-read the 6 dhātus and 20 most common compounds.

• Flashcard drilling: glyph → name concept → decompose to dhātus.
• Error highlighting: identify violations of the sandhi-rules.
• Speed tests: 50 glyphs in 2 minutes with 95% accuracy.

Deliverable: Certification as Śikṣā-vid — phonetics-knower.

Stage 2 · Samāsa Composition (Weeks 3–4)

Goal: build correct compounds from concept descriptions.

• Prompted construction: “Design a glyph for urgent-review-of-blocked-deployment.”
• Peer review pairs: Generator proposes, Synthesizer validates against sūtras.
• Red-team testing: apply compounds in ambiguous contexts to break them.

Deliverable: Certification as Samāsa-kāra — compound-maker.

Stage 3 · Vākya Arrangement (Weeks 5–6)

Goal: compose multi-icon sentences for dashboard and task-board layouts.

• Spatial grammar exercises: arrange 5–10 icons to represent a sprint workflow.
• Ambiguity resolution: defend the clearer of two valid arrangements via sandhi-rules.
• Cross-functional translation: measure comprehension without verbal explanation.

Deliverable: Certification as Vākya-vid — sentence-knower.

Stage 4 · Śāstra Authority (Ongoing)

Goal: Principal Designer level — ability to extend the language.

• Sūtra drafting for new dhātus or samāsa types.
• Ontology mapping of new product domain concepts.
• Governance: review Samāsa-kāra proposals; approve or reject with sūtra citations.
• Paramparā teaching: mentor two Śikṣā-vids to Śāstra level.

Deliverable: Title of Vyākaraṇa-ācārya — grammar-master.

Training Artifacts

Layer 3

Technical Enforcement Tooling

Guardian of the Canon (Śāstra-Rakṣaka)

3.1 · Figma Plugin Architecture — The Digital SanSkrit Linter

Category A · Dhātu Validation (Primitive Integrity)

Every icon must decompose to the approved 6 primitives. Reject any custom SVG path not matching canonical primitive geometry. ERROR — blocks component publish.

Category B · Samāsa Validation (Compound Legality)

Compounds must follow one of the 6 samāsa types with correct syntax: modifier badges ≤20% base area; overlap percentages matching their samāsa type; no unapproved dhātu combinations. WARNING for drafts; ERROR when published to library.

Category C · Vākya Validation (Spatial Grammar)

Adjacent icons must resolve sandhi (no ambiguous 1px gaps). Connection lines must terminate at canonical anchor points. Containment must respect hierarchy — no circular containment.

3.2 · Plugin Feature Specification

3.3 · CI/CD Pipeline Integration

Figma File → SanSkrit Linter → Token Export → Code Generation → Platform Render
                  ↓                  ↓                ↓
            [ERROR / WARN]      [W3C JSON]    [React / Swift / XML]
            Block if ERROR       semantic       platform-specific
                                 tokens         icon libraries

Closed system (internal tooling): linter runs in Figma only; no export. Open system (product surfaces): linter gates the token export pipeline; violations block release.

3.4 · Enforcement Severity Matrix

3.5 · Principal Designer Dashboard

In summary

The Three Layers in Practice

Digital SanSkrit succeeds when these three layers operate as a closed system internally — the Principal Designer controls the grammar, training produces fluent practitioners, and tooling enforces compliance. The open system exports only the rendered output to external platforms, never the grammar itself. This preserves linguistic integrity while enabling broad deployment.

एक भाषा, अनन्त रूप · One language, infinite forms.