My Wedding Invitations Became an Experiment in AI Memory
My Wedding Invitations Became an Experiment in AI Memory I ran into a very annoying issue while trying to build a website for my wedding invitations. I needed the LLM to remember anything interesting that I told it or it discovered during exploration. Then when encountering ambiguiting it should recover those pieces of knowledge on its own.
- ▪My Wedding Invitations Became an Experiment in AI Memory I ran into a very annoying issue while trying to build a website for my wedding invitations.
- ▪I needed the LLM to remember anything interesting that I told it or it discovered during exploration.
- ▪Then when encountering ambiguiting it should recover those pieces of knowledge on its own.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,191 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Hacker News (AI / LLM) |
| Canonical URL | https://pureooze.com/blog/posts/2026-09-22-my-wedding-invitations-became-an-experiment-in-ai-memory/ |
| Publication time | Wed, 23 Sep 2026 21:28:46 +0000 |
| Retrieval time | 2026-09-23T21:39:35.306Z |
| Last seen | 2026-09-23T21:39:35.306Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | yhvr4Imgmkgp · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
My Wedding Invitations Became an Experiment in AI Memory I ran into a very annoying issue while trying to build a website for my wedding invitations. Every time I sent a prompt to my LLM it would do one of two things: Ask me lots of clarifying questions (annoying) Spend lots of time and tokens searching the project (annoying and expensive!) So I would either end up flustered at the amount of questions I was suddenly bombarded with, or run out of tokens before the agent even started the task I wanted to do. I needed the LLM to remember anything interesting that I told it or it discovered during exploration. Then when encountering ambiguiting it should recover those pieces of knowledge on its own. That is what led me to build a knowledge graph extension for Pi.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (AI / LLM).
Discussion
0 commentsMore from Hacker News (AI / LLM)
