---

What is disha6.6?

disha6.6 is a Constitutional Evidence Operating System: an evidence-first intelligence platform for governed public-source research, OSINT, cyber-intelligence posture, geospatial analysis, policy monitoring, source watching, and accountable AI-assisted decision support.

The operating chain is deliberately simple:

source -> observation -> policy -> evidence -> review -> decision

Most intelligence systems focus on producing an answer. disha6.6 focuses on producing an answer that can be inspected, challenged, traced to sources, policy-checked, and reviewed by a human.

A model can assist. A data feed can assist. An analyst can assist. None of them become invisible authority.

What changed in this branding pass

The public product identity is now:

disha6.6

The public deployment remains:

https://disha6.6.thenitishkr.in

The Render origin behind Cloudflare remains:

https://disha-v6-web.onrender.com

The Python intelligence service remains:

https://disha-v6-brain.onrender.com

Internal folder names such as disha/, environment variable names such as DISHA_JWT_SECRET, and existing script paths are retained because they are runtime contracts. A blind rename of those symbols would break imports, CI, Render, workflows, and existing secrets. They can be migrated later through a dedicated compatibility plan.

What disha6.6 is built to solve

Teams already have search engines, LLMs, dashboards, OSINT directories, cyber feeds, and data vendors. The harder problem is governance around intelligence:

• Where did this claim come from?
• Is the source public, authorized, licensed, and current?
• What changed since the last observation?
• Which part came from a model versus a source?
• What did policy allow, restrict, or deny?
• Can another reviewer reconstruct the work?
• Can the evidence trail prove it was not silently rewritten?

That is the product boundary of disha6.6.

Current production posture

Architecture

Browser / API / Workbench
  -> typed signal
  -> source routing
  -> governed adapters
  -> normalized observation
  -> policy gate
  -> evidence ledger
  -> human review
  -> decision record

Core runtime ownership:

• TypeScript / Next.js owns product surfaces, API routes, sessions, policy decisions, evidence presentation, OSINT control plane, and mission flow.
• PostgreSQL / PostGIS owns durable structured data and geospatial persistence paths where configured.
• Redis / Key Value supports runtime workflow infrastructure where configured.
• Python owns bounded intelligence/research services such as the Brain service.
• Extensions cannot bypass the policy gate or evidence ledger.

Product surfaces

Important API entry points

GET  /api/v1/health
POST /api/v1/mission
POST /api/v1/agentic/mission
POST /api/v1/policy/evaluate
GET  /api/v1/evidence/{missionId}
POST /api/v1/evidence/export
GET  /api/v1/osint/catalog
GET  /api/v1/osint/sources
GET  /api/v1/osint/search?q=example.org
GET  /api/v1/osint/service-connectors
GET  /api/v1/osint/restricted-sources
GET  /api/v1/production/readiness

Safe OSINT rule

disha6.6 is passive/public by default. Catalog presence does not imply execution.

Allowed production patterns include public records, official feeds, public DNS and registration metadata, public certificate data, public web archives, public news discovery, defensive vulnerability information, and other explicitly admitted sources.

The default runtime does not perform credential harvesting, authentication bypass, exploit delivery, private-account access, leaked-data ingestion, or automated identity enumeration.

Quick start

Requirements:

• Node.js 22.x
• npm
• PostgreSQL for durable production data
• optional Redis / Key Value
• optional Python runtime for governed research extensions

Run locally:

npm install --prefix web
npm --prefix web run dev

Open:

http://127.0.0.1:3000/login
http://127.0.0.1:3000/dashboard
http://127.0.0.1:3000/workbench
http://127.0.0.1:3000/intelligence

Verify:

npm --prefix web run type-check:full
npm --prefix web test
npm --prefix web run build

Repository map

Repository rename note

The code and docs now use disha6.6 as the public product identity. The actual GitHub repository settings must still be renamed manually in GitHub if the browser URL should become:

https://github.com/Tashima-Tarsh/disha6.6

The connector available here can update repository files, but it does not expose a repository-settings mutation for renaming the GitHub repository object.