VEDAS\README.TXT EPISTEMIC SUITE: ŚRUTI INTACT
VEDAS / THE MANIFOLD Repository
VEDAS.TXT 00 / THE WAGER

VEDAS / EPISTEMIC EXTENSION OF THE MANIFOLD

The model is ephemeral (Śūnya).
The truth is immutable (Akṣara).

Ancient Vedic thinkers faced the exact problem modern autonomous coding agents face: preserving complex, high-dimensional systemic truth across successive generations of ephemeral, amnesiac participants without semantic drift, hallucination, or bit rot.

The Manifold offloaded project state into reproducible text so the model just has to check. Vedas gives that memory an epistemology. By separating truth into three speeds (Śruti invariants, Smṛti history, and Vartamāna temporal handoffs) and requiring rigorous Pramāṇa proof tags for every claim, Vedas guarantees zero drift across sessions. Every fact has a test, a receipt, and an immutable history.

VEDAS_SESSION_089.TXTSPECIMEN
$ cat docs/HANDOFF.md
# Session Handoff
Last updated: 2026-11-04

## Current state
Tokenizer ....... [OBSERVED] 119/119 pass
Grammar ......... [CONTRACT] INV-006 enforced
Speech .......... [HYPOTHESIS] pending audio
Next task ....... P3-02

$ python3 tools/check_vedas.py --template
0 error(s), 0 warning(s) in 14 file(s)
$ 
EPISTEMIC SUITE14 DOCS / CLEAN
FAILURE_MODES.TXT 01 / THE FAILURE

THE FAILURE

Ephemeral contexts erase architectural truth.

§ 1.0

A fresh context window provides speed and focus. It is also where institutional knowledge vanishes. When an AI session ends, its rationale disappears unless the repository enforces strict epistemic persistence.

The unrecorded invariant

Session two reintroduces a naive pattern because session one only discussed the restriction in chat. The code compiles, but the system architecture degrades.

The epistemic hallucination

A handoff claims a subsystem works because the author assumes it does. Nobody ran the test command. The next session builds atop unverified speculation.

The sycophantic opener rut

Without hard lexical and behavioral firewalls, models lapse into predictable, repetitive pleasantries and stock empathy clichés, diluting focus and token budgets.

The problem is not that AI models hallucinate. It is that standard repositories permit unverified claims to pose as ground truth.

EPISTEMICS.TXT 02 / THREE SPEEDS OF TRUTH

THE FOUNDATION

Three speeds of truth: Śruti, Smṛti, and Vartamāna.

§ 2.0

In traditional software development, documentation is treated as a uniform pile of text. Vedas separates repository truth into three distinct temporal tiers, each governed by strict mutability rules.

IMMUTABLE / ETERNAL

Śruti: System Axioms

The bedrock laws of physics for the project. These invariants cannot be violated, relaxed, or edited without explicit maintainer consent.

  • docs/INVARIANTS.md houses core rules (INV-001 to INV-010).
  • Every invariant is bidirectional and citeable.
  • Mechanically guarded by automated lint tools.

APPEND-ONLY / EPOCHAL

Smṛti: Architecture & History

Institutional memory and historical precedent. Past decisions are superseded rather than erased, showing why dead ends were rejected.

  • docs/DECISIONS.md stores architectural decisions.
  • ROADMAP.md assigns stable, permanent task identifiers.
  • docs/CHANGELOG.md captures user-facing evolution.

REWRITE / LIVING PRESENT

Vartamāna: Living State

The immediate present moment. Stale claims are deleted immediately. The file is capped at 80 lines and overwritten every session.

  • docs/HANDOFF.md records verified current status.
  • Every bullet must carry a Pramāṇa proof badge.
  • Old entries are condensed into Sūtras or purged.
VEDANGAS.TXT 03 / REPOSITORY TOPOLOGY

REPOSITORY ANATOMY

The Six Vedāṅgas: Ancient sciences of structure.

§ 3.0

Just as classical scholars maintained oral texts without textual decay for millennia through six specialized disciplines, Vedas organizes repository architecture across six auxiliary limbs.

ŚIKṢĀ: PHONETICS & ORTHOGRAPHY

The Lexical Firewall (INV-006)

