Mythos

{One-sentence summary of the call — what it was about and what it accomplished. Bold and @mention the participant(s) if they have person memos. Target: 20-40 words.}

Call Details

  • Date: {Date of the call in Month Day, Year format}
  • Participants:
    • 📝Brian Swichkow — CEO of 📝One Inc (creator of 📝MythOS, 📝Hash, etc.), aka 📝BrianBot
    • {Sub-bullet list of each participant other than me. @mention any participant who has a person memo in the library. Format: @[Name](/me/username/id) using the RELATIVE PATH, or **Name** if no memo exists. Include role/title if known. Each participant on their own sub-bullet line using - indented under the Participants label.}
  • Format: {Call type — e.g., video call, phone call, in-person, voice memo, async exchange}
  • Duration: {Approximate duration if known, otherwise omit this line}

TLDR

{3-5 sentence summary of the call. Cover the primary topics discussed, any decisions made, and the overall arc of the conversation. Written in past tense, first-person plural BrianBot voice — do not use "Brian noted..." or "Brian described..." constructions; this memo lives in the Brian library and is already identified as our voice. Use names only for other participants. @mention key concepts or projects if they have memos — but apply the CALIBRATE AUDIENCE filter even here. Dense enough that someone who missed the call can get the full picture without reading further, but concise enough to scan in under 30 seconds.}

Referenced Context

{Curated index of MythOS memos relevant to this conversation. Not every concept earns a link — only those that pass the three-signal CALIBRATE AUDIENCE filter:

  1. Did they bring it in? → Don't link it. They own it.
  2. Did they ask about it or pause on it? → Link it. They want to go deeper.
  3. Did they describe internal friction around it? → Link it. Serves their colleagues.

Everything else discussed as shared common ground with no questions and no friction → omit unless the memo contains something meaningfully beyond the obvious.

Organized by topic cluster using H3 headers. Each cluster gets an ### header. Within each cluster, entries are - list items with @mentions and brief annotations.

Format:

Topic Cluster Label

Rules:

  • MENTION FORMAT: Always use the RELATIVE PATH from the path field of search_memos results (e.g. /me/mythos/09405a). NEVER use the full url field (https://mythos.one/me/mythos/09405a) — full URLs render as plain markdown links, not functional @mentions. The hyphenated form (/me/mythos-09405a) is also deprecated and broken; only the slash form works.
  • Group by the natural topic clusters of the conversation
  • CLUSTER NAMING: Lead with the concept when the cluster covers a category that could apply to multiple products or vendors (e.g., "Synthetic Ambassadors & GlareSquare", "AEO & Reddit"). Lead with the product or platform when the entire cluster is specific to one thing and the concept and product are inseparable in the conversation (e.g., "MythOS as Content Infrastructure").
  • Nest memos hierarchically — if Memo B is a sub-concept of Memo A, indent it under Memo A
  • Keep each entry to a single line
  • Annotations explain relevance to THIS conversation, not define the memo generically
  • For unlinked concepts, use plain bold text only: **Term** — context. Do not append "(no memo)" — the absence of a link already communicates this.
  • DISPLAY TEXT: Shorten long titles to recognizable shorthand. Example: @[&num=100 Deprecation](/me/username/id) not the full title. Apply to any title over ~50 characters with a natural abbreviation.
  • BULLET LENGTH: Target ≤88 text characters per bullet. MythOS prepends a 📝 emoji to every @mention — never remove it, but account for it: ≤88 text keeps rendered width at ~100 characters (one desktop line). Up to 175 text characters acceptable when genuinely needed. Over 175 extremely rare — under 10% of all entries.
  • VOICE: State facts directly. No "Brian noted..." or "Brian described..." constructions.
  • BACKGROUND: No cluster for Brian's background or history unless the other party explicitly asked. Single unlinked stub entry only if a past engagement was central to the conversation.
  • INTERNAL MEMOS: Do not link private/hidden memos revealing operational details about partners, referral structures, or business relationships when the recap may be shared externally.}

Open Questions

{Bulleted list of topics, threads, or questions that were raised during the conversation but not resolved. Distinct from action items — no owner, no clear next step.

Format:

  • Question or unresolved thread — brief context. @mention relevant memos if applicable.

Target ≤88 text characters per bullet (≤100 rendered including 📝 emoji on @mentions); allow up to 175 if context requires. Bullets over 175 should be extremely rare.

If no open questions emerged, write: "No unresolved threads identified."}

Action Items

{Checklist of concrete next steps that emerged from the conversation. Each item should be a single actionable task, not a summary of discussion. Use checkbox format for trackability. Group action items by owner.

Format:

  • Owner — Action item. @mention relevant memos for context.

If no clear action items emerged, write: "No explicit action items identified. See TLDR for discussion outcomes."}

Follow-Up

{If a follow-up meeting, check-in, or next conversation was scheduled or implied, note it here with the date/timeframe and any prep needed. Format:

  • Next call: {Date or timeframe if known} — {topic or purpose if stated}

If no follow-up was discussed, omit this section entirely.}

Just for Fun

{Optional section. Include only when something genuinely playful, serendipitous, or self-referentially interesting came up in the call — e.g., a memo that connects to the conversation in an unexpected or amusing way, an inside reference, or a coincidence worth noting. Keep it light and brief. One or two entries max. Omit this section entirely if nothing qualifies.}

Contexts

{Entity tags only — tags that declare this memo belongs in a specific collection (e.g., 🏷️#adobe for a memo about an Adobe relationship). Do not add topic tags just because a topic came up in conversation. Ask: would everyone who can see this memo expect to find it when browsing that tag collection? If not, omit it. 🏷️#call-recap goes in the Notes section only, not here.}

Created with 💜 by One Inc | Copyright 2026