Atlas AI financial assistant
A Telegram-native financial research assistant with durable memory, guarded document intake and evidence-bound answers.
Problem
A financial assistant that watches markets and accepts documents needs to distinguish evidence from inference, limit unsafe input and stay silent when an event is not material.
How I solved it
- 01
Places deterministic source-reliability and materiality gates before model synthesis, so research answers are bounded by evidence rather than generated from every available signal.
- 02
Uses durable D1 and R2-backed paths for Telegram onboarding, research, documents and scheduled briefings, with guarded media download before content enters the system.
- 03
Bounds Telegram delivery with idempotency, retries and at-most-once outbound-message handling, with a Groq text-only continuity fallback that refuses current financial information and scheduled work.
My role / what I owned
Hackathon builder and repository author
- Built Telegram onboarding, research, document and scheduled-briefing paths for the submission.
- Added deterministic source-reliability and materiality gates before AI synthesis.
- Added idempotent Telegram delivery, guarded media downloads and at-most-once outbound-message handling.
How it was built
- Team
- In development for the Atlas AI Financial Assistant Hackathon. The private repository does not document a separate human collaborator split.
- Tools
- TypeScript
- Telegram
- Cloudflare D1
- Cloudflare R2
- OpenAI Responses API
- Groq continuity fallback
- SEC EDGAR
- Use of AI
- OpenAI handles cited research, synthesis and transcription after deterministic trust, materiality and input boundaries. Groq is a limited text-only continuity fallback and never processes attachments, scheduled work or current financial information.
Source and current state
- The private 9-10 August release history includes the D1 migration runner, safe scheduled timestamp handling and the Groq continuity fallback.
- Twenty-four current test files cover finance, security, migrations, jobs, rendered output and Telegram transport.
- The public hosted demo returned HTTP 200 on 29 August 2026; the private source documents the trust boundaries, durable state and guarded outbound-message paths.
- Status
- Private hackathon submission. The public hosted demo is reachable, and the public Telegram profile resolves; neither establishes production financial-service operation or current bot availability.
- What it shows
- The audited repository demonstrates the Telegram, finance, persistence and verification architecture delivered for the submission.