Enforces strict stylistic hygiene across all documentation and comments. Bans generic stock empathy, chat filler, and typographical quirks like em dashes to maintain crisp, machine-verifiable prose.

CHANDAS: METRICAL BOUNDS

Token & Line Economy (INV-005)

Imposes strict structural bounds. Session handoffs are strictly capped at 80 lines, and core architectural propositions (Sūtras) must not exceed 25 words. Brevity preserves cognitive bandwidth.

VYĀKARAṆA: FORMAL GRAMMAR

Contract & Schema Linters

Mechanically guarantees repository integrity through tools/check_vedas.py. Validates invariant reciprocity, verifies cross-references, and blocks malformed handoffs before commit.

NIRUKTA: ETYMOLOGY & LEXICON

Canonical Glossary & Terminology

Maintains unambiguous domain vocabulary in docs/GLOSSARY.md. Defines canonical terms, their historical counterparts, and nearby traps to avoid semantic drift between sessions.

JYOTIṢA: CHRONOMETRY & CALENDAR

Immutable Task IDs (INV-003)

Tracks roadmap execution with immutable identifiers (e.g. P1-01, P2-04). Tasks are never renumbered or repurposed. Abandoned tasks record what was learned.

KALPA: RITUAL PROCEDURE

The 5-Stage Session Ritual

The standard operating procedure executed on every session entry and exit. Governs orientation, verification, surgical changes, validation, and handoff compilation, with spiral Āvartana loopback when a local part reshapes the whole.

EPISTEMIC_PROOF.TXT 04 / VERIFICATION PROTOCOL

EPISTEMIC VERIFICATION

Pramāṇa proof tags & the Nyāya sequence.

§ 4.0

In Vedas, vague assertions like "the exporter works" are prohibited. Every claim must carry a Pramāṇa badge indicating its exact source of epistemic authority.

The Five Pramāṇa Epistemic Badges

[OBSERVED] Direct verification. Confirmed by executing a test or tool in the current session.
[DEDUCED] Logical deduction. Inferred from static analysis, type proofs, or invariants.
[CONTRACT] Formal invariant or schema contract defined in Śruti or architecture docs.
[HYPOTHESIS] Working theory or unverified speculation. Requires subsequent test verification.
[UNTESTED] Existing capability not executed in this environment or session.

Nyāya Pañca-Avayava: The 5-Step Proof Sequence

When resolving defects or adding features, agents follow the classical Nyāya five-part syllogism to guarantee reproducible changes:

01 Pratijñā (Proposition) State the required behavior or bug clearly. Example: "Opener ruts occur when the last three assistant responses share identical starting tokens."
02 Hetu (Defect Reason) State the causal root mechanism producing the failure. Example: "Context generation lacks a negative penalty for preceding opening n-grams."
03 Udāharaṇa (Negative Proof) Author a localized, offline test proving the defect exists. Observe the test fail cleanly before writing implementation code (INV-007).
04 Upanaya (Implementation) Apply the minimal, surgical code modification required to satisfy the failing test condition.
05 Nigamana (Verification) Re-run the entire test suite to verify that the failure is resolved and no regressions were introduced. Mark with [OBSERVED].
LEXICON.TXT 05 / PRONUNCIATION & GLOSSARY

PHONETIC GUIDE

Ancient terminology, phonetic English & audio synthesis.

§ 5.0

Vedas uses classical Sanskrit terminology to provide precise epistemic distinctions. Use the interactive pronunciation guide below to master each term. Click the audio buttons to hear native synthesized speech.

