Pit Wall

2026 Formula 1 standings, teams, the calendar and results, plus a Claude strategist on the radio. Ask a question and Claude answers from the season, and searches the web when the board is not enough.

Questions answered by Claude

Loading the garage board…

Ask the pit wall

Claude answers from the stored season, and can search the web and read pages when the board does not have it. Chat is invite-only for now, with thirty questions a day.

The board reads a stored copy, refreshed on Saturday evening, Sunday afternoon and evening, and Monday morning. It does not call the race feed itself. Questions go to Claude, not the race feed.

Source Jolpica
The 2026 standings, the 23-race calendar, grand prix results, and sprint results. No key.
→
Sat, Sun and Mon Ingest
A scheduled function pages the results, keeps the top 10, and writes one transaction. A failed fetch writes nothing. When qualifying or a race is new, Claude writes a short recap from those results.
→
Five notes Database
- Drivers
- Teams
- Schedule
- Results
- Updated time
→
When you open it This page
The files sit on Amplify. The board then asks GET /season and draws the copy.

When you ask the pit wall

You Sign in
Google sign-in through Amazon Cognito. The page keeps a short-lived token and sends it with each question.
→
Checks Ask function
Verifies the token and counts the question against a limit of thirty a day. A question that fails is handed back.
→
Context Season + web
The stored season goes with every question, plus the official results page or recent headlines when the question is about a result or the news. Claude can also search the web and open pages itself when that is not enough.
→
Answer Claude
Claude Sonnet 5.5 answers from that context. It remembers your last few exchanges in the chat, and AgentCore Memory keeps your name, favorite driver and a summary of past chats between visits.

The AWS resources

Everything runs in one AWS region. Solid arrows are the live path, including AgentCore Memory, which remembers each signed-in fan. The dashed box is the old AgentCore harness setup: it still exists, but nothing calls it any more.

Lambda
Data and keys
Outside AWS
Idle

Each Lambda has its own IAM role and writes to CloudWatch Logs.

What the board is drawing

Updated time, full width

Next round, or Last round, with the start time in your time zone. Rounds are marked Ran once their results are in, or Results pending until then.

Drivers
points, wins, +N this round

Teams
a color chip and the same counts

Latest race, open

Grand Prix slip, top 10

Sprint slip, only on a sprint weekend Sprint

Older rounds stay closed on one line each.

The rules on the wall

2026 only. One season, no switcher.
Top 10 finishers for the grand prix and for the sprint.
The stamp is the database write time, in UTC. That is the proof the latest refresh ran.
Points on the board are the stored totals. The +N line is this round’s grand prix plus sprint.
The board is public. Anyone can sign in with Google, but chat needs approval while this is a proof of concept: a request emails the site owner, who approves or denies it in an admin panel. Approved emails are saved in a list.
Claude answers from the stored season first. If the board does not have a fact, it should say so instead of guessing.
Recaps are written by Claude from the stored results only: one for each qualifying and one for each race, sprints included. Practice is not covered.
Answers can be wrong. Check the stamp for how fresh the standings are.
Pit Wall remembers what you tell it, such as your name and favorite driver, tied to your Google sign-in. It does not share one person's memory with another.