Selemene Engine

Reflection-First Consciousness Calculation Engine
_{Part of the Tryambakam Noesis Project}

Live: selemene.tryambakam.space  ·  16 engines  ·  6 workflows  ·  Rust + Axum + Supabase + Railway

Not prediction. Reflection. Inquiry. Witness.

Reflection-first astronomical and consciousness calculation engine.

Every system you've tried positioned you as user, not author.

Selemene Engine offers something different: 16 symbolic mirrors that reflect patterns in your birth data, timing, and energetic signature. Not to give answers, but to train self-consciousness.

Built in Rust. Sub-millisecond calculations. 100% astronomical accuracy.

Part of Tryambakam Noesis — a living inquiry field where success means you outgrow the system.

Every System You've Tried...

...positioned you as user, not author.

Apps that gamify meditation. Courses that promise transformation. Retreats that crack you open then leave you alone with the fragments.

Each delivered value while creating dependency.

Selemene offers something different: 16 symbolic mirrors that reflect patterns in your birth data, timing, and energetic signature. Not to give answers, but to train the capacity to witness yourself.

Built Different

• Sub-millisecond calculations — Technical rigor in service of inquiry
• Swiss Ephemeris-backed Vedic core — Panchanga, Vimshottari, and Transits validated against trusted chart references
• 16 engines, one coherence — Vedic, Western, and biofield traditions integrated
• Anti-dependency design — Succeeds when you outgrow it

✦ The Philosophy — Kha-Ba-La, Consciousness Levels & Why This Exists

The Problem

You've tried the apps. The courses. The retreats.

Each promised clarity while positioning you as dependent user, not sovereign author.

• Therapy: Narrates your wounds, but who is the narrator?
• Meditation: Observes thoughts, but who observes the observer?
• Productivity: Optimizes actions, but who chose the target?

The Alternative

Selemene doesn't deliver answers. It offers mirrors — 16 symbolic lenses calibrated to reflect different frequencies of your pattern.

Not prediction. Reflection. Inquiry. Witness.

Kha-Ba-La: The Three Forces

Every calculation operates on three co-arising principles:

Force	Domain	Function
Kha (Spirit)	Awareness, witness	The field that observes
Ba (Body)	Embodiment, action	Vehicle for knowing → doing
La (Inertia)	Resistance, gravity	Friction that gives form

Your "stuckness" isn't the enemy. It's the necessary resistance that makes authorship possible.

Self-Consciousness Levels

The system adapts to your relationship with awareness:

• Level 0 (Dormant): "What sensations arise?"
• Level 1 (Glimpsing): "When does this pattern show up?"
• Level 2 (Practicing): "What might this pattern protect?"
• Level 3 (Integrated): "How do you choose to work with this?"
• Level 4+ (Embodied): "What witnesses this pattern arising?"

This isn't gamification. It's meeting you where you are.

✦ Quick Start

First call in 30 seconds. Experience the mirror. Not the answer.

📖 API Quickstart Zero to first call in 5 minutes

🖥 Terminal TUI Interactive Ratatui interface

🔮 Terminal Explorer CLI for every engine

📜 Swagger UI Full API documentation

First Call in 30 Seconds

# Set your API key
export NOESIS_API_KEY="nk_your_key_here"

# Ask the mirror a question
curl -s -X POST https://selemene.tryambakam.space/api/v1/engines/numerology/calculate \
  -H "X-API-Key: $NOESIS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "birth_data": {
      "name": "Your Name",
      "date": "1991-08-13",
      "time": "13:31",
      "latitude": 12.9716,
      "longitude": 77.5946,
      "timezone": "Asia/Kolkata"
    }
  }' | python3 -m json.tool

{
    "engine_id": "numerology",
    "result": {
        "life_path": { "value": 5, "meaning": "Freedom, change, adventure" },
        "expression": { "value": 1, "meaning": "Leadership, independence, pioneering" },
        "soul_urge": { "value": 5, "meaning": "Freedom, change, adventure" }
    },
    "witness_prompt": "What patterns arise when freedom meets discipline?",
    "consciousness_level": 0,
    "metadata": { "calculation_time_ms": 0, "backend": "native" }
}

