TickBase News

Overview

TickBase News is the public website channel of a separate event-processing system behind the TickBase ecosystem. Although it shares the TickBase domain, it is implemented by the independent xauusd-trading-monitor project rather than the main TickBase market data platform.

This is a self-directed product that I planned, designed, implemented, deployed, and maintain. The system collects public market-moving information, processes it through a pipeline, produces normalized events, and routes those events to different output channels. news.thetickbase.com is one public-safe channel in that routing layer, not the only product surface.

The site is intentionally informational. It tracks severity, confirmation state, tags, public summaries, and source attribution for XAUUSD-related macro, policy, energy, and geopolitical risk events, without providing trading advice or order recommendations.

Product Architecture

• Pipeline-first architecture - The system separates collection, normalization, classification, routing, private alerting, public publishing, and public website delivery into independent services.
• Collector layer - Dedicated collectors ingest public information streams and write raw records into PostgreSQL as the system of record.
• Normalizer and classifier - normalizer-classifier cleans text, detects language, performs deterministic filtering, generates summaries, extracts structured event fields, and writes normalized events and claims.
• Event routing - event-router decides which channels should receive each event and records auditable route decisions. It answers what should be sent, where it should go, and why; delivery workers only handle how to send it.
• Multi-channel delivery - The same processed event can be routed to private alerts, public Telegram channel publishing, future social publishing, or the public website outbox.
• Public website boundary - public-syncer pushes approved public-safe payloads from the private HomeLab system to a VPS public-api over outbound HTTPS. The public API stores only sanitized event data in a separate public database.
• Public frontend - public-web is a React Router v7 + TanStack Query + Tailwind / DaisyUI frontend deployed on Cloudflare Pages at news.thetickbase.com.
• Data safety boundary - The public stack does not read the HomeLab database and does not store raw collector metadata, prompts, AI raw responses, private notification settings, internal URLs, credentials, or delivery debug data.

Key Features

• Public event radar - Browse a public-safe feed of high-value events related to XAUUSD macro, policy, energy, and geopolitical risk.
• Severity and confirmation filters - Filter events by impact level and confirmation state instead of treating every item as equally reliable.
• Localized public copy - Public event payloads support language-specific titles and summaries with fallback behavior.
• Raw feed and event detail routes - Public pages expose event and raw-feed views through a sanitized public API contract.
• Auditable routing - Route decisions are recorded before delivery, keeping channel behavior explainable and debuggable.
• Strict public/private separation - The public website is a downstream channel with a narrow payload contract, not a public window into the internal monitoring system.