| --- |
| license: apache-2.0 |
| tags: |
| - deckergui |
| - dgm |
| - gate-protocol |
| - yolomoe |
| - agent-routing |
| - en |
| - license:apache-2.0 |
| library_name: deckergui |
| pipeline_tag: text-generation |
| --- |
| |
| ## DGUI DGM |
|
|
| **Digital Guild Master — Gate Protocol Engine** for DeckerGUI. |
|
|
| ### Overview |
| The DGM (Digital Guild Master) implements the 3-DGM gate protocol that every docking agent must pass before execution. It enforces capability validation, policy governance, and YoloMoE routing. |
|
|
| ### 3-DGM Gate Flow |
| ``` |
| DSYNC Memory Reset → Guard DGM → Supervisor DGM → YoloMoE Seeder → Execute |
| ``` |
|
|
| ### Components |
| - **DSYNC Memory Reset**: Validates agent memory state before evaluation |
| - **Guard DGM**: Capability guard — validates allowed capabilities and policy rules |
| - **Supervisor DGM**: Policy supervisor — enforces `no_high_anomaly`, `no_critical_threats` |
| - **YoloMoE Seeder**: Routes to specialist experts via vision-centric detection |
|
|
| ### DGM Factory |
| The DGM Factory (`DGM-Factory` feature) deploys docking agents through the strict 3-DGM gate and mints their Digital API Keys. |
|
|
| ### Gate Prediction Model |
| The companion model [`DGUI-GatePredictor`](https://huggingface.co/ctaxnagomi/DGUI-GatePredictor) predicts gate outcomes using DistilBERT token classification: |
| - `gate_pass` — Agent cleared for execution |
| - `gate_block` — Agent blocked by policy |
| - `quota_exceeded` — Key quota depleted |
| - `key_revoked` — Digital API Key revoked |
| - `scope_violation` — Capability out of scope |
|
|
| ### Citation |
| ```bibtex |
| @software{deckergui-dgm, |
| title={DGUI DGM}, |
| author={wan mohd azizi}, |
| year={2025}, |
| publisher={Hugging Face}, |
| url={https://huggingface.co/ctaxnagomi/DGUI-DGM} |
| } |
| ``` |
|
|
