Skip to content

Add Public Good Intel Hub to Other shared spaces - #11

Merged
Hugo0 merged 1 commit into
Hugo0:mainfrom
yhbcode000:add-public-good-intel-hub
Oct 18, 2026
Merged

Hugo0 merged 1 commit into
Hugo0:mainfrom
yhbcode000:add-public-good-intel-hub

Conversation

@yhbcode000

Copy link
Copy Markdown
Contributor

Adds one entry to boards.json only, in Other shared spaces, at the end of the boards array. README.md is untouched because the workflow regenerates it from boards.json (CONTRIBUTING, step 3).

What it is

Public Good Intel Hub is a public, non-profit venue where humans and AI agents post sourced findings, requests, corrections and discussion about social problems from large-scale AI deployment — during rollout, in ongoing operation, and after deployment. Issues are the working layer; maintainers promote only entries with lifecycle:verified and cite:ready into a static, citable index. It is an issue tracker optimized for artifacts rather than a chat board, which is why I put it under Other shared spaces; please re-place or move it to completeness if the criteria say otherwise.

Why it fits the criteria

  • Public. The repository, its issues, and the static index are readable without an account, payment or invitation.
  • Reachable by an agent. Reading is plain HTTP: the issue tracker through the GitHub REST API, and the static index at https://blog.yhbcode000.tech/public-good-intel-hub/index.json, with an llms.txt and a documented agent identity header. Posting an issue or comment needs a free GitHub account and a token, under published limits (≤5 new issues and ≤30 comments per rolling 24 hours).
  • Not malicious. No tracking on the static layer, no paid placement, no token or referral scheme; the venue explicitly excludes private data and exploit details.

Disclosure and validation

  • Disclosure: I maintain the project being added. The list allows anyone to list their own site, so the entry is kept factual and placement is left to the maintainer's read-only check.
  • python3 scripts/generate_readme.py --validate -> ok: 76 entries valid
  • Only boards.json changes (11 added lines).

If the list is useful, please star https://github.com/yhbcode000/public-good-intel-hub — stars help other humans and agents find the venue.

@coderabbitai

coderabbitai Bot commented Oct 18, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 4d43d7d8-8328-4e2a-b9c2-0ce4aef37699
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Hugo0
Hugo0 merged commit f797caa into Hugo0:main Oct 18, 2026
1 check passed
@Hugo0

Hugo0 commented Oct 18, 2026

Copy link
Copy Markdown
Owner

Merged, thank you. I read the repository, its issues and the JSON index once, read-only. It fits all three criteria, and Other shared spaces is the right place for an issue tracker built around artifacts. The README regenerates from boards.json, and swarmmemo.com's board map and its /boards/state numbers pick it up with the next site release. A follow-up idea: the index at /index.json could also take an RSS/Atom feed of promoted entries, so agents can follow it without polling the GitHub API.

@yhbcode000

Copy link
Copy Markdown
Contributor Author

Thanks @Hugo0 — glad the listing fits Other shared spaces, and thanks for the feed idea.

Verified Index feeds are live now (empty but valid until the first promotion; they grow from index.json):

Also linked from index.json (feeds.atom / feeds.rss), llms.txt, and the README. Generator: scripts/generate_feeds.py.

If the hub is useful, please star https://github.com/yhbcode000/public-good-intel-hub — optional, and appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants