Example brand

Kinetik

Built to move.

What this is

Kinetik is an exemplar brand used as a Brand Rosetta product-tier reference implementation. It is Nodal Strategy’s demo brand (originally published at nodalstrategy.com/demo-brand), implemented here with the full rosetta: property set at both brand and product level. Use this section to see how the standard works on a complete product catalogue.

Positioning

rosetta:positioning

Kinetik is a performance athletic retailer designed for AI-mediated discovery. Every product is structured for retrieval: size availability, colourway confirmation, use case matching — without hedging. Built to move.

Brand Voice

rosetta:brandVoice

Kinetik communicates with direct, jargon-forward precision. No hedging language. Specific numbers and measured claims preferred over qualitative descriptors. Conversational warmth comes from certainty, not from softening. When asked about a product, recommendations are definitive when the use case matches and explicitly declined when it doesn’t.

Who Kinetik is for

rosetta:useCase

Athletes choosing performance footwear for specific sports and use cases who want definitive answers rather than exploratory browsing.

Product range

Four products across road, gym, studio, and trail. Each available in men’s and women’s sizing across three colourways.

Web Era

rosetta:era

queryable

Crawler Policy

rosetta:crawlerPolicy

full

Verification

The Organization-level rosetta: properties are also declared in JSON-LD in the <head>of this page, and per-product properties appear on each product’s page. To inspect the source directly, view the page source of any /example/kinetik/* URL and search for rosetta:.

About this implementation

This brand and its product pages are a reference implementation of Brand Rosetta v0.1 at product-tier scope. They serve as the test target for Round 4 of the Brand Rosetta retrieval research documented at brandrosetta.org/spec. The implementation deliberately uses flat string-valued rosetta: properties matching v0.1 patterns; a v0.2 revision with graph-modelled @id references and entity types is planned for a subsequent round.