Reflect and write daily
Use Ten Year Journal, also branded A Decade Never to Be Forgotten at adntbf.com, to connect your AI to the same private account you use on the website. New users choose Sign Up during the website connection flow, approve journal permissions on the website, then return to your AI; existing users choose Log in.
Example path →
https://adntbf.com/mcpUse journal data only for the account represented by the OAuth access token. A direct answer to a specific actual prompt returned by the journal tools and presented with a clear date and year authorizes a new entry. Save its exact response immediately, with no probing or extra confirmation. Keep the exchange brief by default: a one-word answer or one or two sentences can be a complete journal response. Reply briefly without probing, padding, rewriting, or automatic follow-up coaching. If the user has not already expressed a length preference, offer it at most once per conversation near the first actual prompt, alongside that prompt: "Keep these quick, or would you prefer longer reflections?" Do not add a round trip or ask after the user has answered a reflection. When replying to that length choice or clearly giving length guidance, a response consisting only of "short," "long," or "keep it quick" is a preference, not a reflection; acknowledge it, continue to the actual prompt, and never save the preference. Do not exclude those words when they clearly answer the actual prompt. If a reply could answer both the length choice and the journal prompt, ask one brief clarification without writing; do not assume it is a preference and discard a possible journal answer. Remember any length preference only within the current conversation; do not create or promise a stored preference. Longer reflections are welcome when requested but never required, and the actual returned prompt wording must remain exact. Do not auto-save drafts, questions, standalone reflections, or unprompted text. An explicit request to save exact content for a clear target is also authorization. A clearly bounded catch-up batch is equally authorized. Save each exact answer without confirmation or probing between answers. Present the next requested prompt as needed. For catch-up, consider only the seven calendar dates before current_date, oldest first, excluding today and skipping existing entries. Fetch each actual prompt and its history, map month/day onto leap-year 2000 for normalized day_of_year, and save under that date's own year, including across December/January. Update only after the user explicitly asks to change an entry and you have read that entry. Before saving a current daily response, use available activity to evaluate a lapse without delaying the save. If it shows a verified lapse, offer a week of prompts once after a successful save instead of the signoff. Otherwise, after a successful standalone create or update, or the final successful catch-up save, reply exactly "I've logged that to your journal. Let's check in tomorrow for the next prompt." Do not give that signoff after a failed write or between catch-up answers. Do not promise reminders or scheduled prompts. returns current_date and last_journal_activity_on in the account timezone. A lapse is verified only when last_journal_activity_on is present and at least 7 calendar days before current_date. Null means no prior entries, not verified inactivity.
1 in the ChatGPT listing