Start with a Source Rune, derive a clearer version, and keep it reusable inside Places and your wider memory space. Rune AI is cards first, not chat first.
Land Friday night. Keep Saturday slow. Save one quiet cafe first, then Arashiyama if the weather stays clear.
Day 1: quiet morning coffee, then a relaxed west-side route. Day 2: keep the plan walkable and leave a short buffer before dinner.
Quiet enough for first-pass planning and easy to revisit because the spot and the note stay together.
Rune AI does not start with chat. It starts with durable cards. A Rune can hold raw truth, AI-shaped writing, or personal memory you want to keep searchable and reusable.
Source keeps the facts. Derived keeps the crafted version. Place gives memory a spatial anchor.
Maybe start west side after coffee. Keep the route light, save one bamboo grove slot, and do not overbook the evening. Need a backup if rain makes the walk less appealing.
Enough context to recognize the card without opening a full editor.
Users should know immediately whether they are looking at truth, transformation, or place memory.
Tags and compact metadata make the next action obvious without bloating the card.
Source keeps the original note. Derived makes it easier to use. Place keeps a real-world anchor. Profile shapes output without replacing facts.
Three possible coffee stops near Kyoto Station. Prioritize quiet seating and places that feel easy to revisit on foot.
Best fit for slow mornings: Kurasu for planning, Weekenders for faster coffee, and one fallback stop if the first choice is crowded.
A saved destination with enough context to remember timing and fallback options if the weather turns.
Prefers quiet cafes, slow mornings, and walkable plans. Good output should stay calm, practical, and easy to scan.
Users only need one loop to start: save truth, derive a clearer version, organize it, then reuse it later.
Paste rough notes, save a clipped article, or create a reminder. The first card should feel low-friction and factual.
Use AI actions like summary, polish, extract, or itinerary to make the saved material easier to use without overwriting the source.
Save the memorable stops, attach notes to them, and give the plan a spatial structure that is easier to recall later.
Bring the cards back into chat, planning, or later edits. The value comes from durable cards, not one-off generation.
Place deserves its own section because it is concrete, memorable, and easier to understand than abstract system language.
Save the spot, keep one short note, and make it easy to reuse later. A Place card becomes more than a pin because it keeps the memory, reason, and follow-up note together.
Saved as a slower afternoon route, with enough context to remember timing and fallback options if the weather turns.
Small, practical memory card: where to end the day, why it fits the plan, and how to keep it easy to revisit.
Each use case starts from a card, moves through transformation, and ends in something reusable.
Capture rough notes, turn them into a plan, and keep the memorable stops visible.
Keep a place card for the spot itself, plus short notes about why it mattered or how to return to it later.
Start from captured material, extract the useful parts, then keep the shorter version ready for later retrieval or chat.
The first step should feel obvious. Save one Source Rune if you want to capture truth. Start with a Place if location is the easier entry. Both routes continue the same card-based system.