✦ Noesis SDK & TUI

Rust SDK (noesis-sdk)

First-party Rust SDK for interacting with the Selemene API. Use it to build your own tools, integrations, or TUI extensions.

use noesis_sdk::{Config, NoesisClient, LocalProfile};

let config = Config::load().unwrap_or_default();
let client = NoesisClient::new(&config)?;
let profile = LocalProfile::load_or_default()?.unwrap();
let output = client.calculate("numerology", profile.to_engine_input()).await?;
println!("{}", MarkdownRenderer::new().render_engine_output(&output));

Features: HTTP client for all 16 engines & 6 workflows, local profile management (~/.noesis/profile.json), macOS Keychain API key storage, Markdown/JSON report rendering, TOML + env config.

Terminal TUI (noesis-tui)

Full interactive terminal interface built with Ratatui. Run engines, browse workflows, manage your profile, and export reports — all from the terminal.

cargo run --bin noesis-tui

Screens: Welcome (with connection status) · Onboarding wizard (8-step profile setup) · Engine picker (16 engines, / to filter) · Workflow picker (6 workflows) · Result display (styled Markdown, scroll, export) · History browser (past readings) · Profile editor (birth data + API key)

Keybinds: j/k navigate · Enter select · / filter · e export MD · J export JSON · r re-run · ? help overlay · Ctrl+Q quit

✦ Roadmap

P0 — SDK Foundation ✅

• noesis-sdk crate — HTTP client, profile, keychain, renderer, config
• 27 tests passing

P1 — Terminal TUI ✅

• noesis-tui crate — Ratatui interactive interface (2,829+ lines)
• All 7 screens + 3 widgets + UX gap analysis fixes (18 issues resolved)

P2 — Desktop Surfaces (planned)

• Raycast extension for quick readings
• macOS menu bar applet
• Tauri wrapper app

P3 — Apple Ecosystem (planned)

• Apple Shortcuts actions
• Apple Watch complications
• On-device caching

✦ The 16 Engines

Each engine is a mirror, not a method. They don't predict; they reflect. The value isn't in the calculation — it's in what you witness when you see the pattern.

Rust Engines (11)

Panchanga Tithi · Nakshatra · Yoga · Karana date, lat/lng	Human Design Type · Centers · Gates · Profile date, time, lat/lng	Gene Keys Shadow · Gift · Siddhi date, time, lat/lng	Vimshottari 120-Year Dasha Periods date, time, lat/lng	Numerology Life Path · Expression date, name
Biorhythm Physical · Emotional · Intellectual date	Vedic Clock TCM Meridians · Doshas current_time	Biofield Vedic Chakra · Birth-Data Analysis date, time, lat/lng	Face Reading Physiognomy Analysis image_data	Nadabrahman Sound Consciousness audio_data
Transits Planetary Transits · Sade Sati date, time, lat/lng

TypeScript Engines (5)

Note: These engines run in a separate ts-engines service. The API attempts to connect to them at startup (with 30s retry logic). If the service is unreachable, these endpoints will be unavailable.

Tarot 78-Card System date, question

I Ching 64 Hexagrams question, method

Enneagram 9 Types · Wings · Tritypes date, name

Sacred Geometry Platonic Solids · Patterns parameters

Sigil Forge Intent Manifestation intent_text

→ View Detailed Engine Documentation

Request Format & Examples

All engines accept the same EngineInput shape:

{
    "birth_data": {
        "name": "string",              // Used by numerology
        "date": "YYYY-MM-DD",          // Required
        "time": "HH:MM",              // Required for HD, gene-keys, vimshottari
        "latitude": 12.9716,           // Decimal degrees
        "longitude": 77.5946,          // Decimal degrees
        "timezone": "Asia/Kolkata"     // IANA timezone
    },
    "precision": "standard"            // "standard" | "high" | "extreme"
}

