Skip to content

DR-008: ChatGPT archive rehoming uses topic-based taxonomy

Status

Accepted — 2026-04-14 · Rick-confirmed

Context

On 2026-03-03, Rick imported 71 business-relevant ChatGPT conversations (out of 200 total) from a ChatGPT data export into the production vault. The import was organized by the old 30-agent taxonomy — conversations were sorted into agent subfolders like AI Revenue OS/, CRO Sales Engine/, Research Assistant/, Code Assistant/, Category & Positioning/, Website Infrastructure/, LinkedIn Distribution/, Offer Architecture/.

The v1.2 migration compressed the roster from 40 agents to 21 (per DR-005). Many of the old agent folders no longer exist as v1.2 agent identities. If we rehomed the 71 ChatGPT conversations using the new agent taxonomy, we'd face:

  1. Ambiguous mapping — AI Revenue OS content would split across revenue.os, cdo, and mining.mind depending on the specific conversation
  2. Taxonomy rot — when agents get added or merged in the future, the research folder structure would need re-migrating
  3. Agent-vs-topic mismatch — the conversations are about topics (ecosystem revenue, partner strategy, brand voice), not about the agents that happen to own them now

Decision

Use a topic-based taxonomy for ChatGPT and other external-chat research captures, not agent-based. Proposed topic folders under /knowledge/research/external-chats/{source}/:

  • ecosystem-revenue-os/ — Revenue OS 2.0 framework research, signal ontology, ERI category
  • partner-channel-strategy/ — CDW, Red Hat, Cisco, VAR intel, partner motivation, swim-lane planning
  • positioning-brand/ — Category design, naming, voice, positioning frameworks
  • tooling-research/ — CRM comparisons, automation tool evaluations, AI platform research
  • website-infra/ — Website build research, SSL, domains, hosting
  • content-distribution/ — LinkedIn, content factory, Substack strategy, brand guidelines
  • offers-advisory/ — Advisory services packaging, program offers
  • code-automation/ — Home Assistant, Google Sheets automation, YAML, Jinja templates
  • _raw-imports/ — untouched original files from the import (fallback for reference)

Agent ownership is recorded in the frontmatter of each file (related_agents: [agent_id, ...]) so Dataview queries can still filter by agent without the folder structure needing to match.

Alternatives considered

Option A — Preserve the original 2026-03-03 agent-based taxonomy

Rejected. Many of the original agent folders no longer exist in v1.2. We'd either need to fabricate non-existent agent folders (confusing) or leave the content in legacy folder names (inconsistent with the 4-bucket vault architecture).

Option B — Remap to v1.2 agent taxonomy (21 agents)

Rejected. Most conversations would be ambiguous (touching multiple v1.2 agent scopes), and the taxonomy would break again the next time the roster changes.

Option C — Topic-based taxonomy

Accepted. Topics are stable across agent reorgs. Frontmatter-based agent association preserves queryability without structural brittleness.

Consequences

What becomes easier: - Stable folder structure across future agent roster changes - Topics match how humans naturally think about research ("I'm looking for partner strategy research" vs. "I'm looking for what CRO.Sales wrote") - Dataview queries work per-agent via frontmatter without needing folder remapping - New external-chat sources (Gemini, Claude web, DeepSeek) can use the same topic taxonomy

What becomes harder: - One-time migration effort to rehome the 71 existing conversations (filed as Task 11751521785 for chief.staff to execute) - Agent ownership requires discipline in frontmatter maintenance (easier to forget than folder placement) - Cross-topic conversations may fit multiple folders (resolved by choosing dominant topic + tagging the others)

Trade-off accepted: Topic-stability + structural durability in exchange for one-time migration work.

Implementation status

  • Decision made 2026-04-14 during wiki architecture discussion
  • Topic taxonomy documented at /Claude/inbox/external-chats/README.md
  • Migration task filed as Task 11751521785 (Monday.com) under the Obsidian Wiki Buildout Epic
  • Execution pending — chief.staff or code.platform will execute once the broader wiki population is complete
  • [[/Claude/inbox/external-chats/README]] — topic taxonomy documentation
  • [[/Claude/archive/claude-chats/]] — source content (71 conversations from 2026-03-03 import)
  • [[capture-to-wiki]] — skill that will use this taxonomy for future captures
  • DR-001 — Obsidian as primary wiki (foundational)

Date: 2026-04-14 · Author: chief.staff · Stakeholders: ceo, chief.staff