Tenue

TENUE ; who is your fragrance?

Verified Fragrance Ownership and Presence Network

TENUE is a platform that transforms luxury fragrance from a private object into a persistent, visible, and social identity layer.

Users register the exact fragrances they own, log when they wear them, and connect with others through shared ownership. Each fragrance forms its own network (“village”), and each wear event contributes to a living map of fragrance presence.

TENUE enables identity to persist through scent.


Core Principles

TENUE is built on three fundamental signals:

Ownership

Permanent record of which fragrances a user owns.

Ownership is binary. You either own a fragrance or you do not.

Ownership defines identity structure.


Presence

Temporal record of when a fragrance is worn.

Presence evolves over time through wear logging.

Presence defines identity continuity.


Village

Community formed by shared ownership of a specific fragrance.

Each fragrance automatically forms its own network of owners.

Villages define identity adjacency.


System Overview

TENUE consists of five core subsystems:


Feature Breakdown

Identity System

Provides persistent user identity.

Features:

Purpose:

Creates persistent identity surface.


Ownership System

Tracks exact fragrance possession.

Features:

Ownership records are permanent.


Presence System (Wear Logging)

Tracks fragrance usage over time.

Features:

Future integration:

Presence transforms ownership into living identity.


Village System

Each fragrance forms its own community.

Village page includes:

Villages are generated dynamically.


Cultural Intelligence System

Tracks fragrance presence across all users.

Features:

Creates real-time cultural map of fragrance presence.


Journal System

Tracks relationship between user and fragrance over time.

Features:

Creates narrative continuity.


NFC / QR Integration Model (Future)

First tap or scan:

Subsequent taps or scans:

MVP simulates this interaction via software button.


Technology Stack

Frontend

Purpose:

Hosted on:


Backend

Provides:

Supabase functions as backend-as-a-service.


Database

PostgreSQL via Supabase.

Stores:


Authentication

Supabase Auth

Supports:


Infrastructure

Fully serverless architecture.


Database Schema

Users

Stores identity.

Fields:


Fragrances

Stores fragrance objects.

Fields:


Ownership

Stores permanent ownership records.

Fields:


WearEvents

Stores wear logging events.

Fields:


Friends (Future Expansion)

Stores friend relationships.

Fields:


Core API Operations

Register User

Creates new user identity.


Add Ownership

Creates ownership record and assigns village membership.


Log Wear Event

Creates presence record and updates journal timeline.


Fetch Profile

Returns:


Fetch Fragrance Village

Returns:


Core Pages

Login Page

Handles authentication.


Profile Page

Displays:


Fragrance Page (Village Page)

Displays:


Add Fragrance Page

Allows users to register ownership.


Journal Page

Displays wear history timeline.


Presence Model

Presence weight derived from wear frequency.

Example:

presence_weight = log(1 + wear_count)

This prevents runaway scaling while preserving relative strength.

Presence weight powers:


Deployment

Frontend:

Backend and database:

No dedicated backend server required.

Fully serverless deployment.


MVP Scope

Minimum viable TENUE includes:

Hardware integration not required for MVP.


Future Expansion

Planned features:

These extend the ownership-presence model.


Vision

TENUE creates a persistent identity layer anchored in fragrance ownership.

Ownership defines structure.

Presence defines continuity.

Villages define connection.

TENUE transforms fragrance into shared cultural presence.