01
Scouts look around
Small research scripts read approved news feeds, papers, and official pages. They collect clues, not passwords.
COLLECT SYSTEM MAP · KID-FRIENDLY EDITION
See how this little AI newsroom works down below.
Imagine a tiny newsroom, a careful librarian, and a fast printing press working together. This page explains the journey in plain language—without showing any private keys or secret settings.
AINEWSROOM
SOURCESCHECKSPAGESTHE BIG JOURNEY
From “what happened?” to “here is what matters.”
Every daily report takes the same careful route, like a package moving through labeled stations.
02
A writer finds the thread
The report writer turns the clues into a short story, keeping links beside the claims so readers can check them.
EXPLAIN03
A checker plays referee
Validation looks for missing dates, missing sources, broken placeholders, provider errors, and duplicate report days.
VERIFY04
The shelves get a new page
A build script turns Markdown into fast HTML pages for the latest report, archive, search, and each dated report.
PUBLISHTHE MACHINE ROOM
Six friendly parts, one calm dashboard.
These are the jobs—not secret ingredients—that make the site tick.
The daily clock
A scheduled workflow starts the research run around the Hong Kong morning target.
The source map
A configuration list tells the scouts which official, research, and discovery sources to watch.
The writing prompt
A plain-text recipe gives the writer its tone, sections, evidence rules, and continuity clues.
The safety lab
Tests and report checks catch mistakes before a new page is allowed onto the public shelves.
The page builder
One static build makes the homepage, report pages, archive cards, and searchable index from saved Markdown.
The browser window
Your browser downloads HTML, CSS, and JavaScript. There is no database server waiting behind each click.
THE LOCKED DRAWER
What stays private?
The architecture guide explains the shape of the machine, not the contents of its locked drawer.
🔒
Secret values
Private provider credentials live in the automation platform’s secret storage.
🚫
No surprise overwrite
If a date already has a report, the generator stops instead of erasing it.
🧯
Safe failure
If research or writing fails, yesterday’s published pages are left alone.
TINY GLOSSARY
Big words, small explanations.
ZOOM ALL THE WAY IN
A report’s day, step by step.
The simple four-step journey contains smaller jobs. Here is the full relay race.
- 01Choose the Hong Kong date
The clock is converted into the report’s calendar before any file gets its name.
- 02Open the research window
Recent items are welcome; stale items are filtered away.
- 03Read the public source map
The scouts learn which official, research, and discovery shelves to visit.
- 04Normalize the clues
Different feed formats become one tidy shape: title, link, time, source, summary, and topics.
- 05Cluster duplicate stories
Five articles about one launch become one evidence bundle instead of five pretend events.
- 06Add continuity
Recent reports help separate a true update from yesterday’s repeated headline.
- 07Draft, continue, or repair
The writer creates the briefing. Incomplete or invalid work is edited and checked again.
- 08Save, build, and test
A protected Markdown file becomes HTML pages, a search record, and a deployable site artifact.
THE DATA CHANGES CLOTHES
One story, five useful shapes.
Each station repacks the same evidence for the next job.
📡Feed itemA title, link, time, and source.
→🧺Story clusterMatching clues bundled together.
→🗂️Research packRanked evidence and continuity notes.
→📝MarkdownThe checked human-readable report.
→🖥️HTML + indexFast pages and browser search data.
TWO DIFFERENT ROOMS
Build-time work versus browser-time work.
🔧 The workshop
Research, writing, repair, validation, Markdown saving, page building, tests, and packaging happen here.
- Can use private automation secrets
- Produces public static files
- Stops safely when a required check fails
📖 The reading room
Your browser receives ready-made files and handles small optional interactions locally.
- Shows HTML styled by CSS
- Searches a small downloaded index
- Never receives private provider credentials
WHEN THINGS GO WRONG
The safety net has several knots.
A failure should leave the last good public site standing.
A source is offline
Other usable sources can continue. No response is treated as missing evidence, not permission to invent.
Writing times out
Retries stay within limits, then a conservative evidence-only edition can preserve the day.
The draft has mistakes
The exact problems are sent back for editing. The edited draft must pass validation again.
Build or tests fail
No successful site artifact is published, so visitors keep seeing the previous good version.
A WORKED EXAMPLE
Suppose a lab announces a school-helper robot.
The official announcement, a technical paper, and a discovery article enter through three doors. Clustering recognizes one event. The official page and paper become strong evidence; the discovery article becomes context. The writer explains what is demonstrated, labels what is only claimed, and avoids inventing a price. Validation checks the links and required sections. One careful story then appears in Markdown, HTML, the archive, and search.
Three doors in → one verified story out.YOUR NEXT STOP
Now you know the backstage trick.
Read a real briefing, explore the archive, or search the signal.