Vecoris System Design & Portals

title: "Vecoris System Design & Portals" summary: "An overview of system layout boundaries, operational portals, and permission scopes defining the trust infrastructure." category: "Platform" difficulty: "Intermediate" author: "Kalyan Chowdary" reviewer: "Vecoris Fronted Lead" version: "1.0" reviewStatus: "Current" lastReviewed: "2026-07-18" definitions:

• term: "Asset Identity" definition: "A persistent digital record tracking the spatial boundaries, chronological title history, and current compliance score of a physical asset."
• term: "Chain of Custody" definition: "Cryptographic audit history logging how and when evidence is added to an asset."
• term: "Connector" definition: "Ingest adapter querying authoritative municipal or private registries."

The Vecoris Platform provides a structured runtime interface to inspect, verify, and verify physical world assets. Rather than operating as a single monolithic dashboard, it divides operational capabilities across specific role-based portals and client libraries.

1. Role-Based User Portals

The frontend application (vecoris-web) maps user interfaces to three distinct operational roles to ensure data hygiene and audit trail integrity:

• Investigator Portal: Field agents and surveyors use this portal to register new assets, submit on-site structural photos, and attach land survey documents. All inputs are tagged with GPS metadata and user identity signatures.
• Reviewer Portal: Compliance officers and legal auditors review incoming cases. They cross-reference submitted field evidence with authoritative municipal records retrieved by crawl connectors, assigning compliance flags or approving titles.
• Admin Portal: System operators manage access controls, monitor RERA crawl pipeline status, adjust rule criteria weights, and deploy custom validation connectors.

2. Dynamic Integration Client (SDK)

The integration boundary is defined by @vecoris/sdk. Any secondary service, crawler trigger, or backend cron node queries the platform via standard API calls:

• Type-Safe Payloads: Every query response is parsed using Zod to ensure runtime objects match compile-time interfaces, shielding the client from database-level refactoring side-effects.
• Role-Based Access Control: API queries are verified against JSON Web Tokens (JWT) signed by the central authentication service, enforcing permission scopes down to the endpoint level.

By enforcing these portal divisions and SDK boundaries, the system preserves strict operational isolation and audit validation compliance.