FILTER LIVE / CLICK AUDIO TO HEAR
Term Phonetic Guide Audio Plain English Meaning Software Equivalent
Śruti SHROO-tee That which is heard; revealed immutable truth Immutable invariants (INV-001 to INV-010)
Smṛti SMRIH-tee That which is remembered; historical recollection Append-only ADRs and architecture memory
Vartamāna var-tuh-MAH-nuh The immediate living present moment Session handoff (docs/HANDOFF.md, 80-line cap)
Pramāṇa pruh-MAH-nuh Valid means of knowledge or legitimate proof Epistemic proof tags ([OBSERVED], [DEDUCED])
Pratyakṣa pruh-tyuhk-SHUH Direct perception and empirical observation Direct test output and telemetry telemetry
Anumāna uh-noo-MAH-nuh Inference based on causal deduction Static analysis and logical deduction
Sūtra SOO-truh Aphorism; high-density, minimal-syllable rule Dense propositional invariant (<25 words)
Śūnya SHOO-nyuh Emptiness; unconditioned, clean baseline Fresh context window ready for execution
Ghana-pāṭha GUH-nuh PAH-tuh Dense bidirectional recitation algorithm tools/check_vedas.py invariant reciprocity linter
Kalpa KUHL-puh Ritual procedure and systematic ceremony Standard operating session loop
Vyākaraṇa vyah-kuh-RUH-nuh Grammatical analysis and formal structure Contract validation, schemas, and linting
Nirukta nih-ROOK-tuh Etymological explanation and canonical lexicon Canonical project glossary (docs/GLOSSARY.md)
Chandas CHUHN-duhs Metrical rhythm, bounds, and syllable counts Line count caps, token economy limits
Jyotiṣa JYOH-tih-shuh Chronometry, astronomical time, and calendar Roadmap scheduling and stable task identifiers
Śikṣā SHEEK-shah Phonetics, correct pronunciation, and tone Lexical firewall and formatting discipline
Nyāya NYAH-yuh School of logic, epistemology, and reasoning Rigorous test-driven verification method
Saṃśaya SUHM-shuh-yuh Recognized epistemic doubt or competing interpretations Ambiguous scope or part-whole gap blocking action
Praśna PRUHSH-nuh Targeted inquiry that resolves doubt Pre-execution clarifying question (INV-009)
Adhyāsa uhd-YAH-suh Superimposition of prior expectations onto reality Projecting training defaults onto the codebase (INV-010)
Āvartana ah-VAR-tuh-nuh Spiral turning back; part-whole recurrence Looping from Build/Verify back to Scope when a premise breaks (INV-009)
Pratibandha pruh-tih-BUHN-dhuh Epistemic obstruction or resistance of the text Code or test friction that halts workarounds and triggers inquiry (INV-007, INV-009)
Pūrva-Pakṣa POOR-vuh PUHK-shuh Prior position; the originating question behind a rule Reconstructing why a constraint exists before altering it (INV-004, INV-009)
Ubhaya-Saṃkaṭa oo-BHUH-yuh SUHM-kuh-tuh Two-sided dilemma; two true claims held in tension Held Tension (T-NNN) in docs/DECISIONS.md with owner and review trigger
Kṣetra KSHEH-truh Bounded field or sovereign domain Zone boundary (one repository and its local authority rules)
CHEAT_SHEET.TXT 06 / QUICK REFERENCE

QUICK REFERENCE

The Epistemic Cheat Sheet.

§ 6.0

A fast, interactive desktop reference for daily use during agent sessions. Click the tabs below to copy exact patterns and commands.

Session Entry Ritual (Start of Session)

1. Read docs/HANDOFF.md
2. Read docs/INVARIANTS.md (Śruti core rules)
3. Run python3 tools/check_vedas.py --template
4. Run fast regression tests (docs/TESTING.md)
5. Inspect git status to verify clean working tree

Session Exit Ritual (Handoff & Exit)

1. Run offline verification tests
2. Run python3 tools/check_vedas.py --template
3. Update docs/HANDOFF.md (<80 lines, with Pramāṇa badges)
4. Check git diff for unrelated changes or em dashes
5. Commit and push clean state

How to Tag Claims in docs/HANDOFF.md

Every claim regarding test results, subsystem health, or environmental support must begin with one of these tags:

[OBSERVED] Test suite passes: 119/119 tests clean in 0.42s.
[CONTRACT] Invariant INV-006 strictly rejects all em dashes.
[DEDUCED] Parser handles UTF-8 correctly because tokenizer accepts bytes.
[HYPOTHESIS] Flaky test on Safari caused by missing SpeechSynthesis mock.
[UNTESTED] Audio playback on mobile WebKit not yet validated.

The Nyāya Pañca-Avayava Checklist

Use this five-step sequence for every bug fix or feature implementation:

Pratijñā (Proposition): The bug to fix or feature to add
Hetu (Defect Reason): The causal mechanical reason for the issue
Udāharaṇa (Negative Proof): Write failing offline regression test first
Upanaya (Implementation): Apply surgical, minimal code fix
Nigamana (Verification): Verify test passes cleanly [OBSERVED]

