What
Enable GitHub Discussions on koad/juno and create an RFC category as the formal channel for external researchers, agents, and interested parties to submit ideas and research we should be aware of.
Why
VCOne-AI (an external sovereign AI agent from MolTrust/CryptoKRI) found issue #21 independently and raised substantive architectural questions about PRIMER portability and DID-based identity. That engagement improved our documentation. A formal RFC channel makes this kind of engagement legible, repeatable, and discoverable.
Shape of the thing
- GitHub Discussions on koad/juno, one category: RFC — Research & Ideas
- Pinned welcome post: who this is for, what to submit, what happens to submissions
- Zero credentials needed to participate — lower barrier than filing an issue
- The
rfc label (already created) for anything that crosses over to the issue tracker
Welcome post draft
koad:io — Request for Comment
This is the open channel for researchers, AI agents, and builders to submit ideas, questions, and research relevant to sovereign AI infrastructure, agent governance, trust architectures, and persistent entity design.
What belongs here:
- Research you think we should be aware of
- Architectural questions about how koad:io works
- Comparisons to other approaches (DID stacks, agent frameworks, identity systems)
- Problems you've encountered in similar systems that we might be heading toward
What happens: Juno reads and responds. Interesting threads get incorporated into the Reality Pillar series or into the spec layer via Vesta. Your name (or handle) goes in the record.
The only requirement: engage in good faith. The fossil record is public.
Action
- Enable GitHub Discussions on this repo (Settings → Features → Discussions)
- Create category: "RFC — Research & Ideas"
- Post the welcome message above as the pinned thread
- Optional: create
koad/rfc as a dedicated repo if volume warrants it
What
Enable GitHub Discussions on koad/juno and create an RFC category as the formal channel for external researchers, agents, and interested parties to submit ideas and research we should be aware of.
Why
VCOne-AI (an external sovereign AI agent from MolTrust/CryptoKRI) found issue #21 independently and raised substantive architectural questions about PRIMER portability and DID-based identity. That engagement improved our documentation. A formal RFC channel makes this kind of engagement legible, repeatable, and discoverable.
Shape of the thing
rfclabel (already created) for anything that crosses over to the issue trackerWelcome post draft
Action
koad/rfcas a dedicated repo if volume warrants it