Try Each Engine

BASE="https://selemene.tryambakam.space/api/v1"

# Numerology — needs name + date
curl -s -X POST $BASE/engines/numerology/calculate \
  -H "X-API-Key: $NOESIS_API_KEY" -H "Content-Type: application/json" \
  -d '{"birth_data":{"name":"Test","date":"1991-08-13","latitude":12.97,"longitude":77.59,"timezone":"Asia/Kolkata"}}'

# Biorhythm — just a birth date
curl -s -X POST $BASE/engines/biorhythm/calculate \
  -H "X-API-Key: $NOESIS_API_KEY" -H "Content-Type: application/json" \
  -d '{"birth_data":{"date":"1991-08-13","latitude":12.97,"longitude":77.59,"timezone":"Asia/Kolkata"}}'

# Human Design — needs exact birth time
curl -s -X POST $BASE/engines/human-design/calculate \
  -H "X-API-Key: $NOESIS_API_KEY" -H "Content-Type: application/json" \
  -d '{"birth_data":{"date":"1991-08-13","time":"13:31","latitude":12.9716,"longitude":77.5946,"timezone":"Asia/Kolkata"}}'

# Vedic Clock — uses current time, no birth data needed
curl -s -X POST $BASE/engines/vedic-clock/calculate \
  -H "X-API-Key: $NOESIS_API_KEY" -H "Content-Type: application/json" \
  -d '{}'

---

✦ The 6 Workflows

Workflows don't pipeline — they synthesize. Not "do this, then this" but "hold these perspectives simultaneously and notice what emerges."

True to the name Noesis (the act of knowing), workflows train direct intellectual apprehension — knowing that is aware of itself knowing.

birth-blueprint — Numerology + Human Design + Gene Keys Your natal imprint. Life path numbers, bodygraph, activation sequences. daily-practice — Panchanga + Vedic Clock + Biorhythm Optimal timing. Cosmic tide aligned with personal rhythm. decision-support — Tarot + I-Ching + HD Authority Multi-perspective guidance. Not "what to do" but "what to notice."

self-inquiry — Gene Keys + Enneagram Shadow work meets personality. Where you contract, where you expand. creative-expression — Sigil Forge + Sacred Geometry Intent made visible. Symbols as seeds, geometry as meditation. full-spectrum — All 16 Engines Complete consciousness portrait. Every lens, every frequency.

_{Workflows referencing TypeScript engines (Tarot, I-Ching, Enneagram, Sacred Geometry, Sigil Forge) require the TS engines server. See Bridge CLI for setup.}

Execute a Workflow

curl -s -X POST $BASE/workflows/birth-blueprint/execute \
  -H "X-API-Key: $NOESIS_API_KEY" -H "Content-Type: application/json" \
  -d '{"birth_data":{"date":"1991-08-13","time":"13:31","latitude":12.9716,"longitude":77.5946,"timezone":"Asia/Kolkata"}}'

---

✦ Consciousness Levels

The system adapts witness prompts based on your relationship with awareness.

Level	State	Prompt Calibration
0	Dormant	"What sensations arise when you feel this pattern?"
1	Glimpsing	"When does this pattern show up in your life?"
2	Practicing	"What might this pattern be protecting?"
3	Integrated	"How do you choose to work with this pattern?"
4-5	Embodied	"What witnesses this pattern arising?"

_{This isn't gamification. It's meeting you where you are.}

---

✦ Authentication

Method	Header	Use Case
API Key	X-API-Key: nk_...	Server-to-server, scripts, CLI
JWT	Authorization: Bearer <token>	User sessions

Rate Limits & Tiers

Tier	Rate Limit	Access
free	60 req/min	Basic engines
premium	1,000 req/min	All engines + batch
enterprise	10,000 req/min	Everything + admin

Seed API Keys:

