Entity graph
Genesis Seeds knowledge map
Wardenseed treats each Genesis Seed as an indexable entity. This hub connects entity profiles to category indexes and documentation clusters so crawlers and collectors traverse a structured graph instead of a flat listing.
Genesis Seeds entity ontology
The Wardenseed Genesis Collection is modeled as exactly one thousand indexable entities. Each entity is a token ID with a stable encyclopedia profile at /seeds/{id}. Profiles expose rarity rank, mythic identity, biome palette, visual aura, trait bundles, and bidirectional links into documentation clusters. This hub is the macro-node that compresses the entity subgraph for crawlers and collectors.
Entity authority does not come from page count alone. It comes from graph structure: every seed profile should connect upward to category indexes (rarity, mythic, aura), sideways to related seeds, and outward to explanatory docs. Category indexes connect back to seed subsets and to this hub. Documentation pillars link down to featured seeds and category bands. That closed loop is what converts a flat directory into a knowledge graph.
The public canonical root for seed discovery is /seeds, not /nft/seeds. The encyclopedia index and all token profiles live under /seeds. The /nft/seeds route is a wallet-gated transactional surface for mint and inventory tabs. It is excluded from sitemap, disallowed in robots.txt, and must not appear as seedsHub in machine-readable discovery feeds.
Collectors and search systems should treat onchain ERC-721 metadata as ownership truth and encyclopedia pages as interpretive ground truth. Documentation explains shared rules: how rank maps to rarity bands, how mythic identity layers lore grammar, and how traits affect presentation without implying financial outcomes. When a capsule-level fact matters, resolve it on the profile page first, then follow linked guides for context.
Traversal model: enter at this hub or /seeds, descend into a category band or individual profile, cross into genesis-collection or relics-traits docs, then return via related documentation blocks on seed pages. That pattern reinforces cluster authority inside the Genesis Seeds topic without orphan entities.
System invariants
- Fixed supply of 1,000 Genesis Seed entities; token IDs are stable primary keys.
- Public entity URLs live under /seeds/{id}; transactional UI lives under /nft/seeds (non-indexable).
- Every encyclopedia profile links to at least one doc cluster and one category index.
- Category indexes enumerate seed subsets and link back to documentation pillars.
Graph definition
- Hub: seeds-overview→/seedsindexes
- /seeds/{id}→/docs/*contextualizes via related docs
- /seeds/rarity/*→/seeds/{id}aggregates subset
- /docs/cluster/genesis-collection→/seeds/{id}featured entities
Knowledge hubs
Encyclopedia and profiles
Every token ID has a dedicated profile with traits, rarity rank, mythic identity, and links into related documentation.
Category indexes
Aggregation pages group seeds by rarity, mythic identity, and visual aura. Use them for crawl depth and collection comparison.
Collector documentation
Documentation explains shared rules; encyclopedia pages show per-token ground truth.