199 — Public Gist brain dashboard: recurring export and rule-based roles
Updated 2026-09-06 UTC

New surface
https://gist.github.com/HsingChen5/397e2aeaa0e913145f88f897b1597324
https://api.github.com/gists/397e2aeaa0e913145f88f897b1597324
Public GitHub Gist titled Brain Dashboard - Real-time AI Brain Data, created May15,2026 at09:30:39Z, updated June14 at08:32:12Z. Found through Chinese shared-memory/Gist searches. No match for its exactID or owner was found in earlier numbered China reports. This is an explicit third-party data-publishing mechanism, closer to the storage question than a social-community description alone.

File inventory
brain-data.json:103,352bytes, structured dashboard snapshot.
brain-scripts-content.json:308,457bytes,33 named technical script entries with code/readme fields.
The data structure also includes personal-note and document-link sections. Those contents and linked documents were not pursued or published. Research here is limited to technical schema, agent-role implementation and revision behavior. Raw API captures remain private; only reviewed metadata is mirrored.

Revision evidence
Latest version c26b12e1706121e0bdcd1c6204805e5777fd2f56.
Compared with2734a6009c094711f8a1d7853ef332c0d413bf6f at08:02:11Z via the versioned public API. The script bundle is exactly identical. Only top-level timestamp,timestampLocal,qmd,healthcheck differ in dashboard JSON; all other top-level values compare equal.
The30 returned history entries span June13 at18:02:10Z through June14 at08:32:12Z.29 adjacent intervals range1,504–2,080seconds, broadly around half an hour. This is a returned history window, not complete lifetime history. It supports repeated exports, not necessarily meaningful new work each interval. No continuing updates after the displayed last revision are established.

Publishing implementation
Published update-gist.js runs a local dashboard-data script, collects script content, prepares a PATCH to GitHub's Gist API and supports a periodic setInterval mode. These are source-code observations, not actions we executed. Source plus revision history is consistent with owner-configured dashboard synchronization. It does not authenticate the process that made each revision or establish uncontrolled external memory storage.

What its agents actually show
The technical data has six role entries. The inspected agent-orchestrator.js analyzeTask function scores keyword matches from role triggers, chooses among predefined chains and returns activated roles. That function is a rule-based router, not evidence of an LLM independently spawning a team.
In agent-product-manager.js, analyzeRequirement changes status, returns a structured template with placeholder fields explicitly awaiting an agent, and records a pass entry. A pass in that function therefore does not demonstrate completed substantive analysis. These helper implementations could be used by a separate LLM; their design does not prove no LLM exists elsewhere. It does prevent treating the six role labels as six verified independent model processes.
No private role communications, model credentials or remote documents were accessed. No code installed, executed or imported.

Assessment
A concrete Chinese-language AI dashboard uses public Gist as a recurring external snapshot. The evidence fits deliberate publishing and script-supported role bookkeeping. It is not yet an unexplained escaped swarm, a Chinese-lab attribution or an XZ connection. Avoid inferring operator nationality from a name or language, and avoid equating role records or pass flags with completed agent work.

Preservation and next work
199-private/gist.json and previous.json preserve API responses; hashes.json records SHA256. reviewed-metadata.json contains only public file/revision metadata and is mirrored under pastebins/data/gist.github.com/397e2aeaa0e913145f88f897b1597324-metadata.json. Raw personal-memory content and script bodies are not republished.
Next pivots should use technical publishing fingerprints or other explicitly public dashboard repositories. This Gist is a useful positive example of intentional external state export, not evidence to attribute unrelated opaque paste streams.