Case: Firey v. Firey
Jurisdiction: Montgomery County, PA
Status: Litigation Mode
Single, authoritative source of truth for pro se legal case management. Designed to survive device failure and counsel changes.
For AI Agents: Do not hallucinate. Use only files present here.
- Linux/WSL environment
- Bash shell
- Internet connection (for initial setup)
# Clone repository
git clone [email protected]:cyserman/Prose_Truth_Repo.git
cd Prose_Truth_Repo
# Make restore script executable
chmod +x restore_christine.sh
# Run restoration (installs Node.js, npm dependencies, launches dev server)
./restore_christine.shThe React app will launch at http://localhost:5173/
cd 09_APP/prose-legal-db-app
npm install
npm run dev# Start reflexive intake agent
python 09_APP/agents/reflexive_intake_agent.py
# Or use the orchestrator
python 09_APP/agents/orchestrator.py00_ANCHORS/ - Constitutional documents and strategic anchors
02_TIMELINES/ - CSV timeline data (evidence spine)
03_EXHIBITS/ - Finalized evidence files (categorized)
04_COMMUNICATIONS/ - Call logs, SMS, app blocks
05_COURT_FILINGS/ - Drafts, filed documents, orders
06_SCANS/ - Input funnel for raw documents
07_LEGAL_RESEARCH/ - Case law and statutes
08_TASKS_AND_LOGS/ - Task tracking and operation logs
09_APP/ - React application tooling
├── prose-legal-db-app/ - Main React application
├── CaseTimeline/ - Mobile timeline app (integration pending)
└── chromebook-toolbox/ - Development toolbox (integration pending)
- USER_GUIDE.md - Complete user instruction manual with step-by-step guides
- FEATURES.md - Comprehensive feature list and capabilities
- INTEGRATION_GUIDE.md - Integration instructions for CaseTimeline Mobile, Chromebook Toolbox v2, and CSV Timeline Data
- README.md - This file (technical setup and overview)
- CSV-based timeline management
- Exhibit linkage system
- Neutralization of emotional language
- Print-to-PDF court-ready output
- Swimlane timeline views with customizable lane profiles
- Smart Sticky Notes - Context-aware annotations
- Categorized exhibit system (CL, FIN, PKT, VEH, etc.)
- OCR processing pipeline (standalone + integrated)
- Index generation
- Reflexive intake agent with logic checks
- Floating note console for quick annotations
- Voice recording for evidence capture
- Strategic analysis via Gemini API
- Automated summary generation
- Gap analysis and consistency checking
- Contradiction detector for cross-examination prep
- Motion/Affidavit builder for document generation
- Neutralization of emotional event descriptions
- Motion Builder - Generate court documents from timeline
- Deadline Tracker - Never miss a court date
- Contradiction Detector - Find inconsistencies automatically
- Smart Sticky Notes - Context-aware floating annotations
- All data remains local (no cloud sync)
- Sensitive exhibits and scans ignored via
.gitignore - Secrets scanning and pre-commit hooks
- Accessibility compliance (WCAG 2.1 AA)
Purpose: One-command restoration and dev server launch
What it does:
- Updates system packages (apt)
- Installs Node.js 20 LTS (if needed)
- Locates React app directory
- Runs
npm install - Launches dev server
Usage:
# Always start with dry-run
./restore_christine.sh --dry-run
# Run with automatic backups
./restore_christine.sh --backup-dir ./backups/manual-$(date +%Y%m%d)
# Run without confirmations (use with caution)
./restore_christine.sh --yes
# Show help
./restore_christine.sh --helpSafety Features:
- ✅
--dry-runmode (preview changes) - ✅ Automatic backups before destructive operations
- ✅ Comprehensive logging
- ✅ Preflight checks (validates environment)
- ✅ Confirmation prompts (unless
--yes) - ✅ Auto-detects repository root
- ✅ Error handling with exit codes
Safety Notes:
- Requires
sudofor apt operations - Always run
--dry-runfirst - Backups created automatically in
backups/directory - Logs saved to
logs/directory - Review script before first run
Interpreting Logs:
- Logs are stored in
logs/restore-YYYYMMDD-HHMMSS.log - Look for
[DRY RUN]markers to identify preview-only operations [CMD]entries show actual commands executed- Check for
✅success markers or❌error markers - Preflight check results are logged at the start
Artifacts Storage:
- Backups:
backups/YYYYMMDD-HHMMSS/(package.json, package-lock.json, etc.) - Logs:
logs/restore-YYYYMMDD-HHMMSS.log - CI Artifacts: GitHub Actions uploads logs and backups as workflow artifacts
- Test Results: Bats test output in CI logs
Rollback / Remediation Steps:
-
If script fails mid-execution:
- Check logs:
tail -50 logs/restore-*.log - Restore from backup:
cp backups/LATEST/package.json 09_APP/prose-legal-db-app/ - Manual recovery:
cd 09_APP/prose-legal-db-app && npm install
- Check logs:
-
If data is lost:
- Check localStorage exports (if exported)
- Check Git history:
git log --all --full-history -- "*.csv" - Restore from backups directory
-
If application won't start:
- Clear node_modules:
rm -rf node_modules && npm install - Check port availability:
lsof -i :5173 - Review dev server logs
- Clear node_modules:
See Also:
- docs/RUNBOOK.md - Detailed recovery procedures and operational guide
- docs/METRICS.md - Metrics tracking guide
- SECURITY.md - Security policies and secrets handling
- RELEASES.md - Release procedures and versioning
- CHANGELOG.md - Change history
When working with this repository:
- Read 00_ANCHORS first - Understand case context and constraints
- Neutralize emotional input - Convert to court-ready language
- Identify manufactured imbalance - Core legal theory of the case
- Preserve exhibit codes - Maintain evidence linkage
- Flag inconsistencies - Timeline gaps, date conflicts
- Ingest: Drop raw files in
06_SCANS/INBOX/ - Process: Use OCR tools or React app to tag and index
- Timeline: Add events to timeline CSVs with exhibit links
- Archive: Move processed files to
03_EXHIBITS/ - Generate: Create court-ready summaries and motions
MIT License - See LICENSE file
Report security vulnerabilities via GitHub security advisories.
See SECURITY.md for details.
GitHub: https://github.com/cyserman/Prose_Truth_Repo
Primary Branch: main