Development notes
What LOVE needs to demonstrate next
The work ahead is a sequence of specific questions: can the opening engage, can choices carry forward, and can the experience remain understandable and manageable?
Begin with a clear account of the stage
LOVE is SYMB10's proposed story-driven AI companion. The project has a character direction, concept artwork and an articulated experience vision. Those materials help explain what we want to make. They do not, on their own, demonstrate a working connected product, sustained demand or a viable operating model.
The next phase needs to turn that vision into work that can be examined. We see this as a sequence of concrete development questions. Each question should have a suitable demonstration and an honest account of what remains unresolved. This article describes that proposed direction, rather than announcing completed milestones or a launch schedule.
Can the opening make sense?
A first experience needs to establish who LOVE is, what situation the person has entered, and how they can participate. A focused opening scene could examine those points without requiring a large world or an extensive catalogue of content.
We would want to understand whether participants can describe the character and the decision in their own words. Confusion about what a response means, or what the product is offering, would be useful evidence for revision. A visually impressive introduction would not answer those questions by itself.
Can a choice carry forward?
The next demonstration would connect an earlier decision to a later scene. The important behaviour is continuity: the story acknowledges what happened, keeps the character coherent, and presents a consequence that someone can understand.
The same work should consider correction and removal. If a remembered detail is wrong, can it be changed? If a person chooses to remove information, can the experience explain the effect and continue appropriately? These ordinary control paths deserve attention alongside the more visible narrative moments.
Can the experience be operated responsibly?
A connected version would introduce further questions about reliability, cost, data handling and failure. A demonstration should make clear whether dialogue is scripted, generated, or a combination, and which parts of the system are actually functioning. An attractive interface should not obscure that distinction.
Before a public release, the intended boundaries would also need to be reflected in real interactions. That includes how the experience handles a pause, a declined reminder, an unexpected request and an unavailable service. Describing those cases is part of defining what needs to be built and assessed.
Is it worth returning to?
Our planned subscription model introduces another question: whether people value the continuing experience enough to choose it again and pay for access. Repeat use, willingness to pay and sustainable delivery are questions to investigate. We are not presenting them as established results, and pricing and availability remain unannounced.
Future updates should connect a claim to the work behind it: what was made, what was examined, what was learned and what changed. That gives people following SYMB10 a useful way to understand progress. The aim is a series of demonstrated improvements that bring the proposed experience closer to something people can use.
Explore the proposed experience and the ideas behind its development.
Our approach
