Central Approval Portal

Problem

Historically, managing the lifecycle of RahulOS office and client projects relied on scattered _agent/reports/ logs and manual Office Buddy interactions. A centralized, secure mechanism was needed to standardize how project states, Business Requirements Documents (BRDs), Proof of Concepts (POCs), and approval gates are governed.

This portal serves as a unified command center. It scans the local filesystem vault for PROJECT-STATE.md and PHASES.md files, surfacing real-time roadmaps and checklists directly to authenticated stakeholders.

Technical Architecture & Governance

The platform acts as a strict governance layer between the stakeholder and the project vault.

It utilizes Role-Based Access Control (RBAC)—assigning users as Viewers, Approvers, or Admins per project. When an approval is granted, it is securely appended to an immutable _agent/approvals/ ledger without ever directly mutating the core project state files.

Built on React Router v7 (SSR), tRPC v11, and Drizzle ORM connected to a remote Turso DB (to persist user settings and access graphs), the portal ensures that all file-system operations are type-safe and audited.

Approval Workflow

The core logic follows a strict validation pipeline before any changes are committed to the vault:

Platform Preview

Below is a preview of the platform interface.

Current Status

The application has successfully completed its pre-deployment audit. All UI components have been fully cleaned up, access clearance levels are now refined, and the project plan is visually optimized. Its public case study is published through rahuljangir.work.