Curiosity Rooms

00 - Indexing Guide

2 min read

Indexing Guide

Rules for turning source files from ActivityTracker / April (Active) into Gemma Index notes. Inventory first; deep indexing second.

Goals

  1. Preserve human orientation — how Nitish moved through the discussion (questions, pivots, constraints, what he was trying to do next).
  2. Preserve AI / research answer quality — keep the useful mechanisms, structures, and citations; do not flatten into a generic blurb.
  3. Not generic summary farms — every Index note should remain navigable back to the lived thread or primary artifact.

Labeling: Experiential vs Authority

  • Do not over-label Authority.
  • Prefer Experiential when the material is process, hypothesis, personal workflow, or “this is how I was thinking / trying.”
  • Use Authority only when the note rests on clear evidence, established mechanism, or cited primary research you are standing behind.
  • Medical PDFs are primary records for Nitish; extracted mechanisms may later become Authority, but the raw file is not automatically an Authority essay.

Priority of material types

  1. Mechanism
  2. Lived systems
  3. Learning / productivity / biohacking (with genuine density)
  4. Supporting research / content frameworks
  5. Last or never: JD dumps, OSINT, relationship dumps, thin clippings, empty stubs

See 00 - Priority Triage.md.

Required Index note shape

Each Index note must include sections 1–4 (use the project’s standard section titles for those), then:

## 5. Miscellaneous
 
- Source path: ...
- Capture / session meta: ...
- Related files: ...
- Notes on duplicates / redaction: ...
 
**Priority:** P1 | P2 | P3 | Skip
**Relevance:** ...

Always set Priority and Relevance fields (in frontmatter and/or at the end of section 5).

Capture bundles

For nitish-capture/... folders, index one unit:

  • Primary: chat.txt
  • Attach: INDEX.txt, MESSAGE_MAP.txt, meta.txt
  • Ignore empty sidecars (attachments.txt, events.txt if empty)
  • checksums.txt optional footnote only

Do not create seven separate Index notes for one Grok capture.

PDF handling

  • Prefer unique dated medical reports over mfine_doc* duplicates.
  • HR / salary / eSign / CRED: P3 or Skip for publish; if indexed at all, mark sensitive and non-public.
  • Research Strategy Development.pdf: P2 supporting research.

What not to do

  • Do not invent content for empty folders or 0-byte stubs.
  • Do not deep-index .trash, .obsidian, .space, TaskNotes views, or Excalidraw binary clutter.
  • Do not turn chats into bullet “summary farms” that lose the human path through the problem.
  • Do not queue P3 admin paper ahead of P1 lived-system / mechanism work.

Graph View

Backlinks