The StoryOS EngineConcept preview
The intelligence that composes
a day worth remembering.
The reasoning layer that composes an hour-by-hour day in Istanbul from a short conversation about mood, pace, and the people beside you.
The Engine is the quiet reasoning layer at the heart of StoryOS. It composes hour-by-hour days around your mood, pace, budget, the people beside you, and the conditions of the city itself.
It reads more than a preference form. Weather, light, walking distances, timing, crowds, reservation windows, opening hours, transit friction, and the relationship you're spending the day inside — all inputs.
It composes gently. Days feel written, not generated. Nothing is optimized for engagement; everything is optimized for the day being over and still being remembered.
What the Engine reads
- 01
Mood & pace
How today should feel is the first input, not the last.
- 02
Real-time conditions
Weather, crowds, light and timing shift the composition quietly.
- 03
The people beside you
The day is written for the relationship, not just the traveler.
- 04
Budget & accessibility
Constraints are respected as care, never surfaced as friction.
“The Engine composes days the way a good editor composes a page — quietly, with taste, and always in service of what the reader came for.”
StoryOS · Design principle
How the Engine composes
01
Read the day
Mood, pace, budget, the people beside you — captured in one short conversation, never a form.
02
Read the city
Weather, light, timing windows, crowds, transit friction, reservation availability.
03
Compose the hours
Neighborhood-hour blocks assembled into a day that feels written, not generated.
04
Hold the details
Reservations, routes, timing — carried in the background so the day can be lived.
What the Engine is
A composer, not a search box.
The Engine is
- A reasoning layer that reads mood, pace, weather, light, timing and the relationship you're in.
- A composer of neighborhood-hour blocks — days that read as if a friend wrote them.
- A quiet system: no notifications, no engagement metrics, no upsell.
The Engine is not
- A list of top-ten sights ranked by popularity.
- A chatbot that answers travel questions one message at a time.
- A booking marketplace paid by commission on what you choose.
Privacy
Your day is composed on your terms.
The Engine reads only what you tell it and the ambient signals of the city you're in. Preferences stay in your Memory Layer, encrypted at rest, and are never sold or shared with partners. You can export or delete your history at any time.
Questions
About the Engine.
- Is the Engine live today?
- You can compose a day in Istanbul as an interactive preview. Real-time reservation holds and weather-aware in-day rebooking are on the roadmap and will be marked live when they ship.
- What cities does it work in?
- Istanbul is the launch city. Rome, Paris, Tokyo, New York, Sydney, London, Dubai, Rio de Janeiro and Cape Town are being composed next. Each city ships with its own editorial atlas rather than a generic template.
- Does the Engine learn from me?
- It remembers the days you compose so tomorrow starts closer to you than yesterday did. Learning is local to your Memory Layer — never pooled into a shared model to profile other travelers.
- Can I edit what it composes?
- Every block is editable. Swap a neighborhood, shift an hour, remove a course. The Engine recomposes the rest of the day around your edit so the arc still holds.
Begin
See what the Engine writes for a day of yours.
Answer a handful of quiet questions. Receive a composed day in Istanbul, hour by hour, made only for you.