DATABASE_URL="your-supabase-postgres-url" \
  cargo run --package noesis-auth --features postgres --example seed_api_keys

Creates admin user (admin@tryambakam.com) + 5 API keys. Keys print once.

---

✦ Architecture

graph LR
    Client["📱 Client / TUI / Agent"] --> API["🔀 noesis-api<br>(Axum)"]
    API --> Auth["🔐 noesis-auth<br>(JWT + API Key)"]
    API --> Orch["⚙️ noesis-orchestrator"]
    Orch --> RE["🧮 Rust Engines (11)"]
    Orch --> Bridge["🌉 noesis-bridge"]
    Bridge --> TSE["📦 TS Engines (5)<br>(Bun)"]
    API --> Cache["🔴 noesis-cache<br>(L1 LRU · L2 Redis · L3 Disk)"]
    Auth --> DB[("🗄️ Supabase<br>PostgreSQL")]
    API --> Metrics["📊 Prometheus<br>/metrics"]
    API --> Sentry["🔍 Sentry"]

Loading

Engine families:

• Rust native: Panchanga, Human Design, Gene Keys, Vimshottari, Numerology, Biorhythm, Vedic Clock, Biofield, Face Reading, Nadabrahman, Transits
• TypeScript bridged: Tarot, I-Ching, Enneagram, Sacred Geometry, Sigil Forge

Crate Structure

crates/
  noesis-api/             Axum HTTP server (the binary you deploy)
  noesis-orchestrator/    Multi-engine parallel execution + workflow synthesis
  noesis-auth/            JWT + API key auth (Supabase Postgres)
  noesis-cache/           3-layer cache (L1 memory, L2 Redis, L3 disk)
  noesis-metrics/         Prometheus instrumentation
  noesis-core/            Shared types (EngineInput, EngineOutput, BirthData)
  noesis-vedic-api/       Optional FreeAstrologyAPI client (not on the active Vedic runtime path)
  engine-panchanga/       Vedic calendar calculations
  engine-human-design/    HD bodygraph (64 gates, 9 centers, profile)
  engine-gene-keys/       Shadow-Gift-Siddhi activation sequences
  engine-vimshottari/     120-year nested dasha periods
  engine-numerology/      Pythagorean + Chaldean number systems
  engine-biorhythm/       3 biological cycles (P/E/I)
  engine-vedic-clock/     TCM organ clock + Ayurvedic timing
  engine-biofield/        Vedic birth-data-driven chakra & biofield analysis
  engine-face-reading/    Physiognomy analysis
  engine-nadabrahman/     Sound consciousness engine
  engine-transits/        Planetary transits, aspects & Sade Sati
  noesis-sdk/             Rust SDK — HTTP client, profiles, keychain, renderer
  noesis-tui/             Terminal TUI — Ratatui interactive interface
  noesis-bridge/          Bridge integrations (Claude, OpenAI, LangChain)
  noesis-data/            Data loading and management
  noesis-integration/     Integration tests & cross-engine coordination
  noesis-western-api/     Western astrology API client
  noesis-witness/         Witness prompt generation & consciousness calibration

Runtime Notes

• panchanga, vimshottari, and transits currently execute through the native Rust engines in the live noesis-api runtime.
• noesis-vedic-api remains in the repository for auxiliary/provider integration work, but it is not the active path for the current Vedic runtime.
• Recent hygiene fixes locked reference regressions for:
  • canonical birth-time Panchanga + Vimshottari output (1991-08-13 13:31 Asia/Kolkata)
  • Panchanga karana sequencing for 2026-03-10 Bengaluru
  • Transits natal baseline across three trusted charts, including timezone-correct birth parsing and date-correct Lahiri ayanamsha

Performance

Engine	Time		Engine	Time
Gene Keys	0.012ms		Vimshottari	<1ms
Panchanga	<1ms		Human Design	1.31ms
Numerology	<1ms		API p95	<100ms
Biorhythm	<1ms		Workflow	<200ms

