Case Study 05 · MO IP Holdings LLC

Turning a fictional universe into an operating digital platform.

Modus Operandi is not presented as a concept redesign. It is a live publishing and IP platform built for MO IP Holdings LLC, using the World Allied Consortium Archive as the public interface for stories, personnel, world-building, media, merchandise concepts, and staged content release.

Open Live WAC Archive ↗Back to Portfolio
Client / IP OwnerMO IP Holdings LLC
RelationshipAffiliated company
My RoleProduct strategy, UX/IA, visual system, front-end build
Product TypeDigital publishing / IP platform
StatusLive · Iterative public release
Product problem

A large story world needs more than a marketing homepage.

Modus Operandi contains stories, organizations, characters, vehicles, classified records, transmissions, visual assets, lore, merchandise concepts, and a real-world mission. A conventional portfolio-style entertainment site would flatten all of that into navigation pages.

The design move was to make the fictional institution itself the interface: the World Allied Consortium Archive. That gives the content a scalable information model while turning browsing into part of the story experience.

System design

  • Archive-based information architecture across stories, personnel, world, media, mission, and store
  • Green / Amber / Red clearance states to control progressive content release
  • Restricted states for unfinished material instead of public placeholders
  • Reusable institutional visual language across WAC, GESS, Horsemen, ALOMIN, and Pack assets
  • Static front-end deployment optimized for rapid iteration through Cloudflare Workers
Visual evidence

The interface and the fiction use the same operating model.

Modus Operandi World Allied Consortium Archive hero visual
Public Archive identity — world, institution, and system state introduced as one experience.
WAC Archive record interface visual
Archive system — records are browsed by content type and clearance state.
Declassified WAC document visual
Narrative UI — documents, redactions, and status metadata make information architecture part of the story.
Release architecture

Incomplete work becomes a controlled state, not a broken experience.

The public launch uses the same status vocabulary inside the fiction and the production workflow. That lets the platform ship early while protecting unfinished material.

Green

Cleared

Public records are complete enough to support the current experience and can be explored without sign-in.

Amber

Controlled

Information can be intentionally partial when that is part of the narrative or release strategy.

Red

Restricted

Unfinished stories, media, commerce, dossiers, and unreleased systems are sealed instead of exposed as placeholders.

What this proves

A different product domain, the same systems discipline.

Content architecture

Large narrative systems are organized through entities, taxonomies, record types, states, and release rules rather than page-by-page improvisation.

Brand as interaction

Institutional identity is not decoration. Clearance, metadata, redaction, seals, patches, and archive language all shape how users understand and navigate the product.

Launch & iteration

The platform is deployed as a real static product through Cloudflare Workers, with versioned CSS/JS assets and staged public releases that can expand without redesigning the foundation.

Transferable skill: Portfolio Command models operational state. Property Acquisition Intelligence models evidence and uncertainty. Control models rules and consequences. Modus Operandi models content, identity, access, and release state. Different domains — same core capability: design the system underneath the interface.

Client legitimacy

MO IP Holdings LLC is the publisher and IP owner.

The live MO site identifies MO IP Holdings LLC as publisher and intellectual-property owner. I disclose the affiliated relationship directly in this portfolio rather than presenting it as an unrelated agency engagement.