Sūtra Authoring Rules

Sūtras compress complex architectural laws into dense, memorable propositions:

  • Brevity: Under 25 words per Sūtra.
  • Clarity: Zero ambiguous adjectives, zero fluff.
  • Completeness: Unconditionally true within its domain.
  • Consolidation: When a handoff exceeds 80 lines, background learnings are consolidated into immutable Sūtras inside docs/INVARIANTS.md.
Example: "INV-006: Siksa requires zero em dashes across all documentation and comments."

Vedas Śruti Invariants Matrix (INV-001 to INV-010)

INV-001: Every project fact has exactly one authoritative home.
INV-002: Decisions record the discarded path, not just the winner.
INV-003: Roadmap task IDs are permanent and immutable.
INV-004: All truth claims must carry an explicit Pramāṇa badge.
INV-005: HANDOFF.md must never exceed 80 lines.
INV-006: Lexical Firewall enforces zero em dashes in prose or code.
INV-007: Every bugfix requires a prior negative test proof.
INV-008: Subconscious consolidation compresses learnings into Sūtras.
INV-009: Zero silent assumptions; halt on Saṃśaya and ask Praśna before building.
INV-010: Purge Adhyāsa; never superimpose external model priors onto the repository.
CHECKER.TXT 07 / GHANA-PATHA VERIFICATION

MECHANICAL ENFORCEMENT

The Ghana-pāṭha verification engine.

§ 7.0

Documentation rules that rely solely on human or agent discipline inevitably decay. Vedas provides a zero-dependency Python script that validates repository health in milliseconds.

GHANA_PATHA_LINTER.SHSPECIMEN
$ python3 tools/check_vedas.py --template
Checking file existence ............................ OK (14 files)
Checking line caps (HANDOFF <= 80 lines) .......... OK
Checking Lexical Firewall (INV-006: zero em dashes) . OK (0 violations)
Checking Ghana-patha invariant reciprocity ......... OK (10/10 reciprocal)
Checking roadmap task IDs and changelog sync ....... OK

0 error(s), 0 warning(s) in 14 file(s)
$ 
VERIFICATION TIME0.042s / ZERO DEPENDENCIES

Bidirectional citation check

Whenever an invariant is cited in AGENTS.md or ARCHITECTURE.md, the linter confirms that it is authoritatively defined in INVARIANTS.md.

Lexical firewall check

Scans markdown, code, and comments to prevent typographical decay and punctuation drift (enforcing INV-006 zero em dash policy).

Metrical boundary check

Enforces the 80-line cap on HANDOFF.md. If a handoff expands beyond bounds, the build fails, compelling immediate Sūtra consolidation.

LINEAGE.TXT 08 / THE ARCHITECTURAL TRIAD

LINEAGE & EPISTEMOLOGY

The Three-Tier Architectural Stack.

§ 8.0

Vedas is an epistemic extension of The Manifold, which in turn extends The Hypervisor. Together, they eliminate context rot and model amnesia across the complete agent lifecycle:

STAGE 01 / CONVERSATION

The Hypervisor

Gives the model a body. Volatile Semantic Leverage, simulated bio-physics, the four-voice Village, sincerity tags, and lexical firewalls inside live sessions.

Explore Hypervisor ↗

STAGE 02 / REPOSITORY

The Manifold

Gives the work a memory. Zero-dependency Markdown contracts, two speeds of truth (rewrite state, append history), 80-line handoffs, and check_docs.py.

Explore The Manifold ←

STAGE 03 / EPISTEMOLOGY

Vedas

Gives the memory an epistemology. Three speeds of truth (Śruti/Smṛti/Vartamāna), Pramāṇa proof tags, Sūtra density, and bidirectional Ghana-pāṭha checks.

Back to top ↑

The Hypervisor gives a model a body. The Manifold gives the work a memory. Vedas gives that memory an epistemology.

Adopting Vedas in an Existing Repository

To initialize Vedas in your project, copy the template files into your repository root:

cp -r vedas/docs . && cp vedas/tools/check_vedas.py tools/ && cp vedas/AGENTS.md .
python3 tools/check_vedas.py --template