AbstractPhil's picture
card: per-boot filename accuracy
20bafe5 verified
|
Raw
History Blame Contribute Delete
1.89 kB
metadata
license: mit
language:
  - en
tags:
  - chat-logs
  - research
  - aleph
  - byte-level
  - human-model-interaction
pretty_name: AlephLLM chat history (public research log)

alephllm-chat-history — public research log

Conversation and completion logs from the Beatrix chat space, collected to study how people interact with an in-training byte-level model and how her behavior evolves across checkpoints.

Storage methodology (full disclosure)

  • What is stored: prompts, chat messages, the model's outputs, sampling parameters (temperature, top-p, max bytes, KV-cache flag), a UTC timestamp, the craft name and checkpoint step that produced each reply.
  • Session tagging: an anonymous per-visit tag (sha256 of the browser session's random id, truncated to 16 hex chars) groups turns from one visit. It is not linked to any account or identity.
  • Completion flag: interrupted or abandoned generations are logged too, marked "completed": false with whatever partial output existed.
  • What is NOT collected: no usernames, no accounts, no IP addresses, no device or browser fingerprints, no cookies beyond the session itself.
  • Format & location: JSON lines under data/, one file per UTC day per space boot (sessions-YYYY-MM-DD-<boot>.jsonl), committed in batches every few minutes by the space.
  • Visibility: this repository is public. Users are warned in the space, above the input box, before typing. If you typed something here you need removed, open a discussion on this repo.

Why public

The AlephLLM program keeps its entire measurement record public — training runs, instruments, failures, and retractions included. The interaction log is part of that record: it documents what an early-stage aleph model actually says to real people at each stage of training.