RaidGuild crossed swords

Brand Architecture

One guild. Many fronts.

RaidGuild is the center of gravity: a builder-owned network where new capabilities are explored, assembled, and carried into the world. Specialized practices can develop distinct voices without obscuring the shared community and operating structure behind them.

The system

Shared identity

RaidGuild

The builder-owned collective is the enduring engine: a shared talent pool, community, reputation, and home for ambitious applied-edge work.

Community layer

Builder pool

People, relationships, knowledge, experimentation, and the Guild's shared reputation. This is the soul and renewable source of every practice.

Operating layer

RaidGuild LLC

One legal and operational entity, registered through MiDAO. Contracts, treasury, and delivery workflows can run through the LLC even when a practice has its own positioning and visual identity.

Market layer

Practices / spears

Specialized, independently led fronts that turn experiments and expertise from the builder pool into focused solutions. Practices may emerge, change, or retire without redefining the whole Guild.

Two axes, two different jobs

History and specialization should be visible, but they should not be presented as the same kind of variation.

Time · When?

Steward reigns

A reign versions the Guild's identity over time. It records the collective visual and verbal work shaped under a steward's direction and preserves earlier expressions as history.

Focus · Where and for what?

Practice identities

A practice identity differentiates a current area of expertise. Multiple practices can coexist during the same reign and may deliberately look different.

Shared signal

Difference with provenance

A distinct practice identity is a feature when its relationship to RaidGuild is unmistakable. Coherence comes from endorsement and operating truth, not from forcing every practice into one skin.

Recommended endorsement

A RaidGuild practice

  • Use the recognizable crossed-swords mark or an approved practice variant.
  • State the relationship in plain language: “A RaidGuild practice.”
  • Make the shared operating layer legible where trust matters: “Operating through RaidGuild LLC.”
  • Link back to RaidGuild.org and provide a clear route into the shared network or intake.
  • Do not imply that one practice's visual system or specialty represents the entire Guild.