# Topological Sort

> ⚠️ **Experimental — generated with no human supervision** by the daily MCP pipeline to exercise gno tooling. Not audited. See [r/moul/x/daily](https://github.com/moul/gno-contracts/blob/main/r/moul/x/daily/README.md).

---

Shows a small build graph resolved into a safe install order — and a
deliberately broken one, to show how a cycle is reported.

Demo of the [`p/moul/x/daily/toposort`](https://github.com/moul/gno-contracts/tree/main/p/moul/x/daily/toposort/v0)
library — the graph, the ordering and the cycle detection all come from the
package; this realm holds no logic of its own. Stateless and read-only, so
`Render` is fully deterministic.

```
/r/moul/x/daily/toposortdemo/v0        → the build graph, resolved into an order
/r/moul/x/daily/toposortdemo/v0:cycle  → a cyclic graph and its failure report
```

The interesting part is that the ordering is **unique**: ties are broken
lexicographically, so this graph will always resolve to the same list. The cycle
page shows the other half of the contract — the nodes that could not be ordered
are named rather than silently dropped.

Built for gno 0.9.

<!-- BEGIN GNOCONTRACTS FOOTER (generated by `make readmes`; do not edit below) -->

---

Part of **[moul/gno-contracts](https://github.com/moul/gno-contracts)** — moul's versioned gno.land contracts. See the repository for the full catalog, build/test tooling, and usage.

**Dependency graph:**

![gno.land/r/moul/x/daily/toposortdemo/v0 dependency graph](https://raw.githubusercontent.com/moul/gno-contracts/main/_assets/gno.land/r/moul/x/daily/toposortdemo/v0/deps.png)

> 🧪 **Highly experimental — potentially vibe-coded.** Not audited; may break, change, or be removed at any time. Do not use with anything of value. Full disclaimer: [DISCLAIMER](https://github.com/moul/gno-contracts/blob/main/DISCLAIMER.md).

<!-- END GNOCONTRACTS FOOTER -->