# Product Vision **The Curiosity Lab** Version: 0.3 Status: Current Working Product Vision Current phase: Documentation consolidation and practical paper testing Path: `/mvp/Product-Vision.md` --- ## 1. Product Definition The Curiosity Lab is a research-led programme exploring whether environments can be intentionally designed to cultivate curiosity through meaningful connection. The current MVP direction is: > **A Living Narrative Canvas in which an object’s initial description remains visible, users explore meaningful associations around it, and the narrative becomes richer as those associations are woven back into the story.** The prototype is not intended to deliver a complete educational journey. It is intended to test a smaller proposition: > **Can visible meaning accretion around an object help a person see it differently, recognise meaningful relationships and ask a better next question?** The current product model is: ```text Persistent Object Narrative ↔ Narrative Anchors ↔ Associations ↔ Narrative Insert Preview ↔ Meaning Weave ↔ Expanded Narrative ↔ Meaning Trace ``` --- ## 2. Mission > **Leave every person slightly more curious than you found them.** This does not mean giving the user the largest possible amount of information. It means helping the user leave with one or more of the following: ```text a changed perception of the object a clearer understanding of why a relationship matters a newly recognised motif or theme a meaningful connection across contexts or disciplines a better question a desire to continue exploring ``` Two supporting programme principles remain: > **Increase curiosity, not content.** > **No research without implementation potential.** The project should remain intellectually ambitious while producing ideas that can be tested through real interactions. --- ## 3. Current Product Decision The current product direction is: ```text Prototype v0.3 — Living Narrative Canvas ``` The core principle is: > **The narrative is not the endpoint of exploration. > The narrative is the surface on which exploration happens.** The earlier v0.1 and v0.2 prototypes are retained as research history. They should not control the active product. ### Earlier models ```text v0.1: Object → Guided Observation → Labelled Doorways → Explanation → Sensemaking Trail → Reflection ``` ```text v0.2: Look → Tension → Context → Insight → Return → Doorway → Reflection → Saved Narrative ``` ### Learning from those models The earlier MVPs demonstrated that: ```text a pathway can be clear a pathway can be usable a pathway can contain relevant information and still feel lifeless ``` The experience remained too: ```text linear prescribed instructional menu-like detached from the original vision ``` The most valuable outcome was the clarification that: > **The object description should remain visible and expand with meaning through exploration of motifs, themes, contexts and relationships.** --- ## 4. Product Problem Many knowledge experiences organise information as: ```text static labels isolated facts topic menus search results linear explanations raw knowledge graphs ``` These structures may be informative. They do not necessarily help a person understand: ```text why the details belong together why the object matters how one relationship changes another how a concrete object participates in wider themes how apparently distant subjects share hidden patterns ``` The product problem is: > **How might we let users explore connected meaning around an object while keeping the object’s narrative present, coherent and visibly changing?** A successful experience must avoid two extremes. ### Too author-directed ```text The user is pushed through a predetermined lesson. ``` ### Too unstructured ```text The user receives a collection of links or a graph without interpretive help. ``` The intended balance is: ```text authored evidence and relationships + user-selected exploration order + visible narrative development ``` --- ## 5. Research Problem The wider research question is: > **Can we intentionally design environments that cultivate curiosity through meaningful connection?** The v0.3 product question is narrower: > **Does a persistent, expanding object narrative make exploration feel more natural, meaningful and curiosity-provoking than a fixed explanatory sequence?** Supporting questions include: ```text Do Narrative Anchors invite voluntary exploration? Do users understand why associations exist? Does each Narrative Insert change the interpretation of the object? Do motifs and themes emerge naturally? Do obscure references increase worldness or create distraction? Do Structural Echoes deepen understanding or merely feel clever? Does the narrative remain coherent after several inserts? Does the user ask a better next question? ``` --- ## 6. Working Hypothesis The current v0.3 hypothesis is: > **A user will experience more curiosity and meaning when a basic object description visibly expands through explored associations than when they are led through a fixed linear explanation.** Supporting hypotheses: ```text A persistent narrative will keep the object cognitively present. Concrete anchors will invite exploration more naturally than abstract topic menus. Associations will feel meaningful when their relationship basis is explained. Narrative Inserts will make the development of interpretation visible. Themes will be stronger when they emerge through exploration. Context Sparks will increase worldness when they reconnect to the object. Structural Echoes will support transfer when both the shared pattern and its limits are clear. A Meaning Trace will help show how understanding changed without asking the user to write the whole narrative. ``` These are hypotheses, not established findings. They must be tested. --- ## 7. Product Experience The experience begins with a concise object narrative. For the first MVP object: ```text A bronze sestertius of Trajan, dated 103–111 CE, shows the emperor on one side and an arched bridge over a river, probably the Danube, on the other. ``` This Base Narrative remains visible. The user may select Narrative Anchors such as: ```text bronze sestertius Trajan 103–111 CE emperor bridge Danube coin ``` Each anchor may open several bounded associations. An association should explain: ```text what the connection is why it matters what relationship basis supports it what motif or theme it develops what evidence status it has how it would change the visible narrative ``` The user may preview a Narrative Insert before choosing to weave it into the story. The visible narrative then develops from: ```text description + basic facts ``` toward: ```text description + context + motifs + themes + lived-world detail + structural relationships + accumulated interpretation ``` The user controls the exploration order. The system remains responsible for: ```text evidence wording relationship clarity narrative coherence limits of analogy ``` --- ## 8. Core Product Concepts ### 8.1 Living Narrative Canvas A persistent narrative surface that remains visible while the user explores meaningful associations around an object. It is not a sequence of screens. It is not a knowledge graph presented directly to the user. --- ### 8.2 Base Narrative The short initial object description. It establishes: ```text what the object is what is visibly or evidentially present the initial details that may become anchors ``` The Base Narrative should be specific enough to support curiosity without front-loading the interpretation. --- ### 8.3 Narrative Anchor A meaningful word, phrase, detail, person, date, place or concept that can open further interpretation. An anchor should not exist merely because a term can be linked. It should open an association capable of changing the object narrative. --- ### 8.4 Association A meaningful relationship opened from an anchor. Possible association types include: ```text basic_fact historical_context obscure_reference context_spark category theme structural_echo modern_parallel question evidence_note ``` Every association must have a reason for being present. --- ### 8.5 Relationship Basis The reason the association exists. Candidate values include: ```text topical contextual causal temporal spatial narrative structural analogical contrastive evidential functional symbolic ``` The relationship basis should prevent arbitrary “related content”. --- ### 8.6 Narrative Insert A concise authored passage that can be added to the visible narrative after an association is explored. A Narrative Insert should: ```text remain connected to the object integrate rather than merely list information change the interpretation preserve evidence status remain short enough to keep the narrative readable ``` --- ### 8.7 Meaning Weave The action of adding an explored Narrative Insert to the current narrative. The user may choose whether a connection belongs in the developing story. --- ### 8.8 Meaning Accretion The visible enrichment of the narrative as associations are woven into it. The test is not whether the text becomes longer. The test is whether the object becomes more meaningful. --- ### 8.9 Motif A concrete recurring or emphasised element that gathers significance through connection. Examples: ```text bridge crossing movement portrait circulation metal authority ``` --- ### 8.10 Theme A broader organising idea that emerges across motifs, contexts and associations. Examples: ```text portable authority infrastructure as power trust public memory ordinary life movement ``` Themes should emerge through exploration rather than be presented initially as a topic menu. --- ### 8.11 Context Spark A short contextual detail that makes the object feel part of a lived world. Examples: ```text who might have handled the coin whether it was ordinary money or treasure what kinds of exchanges it entered what would have felt familiar or strange in its world ``` A Context Spark is not trivia. It must reconnect to the object and change the user’s sense of its world. --- ### 8.12 Structural Echo A meaningful connection between apparently unrelated things that share an underlying structure. Example: ```text Roman coin ↔ passport ``` Possible shared structure: ```text small official object portable authority recognition across distance trust in an issuing power movement through social systems ``` A Structural Echo must state: ```text what is shared why that shared structure matters where the analogy stops ``` It must never imply identity when only one structural resemblance exists. --- ### 8.13 Meaning Trace A local record of: ```text anchors explored associations previewed associations woven themes revealed Structural Echoes revealed current narrative optional final thought optional next question ``` The user does not write the full narrative. The system captures how the narrative developed. --- ## 9. Target User The first MVP is intended for a curious adult who: ```text is willing to spend a few minutes with one object does not need specialist historical knowledge is interested in understanding why details matter may enjoy surprising but well-explained connections ``` Potential later audiences include: ```text museum visitors educators students lifelong learners cultural travellers people exploring collections ``` The first MVP should not attempt to serve all of these audiences simultaneously. --- ## 10. User Value The immediate user value is not mastery of Roman coinage. It is the experience of moving from: ```text I see an old coin with an emperor and a bridge. ``` toward something like: ```text I now see a handled object that could carry authority, military memory, engineering, movement and trust through everyday exchange. ``` The desired outcome is: > **I see the same object differently now.** A secondary outcome is: > **I am left with a question worth following.** --- ## 11. Product Principles ### PV-001 — Curiosity Before Engagement Do not optimise primarily for: ```text clicks completion time spent content consumed ``` A better question may be a stronger success signal than complete traversal. --- ### PV-002 — Increase Meaning, Not Merely Content More facts do not automatically create understanding. Every added association should make the object story richer. --- ### PV-003 — Keep the Object Present The Base Narrative should remain visible throughout exploration. The object must not become a forgotten pretext for unrelated content. --- ### PV-004 — Description Before Interpretation Begin with a stable, evidence-aware description before adding broader meaning. --- ### PV-005 — Specific Before Abstract Begin with: ```text this object this image this material this date this place this historical moment ``` before moving toward: ```text power trust identity empire infrastructure public memory ``` --- ### PV-006 — Narrative Without Forced Sequence Narrative coherence does not require linear navigation. Do not reintroduce a hidden step index, mandatory order, or Next/Previous flow. --- ### PV-007 — Associations Need Reasons Every association should explain why it exists. A generic related link is insufficient. --- ### PV-008 — Meaning Should Accrete Visibly The user should be able to see how explored relationships changed the narrative. --- ### PV-009 — Themes Should Emerge Do not start with an abstract theme menu. Allow themes to become visible through motifs and associations. --- ### PV-010 — Context Sparks Build Worldness Small contextual details should help the user imagine the object in a lived world. They should not become trivia. --- ### PV-011 — Structural Echoes Need Boundaries Unexpected cross-domain connections should explain both the shared pattern and the limits of comparison. --- ### PV-012 — Evidence Before Fluency A smooth narrative must not make an uncertain claim appear established. Distinguish: ```text object record established fact supported interpretation working hypothesis analogy research debt ``` --- ### PV-013 — User Agency, Authorial Responsibility The user chooses what to explore. The system remains responsible for the accuracy, coherence and transparency of the material. --- ### PV-014 — The User Does Not Write the Whole Story Optional reflection or a next question may be captured. The system constructs the developing narrative from explored associations. --- ### PV-015 — Practical Testing Before Expansion The interaction should work in a paper test before more implementation effort is authorised. --- ### PV-016 — Small, Visible, Revisable Changes Every implementation task should produce a specific, manually testable difference. Do not use broad implementation prompts. --- ## 12. Association Quality Standard An association should not enter the MVP unless it passes these checks. ### Object connection ```text Does it reconnect clearly to the object? ``` ### Interpretive value ```text Does it change or deepen the object narrative? ``` ### Relationship clarity ```text Can the reason for the connection be explained? ``` ### Evidence honesty ```text Is its status represented accurately? ``` ### Narrative fit ```text Can it be woven into the story without feeling appended? ``` ### Concision ```text Can it be expressed in one sentence or one short paragraph? ``` ### Analogy boundary For a Structural Echo: ```text Are the shared structure and the limits both clear? ``` If an association is merely interesting, it should be removed or deferred. --- ## 13. First Object and Content Scope The first object is: ```text Bronze sestertius of Trajan The Metropolitan Museum of Art Object number 08.170.120 Date 103–111 CE Roman, Mid Imperial, Trajanic Bronze Trajan portrait on the obverse Arched bridge over a river, probably the Danube, on the reverse ``` For the first practical test, use approximately: ```text 5–7 Narrative Anchors 2–3 strong associations per tested anchor no more than 2 Structural Echoes one concise Narrative Insert per association a small number of emergent themes ``` The first test should prioritise content quality over breadth. --- ## 14. Minimum Viable Experience The practical v0.3 test requires: ```text a visible Base Narrative selectable Narrative Anchors an Association Panel a clear explanation of why the association matters a Narrative Insert preview a choice to add it to the story a visibly expanded narrative a light record of explored meaning ``` It does not require: ```text a full Angular application complex animation multiple objects a graph visualisation AI-generated prose personalisation accounts a backend ``` --- ## 15. In Scope for v0.3 ```text one Roman coin object one authored Base Narrative bounded authored associations motifs and emerging themes Context Sparks a very small number of Structural Echoes Narrative Insert previews Meaning Weave visible Meaning Accretion Meaning Trace local-only data handling paper testing one narrow implementation slice after evidence ``` --- ## 16. Out of Scope for v0.3 ```text authentication user accounts Firebase database CMS admin editor full graph UI search personalisation recommendation engine AI-generated content analytics dashboard gamification social sharing payments mobile wrapper multiple object journeys automatic narrative rewriting dynamic summarisation large-scale visual design system ``` These exclusions are deliberate. They protect the research question from implementation noise. --- ## 17. Ethical and Evidential Commitments The Curiosity Lab should not use curiosity as a pretext for manipulation. Do not use: ```text false mystery artificial cliffhangers pressure wording compulsory reflection hidden behavioural profiling engagement maximisation speculation presented as fact ``` Preserve: ```text choice skip return clear relationship explanations source transparency evidence cues confidence levels limits of analogy optional reflection ``` The MVP should collect the minimum data required for research. Do not collect: ```text name email login identity precise location sensitive personal data cross-site behaviour long-term behavioural profile ``` --- ## 18. Success Criteria The v0.3 direction is promising if users: ```text understand the starting object voluntarily select another anchor can explain why at least one association matters notice the narrative becoming richer describe the object differently after exploration recognise an emerging motif or theme understand the basis of an unexpected connection remain aware of fact versus interpretation ask a new or better question describe the experience as exploratory rather than instructional ``` The strongest practical signal is: > **The user can explain how one explored association changed the object story.** --- ## 19. Failure Criteria The experience needs revision if: ```text the user waits to be led through steps anchors feel like a disguised topic menu associations feel arbitrary the narrative becomes a pile of facts the user cannot see what changed the object disappears behind wider themes Structural Echoes feel clever but shallow the narrative implies unsupported certainty the user cannot distinguish fact from interpretation the experience still feels like a lesson ``` The v0.3 model should not be protected from failure. It is the current hypothesis, not a doctrine. --- ## 20. First Experiment The recommended first formal experiment is: ```text EXP-MVP-012 — Living Narrative Canvas Paper Test ``` ### Primary hypothesis > **A persistent object narrative that expands through user-selected associations will feel more meaningful and curiosity-provoking than a fixed explanatory sequence.** ### Test material ```text Base Narrative Narrative Anchors Association summaries Relationship Basis Narrative Insert previews Expanded Narrative area Meaning Trace ``` ### Primary observations ```text first anchor selected reason for selection associations previewed associations accepted or rejected voluntary selection of another anchor moments of surprise moments of confusion whether narrative growth is noticed whether the expanded text remains coherent whether a new question emerges ``` ### Paper-test requirement The interaction should be tested without Angular before further broad implementation. If it does not work in plain text, implementation polish should not be expected to rescue it. --- ## 21. Current Working Mode The project is currently operating through: ```text working hypothesis → concrete content → paper test → observed findings → documented decision → narrow implementation slice ``` It is not currently operating through: ```text broad theory → idealised interface → large implementation prompt → expensive iteration ``` This shift is intended to reduce avoidable implementation cost while increasing research rigour. --- ## 22. Product Decision Boundaries ### Proceed when ```text the content is coherent enough to test; the hypothesis and observations are written before testing; the user behaviour can be observed without explaining the theory; the next implementation change can be described visibly and narrowly. ``` ### Pause when ```text the core interaction remains unclear; documents contradict each other; associations have no clear relationship basis; the narrative cannot remain coherent after several inserts; a coding task cannot be demonstrated with a simple before-and-after result. ``` --- ## 23. Current Authoritative Documents The v0.3 direction is defined primarily by: ```text /CLAUDE.md /mvp/Prototype-v0.3-Decision.md /mvp/Product-Vision.md /mvp/Living-Narrative-Canvas-Spec.md /mvp/first-journey-roman-coin.json /research/domains/03-Narrative.md /research/domains/07-Patterns-Across-Disciplines.md ``` When older v0.1 or v0.2 documents conflict with these, the v0.3 documents take priority. --- ## 24. Gate 2 Completion Criteria The product-model consolidation gate is complete when: ```text Product Vision, CLAUDE.md and the v0.3 decision agree; the Roman coin content can be reviewed without opening the app; every active association has a reason, insert and evidence status; the JSON references a real human-readable v0.3 content source; Experience Patterns, Pattern Catalogue, Ontology and Terminology describe one coherent v0.3 model; no active document treats Doorways or Saved Narrative as the core interaction. ``` --- ## 25. Provisional Product Conclusion The current product proposition is: > **Curiosity may grow when a person can see a concrete object’s meaning develop through connected exploration.** The Living Narrative Canvas is a practical attempt to test that proposition. It should not become another mechanism for delivering more information. It should make visible: ```text how details connect why relationships matter how motifs gather significance how themes emerge how distant subjects may share structure how the same object can be seen differently ``` The product succeeds only if the expanding narrative produces richer understanding rather than merely longer text. > **The purpose of the MVP is not to impress. > The purpose is to clarify whether visible, connected meaning can cultivate curiosity.**