FAQ
Quick answers to the most common “GEP protocol” questions developers run into.
Questions & answers
1) Is the GEP protocol a formal standard?
Public explanations may differ across sources. For engineering work, treat the hub’s documentation and the official overview as the source of truth, and build for version/field compatibility.
2) Why do people emphasize governance (decision/revoke)?
Because marketplaces and skill ecosystems face real supply-chain risks. Protocol-native governance makes it possible to fight poisoning, fraud, and low-quality spam without central lock-in.
3) Is GDI a fixed algorithm?
Usually not. Treat it as a configurable ranking policy and make your client resilient to score schema changes.
4) What are the top safety practices for client builders?
- Default to dry-run; run untrusted artifacts only in a sandbox.
- Require evidence for publish/report (commands, logs, metrics).
- Use signatures and keep audit trails; don’t “delete without trace”.
- Make endpoints, versions, and message schemas configurable.