Archive: Ballpark (template)

Workflow version: BPT-2026-09-09.02

Last updated: 2026-09-09

Versioning rule: Increment the final two-digit revision for each substantive workflow change. Use a new date when the workflow is revised on a later date. Cosmetic-only edits may be recorded without incrementing the revision.

Purpose

Process a ballpark or location table by connecting team-season thoughts to the ballpark thought and league-season thoughts to the table’s internal references, while validating source URLs and preserving the table’s historical data.

Expected table

The source table normally contains Year, Team, League, record columns, and optionally a source/resource URL column. Preserve all non-link data and formatting unless this workflow explicitly requires a change.

Naming conventions

Team column

• Display text: Team - YEAR.
• Target thought: preferably Team - YEAR, LEAGUECODE when the team belongs to a rookie or complex league.
• Use the existing thought that best matches the historical team-season identity.

League column

• Use the existing exact league-year thought whenever possible.
• Standard name: League Name YEAR, with no hyphen.
• If the source represents a combined or composite league identity, use the existing composite thought exactly; do not split or rename it.

Procedure

1. Read the complete table in the active ballpark/location thought.
2. Extract each populated row’s year, team, league, statistics, and source/resource URL if present.
3. Resolve each team thought:
   • Search for the exact display name first.
   • If appropriate, search for a league-specific form such as Team - YEAR, CODE.
   • Inspect candidates when names are ambiguous; do not guess.
   • Create a thought only when no suitable thought exists and creation is authorized.
4. Ensure every resolved team-season thought is a child of the ballpark thought. Check the existing link first; preserve all other relationships.
5. Resolve each league-year thought:
   • Search for the exact standard or composite thought name.
   • Use an existing matching thought whenever possible.
   • If no suitable thought exists and creation is authorized, create it as a jump thought of the ballpark.
   • Do not make an existing league thought a ballpark child merely because it appears in the table.
6. Generate every new internal thought link with TheBrain’s thought-link URL generator. Never manually construct, guess, edit, or infer a brain:// URL. Preserve existing working internal links exactly.
7. Replace the Team and League cells with internal Markdown links while preserving their display text and all other table content.
8. If the table includes a source/resource URL, inspect the selected team-season thought’s attachments and search the entire brain for the exact URL before attaching it.
9. Attach a valid missing source URL to the selected team-season thought only when it is not already attached elsewhere. Use a descriptive title such as StatsCrew — [Team - YEAR].
10. If the URL is already attached elsewhere:
    • Do not create a duplicate attachment.
    • Verify the owning thought is a plausible source identity.
    • Create or preserve a jump link between the owner and the selected team-season thought.
    • Append a concise explanation to the selected thought’s note identifying the owner and why duplication was avoided.
    • Report the duplicate-source safety catch.
11. If the URL is broken, ghost, misclassified, or attached to an implausible thought, document the anomaly and flag it for review. Do not silently duplicate or reassign it.
12. Remove a source/resource column only after every URL has been attached, intentionally represented elsewhere with a documented exception, or explicitly documented as unresolved. If the source column is absent, report that attachment validation could not be performed from the table.
13. Re-read the updated note and verify every populated row has working Team and League internal links, every team thought is a ballpark child, and every source URL has a documented attachment status.

Graph relationships

• Team-season thoughts: children of the ballpark thought.
• Existing league-year thoughts: linked in the table only; do not add a ballpark child link solely for the table.
• Newly created league-year thoughts: jump-linked to the ballpark.
• Preserve existing parents, children, jumps, and custom ordering.
• Do not re-parent, merge, or delete thoughts merely to make the graph uniform.

Classification and identity safeguards

• Preserve historical names, spellings, composite league identities, and disambiguating suffixes.
• Do not infer league level from a URL directory such as /minorbaseball/; use historical context and page content.
• If several team or league candidates could be correct, document the ambiguity and ask for clarification rather than guessing.
• Existing types and tags should be reused; do not create duplicate types. Apply correction tags only with permission.

Completion checklist

• [ ] All populated rows extracted.
• [ ] Team identities verified; ambiguities flagged.
• [ ] League-year identities verified, including composite identities.
• [ ] Internal links generated with TheBrain’s URL generator.
• [ ] Team-season thoughts linked as ballpark children.
• [ ] Existing relationships and ordering preserved.
• [ ] Source URLs checked on selected thoughts and across the brain when a source column exists.
• [ ] Missing URLs attached when valid and not duplicates.
• [ ] Duplicate URLs documented with owning thought, jump link, and explanation note.
• [ ] Ghost, broken, or misleading URLs documented.
• [ ] Source column removed only after attachment verification or documented exceptions.
• [ ] Updated note re-read and validated.
• [ ] Completion report includes completed items, safety catches, unresolved items, and user action required.

Related workflows

• League Franchise Team Table Workflow — franchise-level league tables and source-URL safeguards.
• League (template) — connects team-season thoughts to league-season thoughts.
• Franchise (template) — organizes a franchise and its season records.
• Location: Template — indexes franchises associated with a location.

Revision history

• BPT-2026-08-24.01 — original workflow.
• BPT-2026-09-09.02 — added cross-brain URL duplicate detection, duplicate-source handling, owning-thought jump links, explanatory notes, source validation, ambiguity safeguards, and completion verification.