Storage programs

.beads/.gitignore

@@ -0,0 +1,29 @@
+# SQLite databases
+*.db
+*.db?*
+*.db-journal
+*.db-wal
+*.db-shm
+
+# Daemon runtime files
+daemon.lock
+daemon.log
+daemon.pid
+bd.sock
+
+# Legacy database files
+db.sqlite
+bd.db
+
+# Merge artifacts (temporary files from 3-way merge)
+beads.base.jsonl
+beads.base.meta.json
+beads.left.jsonl
+beads.left.meta.json
+beads.right.jsonl
+beads.right.meta.json
+
+# Keep JSONL exports and config (source of truth for git)
+!issues.jsonl
+!metadata.json
+!config.json

.beads/README.md

@@ -0,0 +1,81 @@
+# Beads - AI-Native Issue Tracking
+
+Welcome to Beads! This repository uses **Beads** for issue tracking - a modern, AI-native tool designed to live directly in your codebase alongside your code.
+
+## What is Beads?
+
+Beads is issue tracking that lives in your repo, making it perfect for AI coding agents and developers who want their issues close to their code. No web UI required - everything works through the CLI and integrates seamlessly with git.
+
+**Learn more:** [github.com/steveyegge/beads](https://github.com/steveyegge/beads)
+
+## Quick Start
+
+### Essential Commands
+
+```bash
+# Create new issues
+bd create "Add user authentication"
+
+# View all issues
+bd list
+
+# View issue details
+bd show <issue-id>
+
+# Update issue status
+bd update <issue-id> --status in_progress
+bd update <issue-id> --status done
+
+# Sync with git remote
+bd sync
+```
+
+### Working with Issues
+
+Issues in Beads are:
+- **Git-native**: Stored in `.beads/issues.jsonl` and synced like code
+- **AI-friendly**: CLI-first design works perfectly with AI coding agents
+- **Branch-aware**: Issues can follow your branch workflow
+- **Always in sync**: Auto-syncs with your commits
+
+## Why Beads?
+
+✨ **AI-Native Design**
+- Built specifically for AI-assisted development workflows
+- CLI-first interface works seamlessly with AI coding agents
+- No context switching to web UIs
+
+🚀 **Developer Focused**
+- Issues live in your repo, right next to your code
+- Works offline, syncs when you push
+- Fast, lightweight, and stays out of your way
+
+🔧 **Git Integration**
+- Automatic sync with git commits
+- Branch-aware issue tracking
+- Intelligent JSONL merge resolution
+
+## Get Started with Beads
+
+Try Beads in your own projects:
+
+```bash
+# Install Beads
+curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
+
+# Initialize in your repo
+bd init
+
+# Create your first issue
+bd create "Try out Beads"
+```
+
+## Learn More
+
+- **Documentation**: [github.com/steveyegge/beads/docs](https://github.com/steveyegge/beads/tree/main/docs)
+- **Quick Start Guide**: Run `bd quickstart`
+- **Examples**: [github.com/steveyegge/beads/examples](https://github.com/steveyegge/beads/tree/main/examples)
+
+---
+
+*Beads: Issue tracking that moves at the speed of thought* ⚡

.beads/config.yaml

@@ -0,0 +1,63 @@
+# Beads Configuration File
+# This file configures default behavior for all bd commands in this repository
+# All settings can also be set via environment variables (BD_* prefix)
+# or overridden with command-line flags
+
+# Issue prefix for this repository (used by bd init)
+# If not set, bd init will auto-detect from directory name
+# Example: issue-prefix: "myproject" creates issues like "myproject-1", "myproject-2", etc.
+# issue-prefix: ""
+
+# Use no-db mode: load from JSONL, no SQLite, write back after each command
+# When true, bd will use .beads/issues.jsonl as the source of truth
+# instead of SQLite database
+# no-db: false
+
+# Disable daemon for RPC communication (forces direct database access)
+# no-daemon: false
+
+# Disable auto-flush of database to JSONL after mutations
+# no-auto-flush: false
+
+# Disable auto-import from JSONL when it's newer than database
+# no-auto-import: false
+
+# Enable JSON output by default
+# json: false
+
+# Default actor for audit trails (overridden by BD_ACTOR or --actor)
+# actor: ""
+
+# Path to database (overridden by BEADS_DB or --db)
+# db: ""
+
+# Auto-start daemon if not running (can also use BEADS_AUTO_START_DAEMON)
+# auto-start-daemon: true
+
+# Debounce interval for auto-flush (can also use BEADS_FLUSH_DEBOUNCE)
+# flush-debounce: "5s"
+
+# Git branch for beads commits (bd sync will commit to this branch)
+# IMPORTANT: Set this for team projects so all clones use the same sync branch.
+# This setting persists across clones (unlike database config which is gitignored).
+# Can also use BEADS_SYNC_BRANCH env var for local override.
+# If not set, bd sync will require you to run 'bd config set sync.branch <branch>'.
+# sync-branch: "beads-sync"
+
+# Multi-repo configuration (experimental - bd-307)
+# Allows hydrating from multiple repositories and routing writes to the correct JSONL
+# repos:
+#   primary: "."  # Primary repo (where this database lives)
+#   additional:   # Additional repos to hydrate from (read-only)
+#     - ~/beads-planning  # Personal planning repo
+#     - ~/work-planning   # Work planning repo
+
+# Integration settings (access with 'bd config get/set')
+# These are stored in the database, not in this file:
+# - jira.url
+# - jira.project
+# - linear.url
+# - linear.api-key
+# - github.org
+# - github.repo
+sync-branch: beads-sync

.beads/metadata.json

@@ -0,0 +1,4 @@
+{
+  "database": "beads.db",
+  "jsonl_export": "issues.jsonl"
+}

.gitattributes

@@ -0,0 +1,3 @@
+
+# Use bd merge for beads JSONL files
+.beads/issues.jsonl merge=beads

.gitignore

@@ -153,3 +153,17 @@ claudedocs
 docs/storage_features
 temp
 STORAGE_PROGRAMS_SPEC.md
+omniprotocol_fixtures_scripts
+captraf.sh
+http-capture-1762006580.pcap
+http-capture-1762008909.pcap
+http-traffic.json
+prop_agent
+attestation_20251204_125424.txt
+ZK_CEREMONY_GUIDE.md
+ZK_CEREMONY_GIT_WORKFLOW.md
+REVIEWER_QUESTIONS_ANSWERED.md
+PR_REVIEW_RAW.md
+PR_REVIEW_COMPREHENSIVE.md
+CEREMONY_COORDINATION.md
+BUGS_AND_SECURITY_REPORT.md

.serena/memories/_index.md

@@ -0,0 +1,148 @@
+# Serena Memory Index - Demos Network Node
+
+## Quick Navigation Guide
+
+This index helps Serena efficiently locate and load the most relevant memories for any task. Memories are organized by domain and purpose.
+
+## Core Project Knowledge (Always Load First)
+
+### Foundation
+- **`project_core`** - Project identity, architecture, tech stack, naming conventions
+- **`development_guidelines`** - Code style, workflow, quality standards, best practices
+
+### Essential References
+- **`suggested_commands`** - Development commands and utilities
+- **`task_completion_guidelines`** - DEPRECATED (merged into development_guidelines)
+
+## Feature Implementation Memories
+
+### Storage Programs (Complete)
+- **`storage_programs`** - Complete implementation reference, architecture patterns, usage
+  - Covers: Two-phase validation, access control, size limits, data flow
+  - Commits: b0b062f1, 1bbed306, 7a5062f1, 28412a53
+  - Status: Production ready ✅
+
+### Telegram Identity System (Complete)
+- **`telegram_identity`** - Dual-signature verification, bot authorization, points system
+  - Covers: Demos address=public key pattern, group membership points
+  - SDK: v2.4.18+
+  - Status: Production ready ✅
+
+## Quality & Review Memories
+
+### Code Reviews
+- **`pr_review_tg_identities_complete`** - PR #468 complete analysis and resolutions
+  - All CRITICAL and HIGH priority issues resolved
+  - Security decisions documented
+  - Lessons learned from automated reviews
+
+### Session Checkpoints (Keep Most Recent)
+- **`session_storage_review_2025_10_11`** - Storage Programs review session
+  - Automated review analysis (GLM, QWEN)
+  - Bug verification and false positive identification
+  - Production readiness assessment
+
+- **`session_final_2025_01_31`** - Telegram identities final checkpoint
+  - All high priority issues complete
+  - Security analysis and decisions
+  - Implementation milestones
+
+## Deprecated Memories (Delete After Verification)
+
+### Superseded by Consolidated Memories
+- `project_purpose` → Merged into `project_core`
+- `tech_stack` → Merged into `project_core`
+- `codebase_structure` → Merged into `project_core`
+- `code_style_conventions` → Merged into `development_guidelines`
+- `development_patterns` → Merged into `development_guidelines`
+- `project_context_consolidated` → Replaced by `project_core`
+
+### Storage Programs (Consolidated)
+- `storage_programs_complete` → Merged into `storage_programs`
+- `storage_programs_specification` → Merged into `storage_programs`
+- `storage_programs_architectural_patterns` → Merged into `storage_programs`
+- `storage_programs_access_control_patterns` → Merged into `storage_programs`
+- `storage_programs_implementation_phases` → Merged into `storage_programs`
+- `storage_programs_phases_commits_guide` → Merged into `storage_programs`
+- `storage_programs_phase2_complete` → Merged into `storage_programs`
+- `storage_programs_phase3_complete` → Merged into `storage_programs`
+- `storage_programs_phase4_complete` → Merged into `storage_programs`
+- `storage_programs_review_fixes_complete` → Merged into `storage_programs`
+- `storage_programs_review_lessons_learned` → Merged into `storage_programs`
+
+### Telegram Identity (Consolidated)
+- `telegram_identity_system_complete` → Merged into `telegram_identity`
+- `project_patterns_telegram_identity_system` → Merged into `telegram_identity`
+- `session_2025_10_10_telegram_group_membership` → Merged into `telegram_identity`
+- `telegram_points_implementation_decision` → Merged into `telegram_identity`
+- `telegram_points_conditional_requirement` → Merged into `telegram_identity`
+
+### PR Review (Consolidated)
+- `pr_review_point_system_fixes_completed` → Merged into `pr_review_tg_identities_complete`
+- `pr_review_analysis_complete` → Merged into `pr_review_tg_identities_complete`
+- `pr_review_corrected_analysis` → Merged into `pr_review_tg_identities_complete`
+- `pr_review_all_high_priority_completed` → Merged into `pr_review_tg_identities_complete`
+- `pr_review_import_fix_completed` → Merged into `pr_review_tg_identities_complete`
+- `pr_review_json_canonicalization_dismissed` → Merged into `pr_review_tg_identities_complete`
+- `genesis_caching_security_dismissed` → Merged into `pr_review_tg_identities_complete`
+- `data_structure_robustness_completed` → Merged into `pr_review_tg_identities_complete`
+- `input_validation_improvements_completed` → Merged into `pr_review_tg_identities_complete`
+
+### Session Checkpoints (Superseded)
+- `checkpoint_2025_10_11_session_complete` → Keep as `session_storage_review_2025_10_11`
+- `session_2025_10_11_storage_branch_review` → Merged into `session_storage_review_2025_10_11`
+- `session_2025-10-11_storage_programs_review_fixes` → Merged into `session_storage_review_2025_10_11`
+- `session_2025_10_11_storage_programs_fixes` → Merged into `session_storage_review_2025_10_11`
+- `session_checkpoint_2025_01_31` → Keep as `session_final_2025_01_31`
+- `session_final_checkpoint_2025_01_31` → Merged into `session_final_2025_01_31`
+
+## Memory Loading Strategy
+
+### For New Tasks
+1. Load `project_core` and `development_guidelines` first
+2. Identify task domain and load relevant feature memory
+3. Load session checkpoints only if resuming interrupted work
+
+### For Feature Development
+- **Storage Programs**: Load `storage_programs`
+- **Telegram Identity**: Load `telegram_identity`
+- **New Feature**: Start with core memories only
+
+### For Code Review
+- Load `pr_review_tg_identities_complete` for patterns and lessons
+- Load feature-specific memory for context
+
+### For Bug Fixes
+- Load relevant feature memory
+- Load session checkpoints if issue is known
+- Load core memories for context
+
+## Optimization Results
+
+### Before Consolidation
+- **Total Memories**: 40
+- **Estimated Size**: ~150KB
+- **Redundancy**: High (70%+ duplicate information)
+
+### After Consolidation
+- **Total Memories**: 10 (8 consolidated + 2 reference)
+- **Estimated Size**: ~50KB
+- **Redundancy**: Minimal (atomic, non-overlapping domains)
+- **Space Savings**: 67% fewer memories, 66% size reduction
+
+## Maintenance Guidelines
+
+### When to Add New Memories
+- Major feature completion (add feature-specific memory)
+- Significant session milestones (add checkpoint)
+- Important lessons learned (add to relevant feature memory)
+
+### When to Update Memories
+- Feature enhancement (update feature memory)
+- Pattern changes (update core memories)
+- Guideline updates (update development_guidelines)
+
+### When to Delete Memories
+- After successful consolidation verification
+- When superseded by updated memory
+- After confirming no unique information loss