UFOBriefing

What it is

A read-only, static website that visualizes UAP-related signals, panel debates, and disclosure leads. It ingests structured data from the Intelligence Briefing Toolkit (IBT) and Tool-RAG repositories to generate JSON APIs consumed by a Next.js frontend. The site emphasizes provenance, showing exactly how raw signals are filtered into daily briefs and wire logs.

Features

• Daily UAP signal briefings with recency-weighted confidence scoring
• Chronological wire ledger of dated, on-topic signals with source deduplication
• Structured panel debate transcripts with persona-specific stance blocks
• Disclosure lead generation connecting entities, events, and sources via graph edges
• Analytical transparency page showing pipeline filtering statistics and source tiers

Quickstart

git clone https://github.com/davidbmar/UFOBriefing.git
cd UFOBriefing
npm install
export IBT_ROOT=~/src/intelligence-briefing-toolkit
export TOOLRAG_ROOT=~/src/tool-RAG
npx tsx scripts/build-daily.ts
npx tsx scripts/build-cases.ts
npx tsx scripts/build-disclosure.ts
npx tsx scripts/build-wire.ts
npm run dev

Architecture

flowchart TD
    subgraph DataSources["External Data Sources"]
        IBT["Intelligence Briefing Toolkit\n(graph.json, signals.json)"]
        RAG["Tool-RAG\n(PANEL_DEBATE artifacts)"]
    end

    subgraph BuildProcess["Build Scripts (tsx)"]
        BuildDaily["build-daily.ts"]
        BuildWire["build-wire.ts"]
        BuildCases["build-cases.ts"]
        BuildDisclosure["build-disclosure.ts"]
        BuildLeads["build-disclosure-leads.ts"]
        BuildStats["build-signals.ts"]
    end

    subgraph StaticAssets["Public API (JSON)"]
        DailyAPI["/api/daily-brief.json"]
        WireAPI["/api/wire.json"]
        CasesAPI["/api/cases/*.json"]
        DisclosureAPI["/api/disclosure.json"]
        LeadsAPI["/api/disclosure-leads.json"]
        StatsAPI["/api/signals-stats.json"]
    end

    subgraph Frontend["Next.js Static Site"]
        Pages["React Pages"]
    end

    subgraph Deploy["AWS Infrastructure"]
        S3["S3 Bucket"]
        CF["CloudFront Distribution"]
    end

    IBT --> BuildDaily
    IBT --> BuildWire
    IBT --> BuildDisclosure
    IBT --> BuildStats
    RAG --> BuildCases
    
    BuildDaily --> DailyAPI
    BuildWire --> WireAPI
    BuildCases --> CasesAPI
    BuildDisclosure --> DisclosureAPI
    DisclosureAPI --> BuildLeads
    BuildLeads --> LeadsAPI
    BuildStats --> StatsAPI

    DailyAPI --> Pages
    WireAPI --> Pages
    CasesAPI --> Pages
    DisclosureAPI --> Pages
    LeadsAPI --> Pages
    StatsAPI --> Pages

    Pages --> S3
    S3 --> CF

How it's built

TypeScript/Next.js static site. Build scripts (tsx) read IBT graph data and Tool-RAG artifacts to generate static JSON files in public/api/. The site is deployed to AWS S3 behind CloudFront. It uses a three-repo architecture: IBT for data collection, Tool-RAG for debate analysis, and UFOBriefing for presentation.

How it runs

sequenceDiagram
    participant Dev as Developer
    participant Build as Build Scripts (tsx)
    participant IBT as IBT Data Store
    participant RAG as Tool-RAG Artifacts
    participant FS as Public API (JSON)
    participant Next as Next.js Builder
    participant S3 as AWS S3

    Dev->>IBT: Read signals.json & graph.json
    Dev->>RAG: Read PANEL_DEBATE files
    
    Build->>IBT: Fetch latest signals
    Build->>Build: Filter by recency & topic
    Build->>FS: Write daily-brief.json
    
    Build->>IBT: Fetch graph edges
    Build->>FS: Write disclosure.json
    Build->>FS: Write disclosure-leads.json
    
    Build->>RAG: Parse debate transcripts
    Build->>FS: Write cases/*.json
    
    Build->>IBT: Calculate funnel stats
    Build->>FS: Write signals-stats.json
    
    Dev->>Next: Run npm run static
    Next->>FS: Read generated JSON APIs
    Next->>Next: Pre-render React pages
    Next->>S3: Sync ./out/ directory

How to apply & reuse

Clone the repo, ensure IBT and Tool-RAG repos are available locally, set environment variables for their paths, run build scripts to generate API data, then build and deploy the Next.js static export.

At a glance