docs: Rebuild documentation as enterprise-grade TLAS platform

- Migrate from custom HTTP server to VitePress framework
- Rename project to Tokenized License Approval System (TLAS)
- Add comprehensive documentation for all stakeholders:
  - Business: Executive summary, value proposition, governance
  - Operations: Infrastructure, installation, monitoring, backup
  - Departments: User guide, workflows, verification, issuance
  - Developers: API reference, authentication, webhooks, SDKs
  - Compliance: OWASP, DPDP Act, IT Act, audit framework
- Add modern theme with dark mode and full-text search
- Update Dockerfile for VitePress build process

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Mahi
2026-02-10 00:05:20 -04:00
parent 4a5bf16827
commit 435889ee79
65 changed files with 6324 additions and 8342 deletions

View File

@@ -0,0 +1,104 @@
# Platform Overview
The Tokenized License Approval System (TLAS) is an enterprise platform that transforms government licensing operations through blockchain-based credential issuance and configurable workflow automation.
## Context
Government licensing processes across India handle millions of applications annually. These processes involve multiple stakeholders, complex approval hierarchies, and strict compliance requirements. Traditional systems face persistent challenges that impact both operational efficiency and citizen trust.
TLAS addresses these challenges through a purpose-built platform that combines workflow automation with cryptographic verification.
## Platform Objectives
| Objective | Measurement |
|-----------|-------------|
| Eliminate document fraud | Zero forged licenses in circulation |
| Reduce processing time | 60% reduction in average approval duration |
| Ensure complete traceability | 100% audit coverage for all transactions |
| Enable citizen self-service | 80% of status inquiries handled without staff |
| Support multi-department deployment | Single platform serving 15+ departments |
## Core Capabilities
### Tokenized License Certificates
Every license issued through TLAS is minted as a Non-Fungible Token (NFT) on a private Hyperledger Besu blockchain. This provides:
- **Cryptographic authenticity**: Certificates are digitally signed and verifiable
- **Tamper evidence**: Any modification attempt is detectable
- **Instant verification**: QR code scanning validates certificate authenticity
- **Permanent record**: Blockchain maintains immutable issuance history
### Configurable Workflow Engine
Departments define their approval processes through a visual workflow builder:
- Sequential and parallel approval stages
- Conditional routing based on application attributes
- Automated document validation rules
- SLA tracking with escalation triggers
- Role-based task assignment
### Unified Operations Dashboard
Administrators and department heads access real-time visibility into:
- Application volumes and processing rates
- Stage-wise bottleneck identification
- SLA compliance metrics
- Staff workload distribution
- Revenue and fee collection status
## Deployment Model
TLAS operates as a multi-tenant platform with department-level isolation:
```
┌─────────────────────────────────┐
│ TLAS Platform │
├─────────────────────────────────┤
┌───────────┼───────────┬───────────┐ │
│ │ │ │ │
┌────▼────┐ ┌────▼────┐ ┌────▼────┐ ┌────▼────┐ │
│ Dept A │ │ Dept B │ │ Dept C │ │ Dept N │ │
│ │ │ │ │ │ │ │ │
│Workflows│ │Workflows│ │Workflows│ │Workflows│ │
│Users │ │Users │ │Users │ │Users │ │
│Licenses │ │Licenses │ │Licenses │ │Licenses │ │
└─────────┘ └─────────┘ └─────────┘ └─────────┘ │
│ │
│ Shared Infrastructure │
│ - Blockchain Network │
│ - Authentication Service │
│ - Notification Gateway │
│ - Analytics Engine │
└─────────────────────────────────┘
```
## Integration Points
TLAS integrates with government and third-party services:
| Integration | Purpose | Protocol |
|-------------|---------|----------|
| DigiLocker | Citizen identity verification, document retrieval | OAuth 2.0 |
| Payment Gateway | License fee collection | REST API |
| SMS Gateway | Application status notifications | HTTP |
| Email Service | Formal communications and certificates | SMTP |
| Legacy Systems | Data migration, reference data sync | Batch/API |
## User Roles
| Role | Responsibilities |
|------|------------------|
| **Applicant** | Submit applications, upload documents, track status, download certificates |
| **Department Officer** | Review applications, verify documents, approve/reject/return |
| **Department Admin** | Configure workflows, manage staff, view department analytics |
| **System Administrator** | Manage departments, monitor platform health, handle escalations |
## Navigation
- [Problem Statement](/overview/problem) - Challenges addressed by TLAS
- [Solution Architecture](/overview/solution) - Technical design and components
- [Key Capabilities](/overview/capabilities) - Feature deep-dive
- [Technology Stack](/overview/technology) - Implementation technologies