PilotFrontend & Console
MCPLLMs

Frontend & Console

Pilot Frontend and Console

Founder workflows, YC intel, cofounder UI, and Telegram miniapp.
PublicSource-ownedMarkdown export

This page is the public frontend map for Pilot. It covers user-facing surfaces and points readers to the implementation paths that own behavior.

Source truth

  • Web application shell and founder workflows: apps/web/README.md and apps/web/src/app/.
  • Telegram Mini App behavior: docs/telegram-miniapp-8.md and apps/telegram-miniapp/README.md.
  • Telegram bot behavior: apps/telegram-bot/README.md.
  • Public workflow routes and capability labels: docs/capabilities.md, docs/pilot-capability-matrix.md, and the shared capability registry.
  • API payloads used by UI surfaces: docs/api.md.

Frontend boundary

Pilot frontend docs may describe available screens, route families, and the state each screen reads. They must not promote prototype or implemented capabilities to production-ready unless the shared registry and evidence-backed evals have already promoted the capability.

Surface map

Diagram1. Ingestion & Context Plane -> Founder or operator -> apps/web -> Telegram bot and mini app -> 2. Evaluation & Policy Plane -> Gateway API -> 4. Tamper-Evident Ledger Plane -> Workspace, task, evidence, and capability state
flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        Founder["Founder or operator"]
        Web["apps/web"]
        Telegram["Telegram bot and mini app"]
    end

    subgraph Evaluation["2. Evaluation & Policy Plane"]
        Gateway["Gateway API"]
    end

    subgraph Ledger["4. Tamper-Evident Ledger Plane"]
        State["Workspace, task, evidence, and capability state"]
    end

    %% Operational Flow Edges
    Founder --> Web
    Founder --> Telegram
    Web --> Gateway
    Telegram --> Gateway
    Gateway --> State
    State --> Web

    %% Premium Styling Rules
    style Gateway fill:#2d3748,stroke:#4a5568,stroke-width:2px,color:#fff
    style State fill:#2f855a,stroke:#276749,stroke-width:2px,color:#fff
Mermaid source
flowchart TD
    subgraph Ingestion["1. Ingestion & Context Plane"]
        Founder["Founder or operator"]
        Web["apps/web"]
        Telegram["Telegram bot and mini app"]
    end

    subgraph Evaluation["2. Evaluation & Policy Plane"]
        Gateway["Gateway API"]
    end

    subgraph Ledger["4. Tamper-Evident Ledger Plane"]
        State["Workspace, task, evidence, and capability state"]
    end

    %% Operational Flow Edges
    Founder --> Web
    Founder --> Telegram
    Web --> Gateway
    Telegram --> Gateway
    Gateway --> State
    State --> Web

    %% Premium Styling Rules
    style Gateway fill:#2d3748,stroke:#4a5568,stroke-width:2px,color:#fff
    style State fill:#2f855a,stroke:#276749,stroke-width:2px,color:#fff

Validation

Run npm run docs:coverage && npm run docs:truth before changing frontend docs. Run the relevant web or Telegram package checks when a UI claim depends on actual route behavior.