Vecoris Core Technology Integration

title: "Vecoris Core Technology Integration" summary: "An engineering review of the Vecoris multi-package repository architecture, REST api bindings, and Prisma database schema layouts." category: "Technology" difficulty: "Advanced" author: "Kalyan Chowdary" reviewer: "Vecoris Platform Team" version: "1.0" reviewStatus: "Current" lastReviewed: "2026-07-18" definitions:

• term: "Trust Graph" definition: "A unified, relational validation structure representing spatial audits, title records, and documents."
• term: "Evidence" definition: "Validated inspections, deeds, and logs captured through authenticated connector endpoints."
• term: "Verification" definition: "Programmatic and human execution of verification rules to match records against ground truth."
• term: "Connector" definition: "Ingest adapter querying authoritative municipal or private registries."

The Vecoris platform is built using a decoupled, multi-repository architecture that enforces strict separation of concerns, unidirectional data flow, and type-safe API boundaries. This documents the primary software components, packages, and database layers that comprise the active system.

1. Repository Architecture

The platform partitions codebase responsibilities across six dedicated packages and workspaces to ensure modularity and maintainability:

1. vecoris-web: Next.js App Router workspace housing the operational dashboards (Investigator, Reviewer, and Admin portals). It serves as the primary user interface canvas for operators managing property titles and compliance disputes.
2. vecoris-platform: The backend business engine executing coordinate evaluations, RERA title checks, and PDF report compilation. It exposes a modular server built on Node.js and TypeScript.
3. vecoris-connectors: Ingestion layer handling land registries, civil courts, and municipal databases. It normalizes incoming external data formats into standard internal structures.
4. vecoris-sdk: Generated TypeScript bindings containing programmatic API clients, validators, and Zod data transfer objects. All communications between vecoris-web and vecoris-platform are typed by this client.
5. vecoris-design: Styling tokens, CSS variables, and SVGs distributing consistent visual branding across the frontend portals.
6. vecoris-docs: Architectural records and ADRs tracking key design decisions.

2. Unidirectional Data Dependency Flow

To prevent spaghetti architectures and cyclic compilation failures, Vecoris enforces a strict unidirectional dependency layout:

[ vecoris-web ]  ───>  [ vecoris-sdk ]  ───>  [ vecoris-platform ]  ───>  [ Prisma/SQLite Database ]

Portals running inside vecoris-web never import database models directly or execute raw SQL queries. Instead, all interaction with the data layer goes through the SDK API client, which executes validated HTTP/REST requests against the vecoris-platform server.

3. Database Layer & Schema Management

The storage engine utilizes SQLite for local development and PostgreSQL for production systems, managed via Prisma ORM. The database structure is mapped in @vecoris/database and holds tables tracking:

• Assets: Tracking spatial GIS coordinates, database identifiers, and overall compliance indexes.
• Evidence Files: Storing references to documents parsed by crawler connectors, alongside computed evidence DNA hashes.
• Snapshots: Sealed, chronologically indexed records representing the validated state of a property at a specific timestamp.
• Cases: Internal workflows tracking active boundary disputes or title audits assigned to reviewers.

By executing programmatic checks on build time and compiling OpenAPI specs natively, the SDK guarantees contract validation before any deploy is accepted.