Vivarta

The umbrella platform. Substrate appearing as multiplicity through superimposition.

Advaita's "one substrate appearing as multiplicity through superimposition" and our "append-only crossings substrate with environment projections" are structurally the same claim. The architectural fit is genuine, not decorative. Names earned this way travel — the team using them won't have to be told what they mean once they understand the system.

Why "Vivarta"

Vivarta is the specific Advaita Vedanta doctrine that change is apparent in something that doesn't actually change. Brahman is unchanging; the world's apparent transformation IS the world. Our substrate is unchanging; the per-environment deployed projections are vivarta. The doctrine names the architecture rather than gesturing at the tradition. CLI reads cleanly: vivarta deploy --target prod.

Component family

A coherent map under one umbrella; the doctrine supports it cleanly.

Name	Role	Operation it names
Vivarta	Umbrella platform	The substrate appearing as multiplicity through projection
Sruti	Service / tag registry	"That which is heard" — revealed canonical truth
Smriti	Knowledge base, taxonomy, docs	"That which is remembered"
Sakshi	Audit / observability	The witness consciousness — sees and records every crossing without participating
Pramana	Verification, scenarios, testing	The valid means of knowledge — establishes deploy truth
Adhyasa	Templating / overlay engine	Superimposition — projection of attributes onto a base
Viveka	Policy / discrimination / deny-by-default	The faculty that distinguishes real from apparent, safe from destructive
Lila	Playground / dry-run / scenario sandbox	Divine play
Drishti	Dashboards / views / vantage points	Seeing

The full system reads as a deliberate mapping of Advaita's epistemology onto platform substrates: substrate-appearing-as-multiplicity, the witness, the remembered tradition, the revealed canon, the tools of valid knowledge, the projection mechanism, the discrimination, the play, the seeing. Each name does conceptual work; none is purely Sanskrit costume.

Why not "Advaita" the platform

The company is already Advaita; the platform is of the tradition without being a redundant restatement. Components inherit the philosophical lineage from the company name without competing with it.

Alternative umbrella candidates considered

• Sadhana — practiced path, the disciplined sequence the practitioner walks. Less metaphysically loaded than Vivarta, more about the lived experience of running the platform daily. "The sadhana of getting code to prod" reads as ritual without irony. Lost on architectural fit — Sadhana names the experience, Vivarta names the form.
• Pramana — valid means of knowledge. Advaita recognizes six pramanas (perception, inference, comparison, postulation, non-perception, testimony), each a way to establish truth. Promoted to a component name (verification / scenarios / testing) rather than the umbrella.

Naming conventions

• Drop diacritics for code and CLI use. vivarta, sadhana, sakshi — the diacritic-free transliterations are conventional in English-language Sanskrit usage and avoid Unicode handling issues in shells and config files.
• Verify prior tech use before locking a name. "Sadhana" has been used as a meditation app name; "Lila" is a Microsoft Research RL library; "Brahman" appears in distributed-systems papers. Vivarta, Sakshi, Smriti, Sruti, Pramana, Adhyasa, Viveka, and Drishti are mostly clean as far as I know — verify before committing.