🗂️ Evidence & Archive

This page explains what evidence is published in the repository and what intentionally remains local-only.

Published Evidence

The following artifacts are committed and safe to reference publicly:

• ../assets/grok-generated-cat-logo.jpg
• ../telegram-remote-bridge.mjs
• Verification Summary
• Command Highlights
• Telegram Helper
• Archived Raw Session Log

Local-Only Runtime Evidence

These artifacts are intentionally kept out of version control:

• repo-local .grok/
• telegram-pair-code.txt
• telegram-remote-bridge.log
• personal ~/.grok/user-settings.json
• local runtime databases under ~/.grok/

Archive Policy

GROK_COMMANDS_AND_OUTPUTS.md is retained as an archived lab notebook from the original Windows sandbox session.

Important notes:

• it may contain Japanese text
• it may show terminal-dependent encoding artifacts
• it should be treated as historical appendix material, not as the primary onboarding document

For public-facing claims, prefer the curated summaries in this docs/ directory.