Welcome. This repository is the public forum for the KYE Protocol™ community: integrators, sector profile authors, security reviewers, governance contributors, and anyone building agentic systems that need provable identity, authority, scope, and audit.
| You want to… | Use |
|---|---|
| Ask how do I…? about an SDK, the reference Gateway, or a profile | 💬 Q&A |
| Propose a new sectoral profile (Healthcare-X, Treasury-Y, …) or change a vocabulary term | 📜 RFCs |
| Share an integration, demo, or case study | 🚀 Show & tell |
| Discuss governance, roadmap, conformance criteria | 🏛️ Governance |
| Report a security concern | Do not open a public discussion. Email security@kye-protocol (PGP key in SECURITY.md). |
| File a bug / feature request against a code repository | Open an issue on the relevant repo (vocabulary, id-format, examples). This forum is for cross-repo conversation. |
KYE Protocol™ is a public vocabulary and contract layer. The patent-track mechanism designs (decision algorithms, hash-chain construction, cascade ordering, attenuation propagation) are intentionally not published and are out of scope for public discussion. Stick to:
- Public vocabulary terms (entity types, lifecycle states, decision codes, signal types, obligations, stop conditions, reason codes)
- The KYE™ URN format (
kye:<class>:<trust-domain>:<subclass>:<local>) - The OpenAPI surface and JSON Schemas published in vocabulary, id-format, and examples
- The reference Gateway behaviours that conformant implementations must reproduce
- Integration patterns, SDK ergonomics, profile composition
If a question requires a specific algorithm, replay/audit-chain reconstruction technique, or cascade propagation rule that is not in the public vocabulary, the answer here will be: "that lives in the patent-track design and isn't published."
Be kind. Cite specifics. Assume good faith.
- Treat others' time as scarce.
- Quote the schema or vocabulary file you're referring to (link by line).
- Keep RFCs in a single thread; iterate via comments rather than re-posting.
- No marketing-only posts; share something the community can run, read, or evaluate.
- Conduct violations are handled per the org Code of Conduct.
KYE™, KYE Protocol™, and Know Your Entity™ are trademarks of the KYE Protocol™ project. Use them to refer to the protocol as published. Do not use them to identify a forked, modified, or unrelated project as "KYE™".
- 🌐 kye-protocol.github.io — interactive landing page
- 📚 Vocabulary — entity types, actions, decisions, signals
- 🔗 ID format — canonical URN scheme
- 📦 Examples — validated JSON for every schema
- 🏷️ Org profile — mission, governance, security policy
© KYE Protocol™. Apache License 2.0 for content licensable here. Trademark policy in .github/.