JOURNEY

Date index

The build log starts in December 2025 and follows the projects as they moved from prompts and local experiments into visible product systems.

Use this as a reverse-chronological map: each row opens the exact project page and anchors to the dated moment.

June 2026

launch layerWGTakt mobile appThe app became a story people can inspect
archiveSantorinoThe fragment earned a page
resourceSEO DashboardSEO became a public workflow story
indexPrototypeThe prototype lane became searchable
ux correctionWGTakt mobile appThe chat tab could not become a trap / prompt trace
source idsCost articlesThe numbers were not rankings / prompt trace
emsqreSEO DashboardThe blog got its own crawl layer
shipEdelweissThe repo got pushed as a product asset
verificationNeeedThe matrix became the product memory
profile qualityNeeedAI profiles needed craft-specific proof
cost bridgePressroomCost articles entered the control center
public safetyNeeedRaw request text could not leak into public surfaces
dedupeCost articles`covered` did not mean finished / prompt trace
routingNeeedUnknown services stopped falling into events
concept lockNeeedAny service meant AI-generic first / prompt trace
repairSEO DashboardCost article SEO needed structure, not polish
handoffPressroomThe system learned how to be continued
voiceVividishThe copy had to stop sounding generated / prompt trace

May 2026

moneyWGTakt mobile appThe money layer stopped being bolted on
guest viewVividishThe menu became the public product
editorial qaPressroomValidation became a review surface
neeedPrototypePrototype screens hardened into verification
systemSantorinoSantorino sat beside restaurant-platform thinking
operationsVividishThe back office became a service map
safetyPressroomUpload became a guarded act
fairnessWGTakt mobile appRound-robin was not enough

April 2026

prototypePressroomThe pipeline became visible
validationSEO DashboardSEO moved into article review
fidelityVividishBlueprint and production had to match
draftingCost articlesDrafts became inventory, not loose files
native turnWGTakt mobile appThe app inherited the bot's best behavior
flowVividishPayment and reservation became closeout problems
mappingCost articlesTopics needed a vertical home
translationWGTakt chatbotFrom reply bot to house OS
seasonalityEdelweissThe product library became seasonal
seedCost articlesThe catalog became a dataset
crawlerPrototypeExtraction work became product thinking
constraintWGTakt chatbotWhatsApp was right for proof and wrong for launch
reuseSantorinoThe logo became reusable evidence

March 2026

state machineWGTakt chatbotThe backend became the product
tasteSantorinoThe brand thread stayed separate from feature work
reservationEdelweissThe reservation form got tightened
canvasPrototypeCanvas became a test surface
normalizationSEO DashboardRaw search numbers needed safer meaning
identitySantorinoThe name became a place
lessonVisualMenuThe menu needs evidence, not adjectives
bridgeVisualMenuVisualMenu became a seed for restaurant product thinking

February 2026

compositionVisualMenuBackground and cutout became two different jobs
menu uxVisualMenuVisual choice reduces reading load
asset thinkingVisualMenuThe drink became a composable object
bot testWGTakt chatbotThe interface became a roommate reply
scratchPrototypeThe unnamed ideas stayed alive

January 2026

seoEdelweissThe cafe became searchable

December 2025

visual baseEdelweissThe site started with place and appetite
pain pointWGTakt chatbotThe calendar stopped being enough