The ideal experience for me would be nearly seamless between web2 and web3 users, provide many loops for return interactions with the app environment based on community inputs around various topics and features. the community would drive the feature set and we would be responsive and dedicated to providing a rich and immersive user and community and club and company culture.

The slowest part of the project is the part where we dwell on past mistakes, we can make it faster by focusing our discussions on solutions and next steps and by reading each other’s documentation. BUT…

…the slowest part of the app doesn’t exist yet. it is a loop created by return users and human artist inputs that make it exciting for someone to wait for an artist to finish a commission because then you can use their updated style checkpoint. it is slow because we want it to be and we use the slowness to build anticipation and buzz.

…the slowest part of our end to end is the homework for users of providing a character sheet - and although that feature of the app has value it is also the thing to remove.

…the slowest part of private beta is going to be setting realistic expectations for design, dev and admin timelines.

…the slowest part of marketing is planning

…the slowest part of my brain is the part that has to decode your true meanings but the fastest part is the one that obfuscates mine.

Ceptor Club has all of the following style properties: Wise, Creative, Opportunistic, Off-beat, Considerate, Magical, Sly, Exclusive

When used in design these properties are already evident in the architecture of the app and the look and feel in the figma. When used in marketing copy or communications, this set allows for anyone in our group to be the core composer of any draft of something and provides a baseline for the archetypes we might like to add to our decision-making body.