Franchise All-Time Leaders Template

Franchise All-Time Leaders — Reusable Template

Purpose

Use this template with any franchise’s All-Time Leaders thought to organize player thoughts and accomplishment/category thoughts from one or more statistical leader tables.

Inputs

• Target thought: The franchise’s All-Time Leaders thought.
• Table heading(s): One or more headings in the target thought’s notes, such as Hits Leaders, Home Run Leaders, Doubles Leaders, Triples Leaders, RBI Leaders, Wins Leaders, Shutout Leaders, or Strikeout Leaders.
• Player column: The first column of each selected table, normally labeled Player.
• Source: Each player row contains a StatsCrew.com player URL.

Target Structure

• The target franchise All-Time Leaders thought is the hub.
• Each player thought is a jump-link to the target thought, not a child of it.
• Each category/accomplishment thought is a child of the target thought.
• Each player appearing in a category is a parent of that category thought. This records the accomplishment under the player’s name.
• A category thought therefore has two kinds of parents:
  • The target franchise All-Time Leaders thought.
  • Every player who appears in that category.
• Each category thought also receives a jump-link to every other category thought in the same target franchise All-Time Leaders group. These category-to-category jumps create a navigable sequence for readers moving among leaderboards.
• Do not create a separate player thought for each category. Reuse the same player thought across all categories and preserve one jump-link to the target.

Category Notes

• Keep a focused note on each category thought containing the category’s statistical table.
• The category table should use internal brain:// links to the player thoughts so readers can navigate directly to the players.
• Do not repeat the StatsCrew.com external URLs in category notes. The external source URL belongs on the player thought as an attachment and/or in the target thought’s source-oriented table.
• Preserve existing working internal brain:// links exactly. For new internal links, use the exact URL returned by TheBrain’s thought-link URL generator; never manually construct one.
• Treat the category note as a reader-oriented page: after the table, leave room for historical commentary, observations, comparisons, records, and other color.
• Do not overwrite or replace commentary when refreshing a table unless specifically requested. Update only the statistical table portion when necessary.
• The target thought’s note remains the consolidated, source-oriented dataset and may retain the complete StatsCrew.com player URLs.

Procedure

1. Open and read the notes of the target franchise All-Time Leaders thought.
2. Locate each requested table by its heading. Match headings carefully; use the exact table requested by the user.
3. For every selected table:
   • Extract the displayed category heading.
   • Extract every player’s displayed name.
   • Extract the complete StatsCrew.com source URL from each player link.
4. Locate the category thought under the target:
   • Reuse the existing category thought if it already exists.
   • Otherwise create a category thought using the short statistic name, such as Hits Leaders, Strikeout Leaders, or Wins Leaders, as a child of the target thought.
   • Do not add the franchise name and All-Time Leaders to the category name when the parent already supplies that context. Existing names using a comma and full target context may be retained when they provide useful clarification.
5. Create or refresh the category note:
   • Include the focused table.
   • Link player names to their existing internal thought links.
   • Do not add or duplicate external StatsCrew URLs in the category note.
   • Preserve any existing commentary and color comments.
6. Connect the category thoughts:
   • For every pair of category thoughts in the target group, create a jump-link unless that jump-link already exists.
   • Do not replace the category’s child link to the target or its parent links to players.
   • If the user requests a particular reading order, create or preserve jumps in that order; otherwise connect all categories to one another.
7. For every player row:
   • Search the brain for an existing thought matching the player’s name.
   • Search again using distinctive parts of the name, alternate punctuation/diacritics, and any existing suffix such as a position, when needed.
8. If a matching player thought exists:
   • Link the player thought as a jump to the target franchise All-Time Leaders thought.
   • Link the category thought as a child of that player thought, making the category an accomplishment under the player.
   • Attach the extracted StatsCrew.com URL to that existing player thought, unless the same URL is already attached.
9. If no matching player thought exists after the additional searches:
   • Create a new player thought using the displayed name, as a normal thought.
   • Link the new player thought as a jump to the target franchise All-Time Leaders thought.
   • Link the category thought as a child of the new player thought.
   • Attach the extracted StatsCrew.com URL to the new player thought.
10. If the category thought already has the player as a parent, leave the relationship unchanged. If the player is already jump-linked to the target, do not create a duplicate link.
11. Do not create duplicate player or category thoughts when a reasonable existing match is found. Do not alter the target statistical tables unless specifically requested.
12. If a row has no valid player URL or the table cannot be read, report it for review rather than guessing.

Types and Tags

• Keep player thoughts as Normal thoughts unless an existing player classification requires otherwise.
• Use the target’s existing leader type, such as Franchise Leaders, according to the brain’s established taxonomy.
• Do not assign leader types to player thoughts.
• Tags may be used later for broad, cross-cutting filters, but do not create redundant player-specific tags as part of this workflow unless explicitly requested.
• Keep labels available for the established team descriptive/class-level information; do not use labels as the primary leader filter.

Handling Multiple Tables

• Process every table explicitly requested by the user.
• Deduplicate work by player and source URL: a player appearing in several tables receives one player thought, one jump-link to the target, and one source attachment, while receiving parent links from each applicable category thought.
• If the same player has different StatsCrew URLs, preserve and attach each distinct source URL, but verify the player identity before doing so.

Completion Report

Report:

• Target thought processed.
• Table headings processed.
• Category thoughts reused or created.
• Category notes created or refreshed.
• Category-to-category jump-links created or already present.
• Existing player thoughts linked as jumps.
• New player thoughts created.
• Category-parent accomplishment links created.
• External URLs attached to players or already present.
• Rows skipped or ambiguous, with the reason.

Do not claim a table was processed unless its notes were successfully read.

Internal brain-link rule (global)

• Preserve existing working internal brain:// links exactly.
• Never manually construct, guess, edit, or infer a brain:// URL.
• For new internal links, call TheBrain’s thought-link URL generator for the exact thought and copy the returned URL exactly.
• If generation fails, leave the item plain text and report it; do not substitute another format.