---

✦ Project Health

Category	Status	Score
Tests	████████████████████	86 files
CI/CD	████████████████████	test + deploy + release
Type Safety	████████████████████	Rust strict + Biome
Documentation	████████████████░░░░	API docs, runbooks, portal
Monitoring	████████████████████	Prometheus + Sentry + Grafana

---

✦ Production Stack

Component Technology Compute Railway Admin Frontend Vercel (apps/admin-web) · billing at /billing Payments Dodo Payments — plan catalog, subscriptions, webhooks Database Supabase PostgreSQL Cache Redis (L2) + LRU (L1)

Component Technology Errors Sentry Metrics Prometheus (/metrics) Docs Swagger UI (/api/docs)

All Endpoints

Path	Auth	Purpose
/health/live	✗	Liveness probe
/health/ready	✗	Readiness check
/api/docs	✗	Swagger UI
/metrics	✗	Prometheus metrics
/api/v1/engines	✓	List engines
/api/v1/engines/:id/calculate	✓	Run calculation
/api/v1/engines/:id/info	✓	Engine metadata
/api/v1/workflows	✓	List workflows
/api/v1/workflows/:id/execute	✓	Execute workflow
/api/v1/admin/session	✓	Current admin session envelope
/api/v1/admin/users	✓	List/search users
/api/v1/admin/users/:user_id/state	✓	Lock/unlock account
/api/v1/admin/users/:user_id/tier	✓	Update user tier
/api/v1/admin/users/:user_id/roles	✓	Apply role-derived permissions
/api/v1/admin/api-keys	✓	List/create API keys
/api/v1/admin/api-keys/:key_id	✓	Permanently delete API key
/api/v1/admin/api-keys/:key_id/revoke	✓	Revoke API key
/api/v1/admin/api-keys/:key_id/rotate	✓	Rotate API key
/api/v1/admin/history-sync/*	✓	Drift/device/event sync views
/api/v1/admin/analytics/*	✓	Summary/timeseries/breakdown/top consumers
/api/v1/admin/billing/overview	✓	Subscription counts, MRR estimate, free user count
/api/v1/admin/billing/subscriptions	✓	Paginated subscription list with status filter
/api/v1/admin/billing/subscriptions/:id	✓	Subscription detail + force-cancel
/api/v1/admin/billing/webhook-events	✓	Last 100 processed Dodo webhook events
/api/v1/admin/billing/reconcile/drift	✓	Current subscription drift report
/api/v1/admin/billing/reconcile/run	✓	Trigger reconcile job
/api/v1/admin/billing/plans	✓	Plan catalog (read-only)
/api/v1/admin/usage/summary	✓	Engine usage summary + top consumers

---

✦ Physical Embodiments

Beyond code, Noesis manifests in ritual objects and somatic practices. Explore Somatic Canticles.

• Ritual Kit — essential tools for embodied practice
• Somatic Grimoire — knowledge meets sensation
• Clarity Elixir — aromatic anchors for inquiry
• Sacred Objects — daily practice artifacts

---

✦ Local Development

cargo build --release && cargo run --bin noesis-server   # Build & run
cargo test -- --test-threads=1                           # Run tests
docker-compose up -d                                     # Docker

Environment Setup

Copy .env.example to .env. Required variables:

• RUST_ENV — development or production
• JWT_SECRET — signing key for JWT tokens
• DATABASE_URL — Supabase Postgres connection URL (optional — runs degraded without)

See .env.example for full list.

---

✦ Documentation

API Quickstart	Zero to first call
Terminal TUI	Interactive terminal interface
Rust SDK	Build your own integrations
Engine Onboarding	Add a native Rust engine
Swagger UI	Interactive explorer
Terminal Explorer	CLI exploration
Agent Bridge	Claude, OpenAI, LangChain tool defs
OpenClaw Gateway	Connect OpenClaw agents
Deployment	Production guide
Troubleshooting	Common issues & fixes

OpenClaw Gateway Integration

Selemene Engine supports integration with OpenClaw agents via the OpenClaw Gateway protocol. Generate an invite code to get onboarding instructions:

# 1. Generate an invite code (requires auth)
curl -X POST https://selemene.tryambakam.space/api/v1/onboarding/invite \
  -H "X-API-Key: nk_your_key" \
  -H "Content-Type: application/json" \
  -d '{"expires_hours": 24}'

# Response includes:
# {
#   "invite_code": "selemene_abc123...",
#   "onboarding_url": "/api/v1/onboarding/selemene_abc123.../openclaw.txt"
# }

# 2. Get onboarding instructions
curl https://selemene.tryambakam.space/api/v1/onboarding/selemene_abc123.../openclaw.txt

The onboarding instructions include:

• OpenClaw Gateway adapter configuration
• Gateway URL and authentication tokens
• Connectivity test commands
• List of all 16 engines and 6 workflows

See OpenClaw Integration for detailed setup.

---

✦ Brand Identity

Brand and visual identity assets live under docs/assets/images/ and campaign-ready compositions are maintained in the design pipeline docs.

---

✦ Contributing

We welcome contributions — especially new engines, witness prompt refinements, and bridge integrations.

1. Fork the repo and create a feature branch
2. Follow the Engine Onboarding Guide for new engines
3. Run tests: cargo test -- --test-threads=1
4. Ensure CI passes: cargo clippy --workspace and cargo fmt --all --check
5. Open a PR against main

See the deployment docs for production setup.

---

✦ Agent dispatch

Selemene ships an automated contributor pipeline: any open issue with the agent-ready label is auto-converted into a draft PR implemented by the GitHub Copilot coding agent. Useful for well-scoped tasks where the issue body fully specifies the deliverable.

Trigger: apply the agent-ready label to an open issue.

What happens (in order):

1. agent-dispatch.yml creates branch agent/issue-{N}-{slug} off main, opens a draft PR with the issue spec + checklist, and commits a task file at .agent-tasks/issue-{N}.md.
2. The dispatch workflow posts an @copilot Implement everything in .agent-tasks/issue-{N}.md. comment on the PR (controlled by repo var COPILOT_AUTOKICK, default true).
3. The Copilot coding agent picks up the kickoff, implements per the spec, and deletes .agent-tasks/issue-{N}.md in its final commit to signal done.
4. agent-auto-ready.yml detects the deleted task file (gated on >1 commit + draft + agent/issue-* head) and flips the PR from draft → ready-for-review.
5. On merge, agent-post-merge.yml closes the linked issue and applies the agent-merged label.

Backfill mode — for issues already labeled before the dispatch workflow was added, run Actions → Agent Issue Dispatch → Run workflow (leave input empty for all open agent-ready issues, or pass a comma-separated issue list).

Batch merge — agent-merge-lane.yml supports manual dispatch to merge eligible agent PRs by lane (qa-docs, backend, all) with an optional dry_run.

Gotchas:

• Issue body must fully specify the deliverable + acceptance criteria — the bot reads only .agent-tasks/issue-{N}.md, not the surrounding repo context.
• Idempotent: if the dispatch fires twice on the same issue, the second run skips because an agent/issue-{N}-* PR already exists.
• The auto-ready gate requires >1 commit (scaffold + at least one bot commit) — empty draft PRs stay draft.

---

✦ Acknowledgments

_{This work stands on the shoulders of Maharishi Parashara (Vimshottari Dasha), Ra Uru Hu (Human Design), Richard Rudd (Gene Keys), B.V. Raman (Vedic astrology), and the Swiss Ephemeris Team.}

---

Not Prediction. Reflection. Inquiry. Witness.

Selemene Engine succeeds when you no longer need it.

That's the point.

MIT License
_{Not prediction. Reflection. Inquiry. Witness.}

_{Quickstart · API Docs · Agent Bridge}