Add invention overview for Sapphire Sentinel

Introduced an overview of the Sapphire Sentinel invention, detailing its problem statement, solution, core components, key differentiators, intended use cases, and future expansion plans.

Author: Huffle89

docs/invention.md

@@ -0,0 +1,164 @@
+# Sapphire Sentinel — Invention Overview
+
+## Author
+Christopher Lagasse  
+Huffle’s IT Services LLC
+
+---
+
+## Problem Statement
+
+Modern terminal workflows rely on fragmented history mechanisms (e.g., bash history) that lack context, structure, and interpretability.
+
+Users are unable to:
+- understand *why* actions were taken
+- reconstruct workflows after the fact
+- correlate commands, errors, and outcomes
+- retain meaningful knowledge from prior sessions
+
+This results in:
+- lost productivity
+- repeated troubleshooting
+- poor auditability
+- weak knowledge retention
+
+---
+
+## Solution Overview
+
+Sapphire Sentinel is a terminal session intelligence system that captures, structures, and reconstructs command-line activity into human-readable narratives.
+
+Rather than logging raw commands alone, Sentinel:
+- groups activity into sessions
+- attaches contextual meaning (project, ticket, label)
+- classifies signals (command, error, note)
+- reconstructs sessions into readable “stories”
+- generates analytical summaries across time
+
+---
+
+## Core System Components
+
+### 1. Session Model
+
+Each terminal interaction is grouped into a structured session with:
+
+- session_id
+- session_mode (development, troubleshooting, etc.)
+- context_type (project, ticket, label, none)
+- context_value
+- start_time / end_time
+- duration
+
+Sessions are the foundational unit of understanding.
+
+---
+
+### 2. Signal Classification System
+
+All captured activity is normalized into signal types:
+
+- command
+- error
+- note
+
+Each signal is logged in a structured format:
+
+timestamp | mode | action | target | status | details
+
+This enables downstream processing and analytics.
+
+---
+
+### 3. Context System
+
+Sentinel attaches meaning to work through flexible context types:
+
+- project-based work
+- ticket-based work
+- labeled sessions
+- unstructured sessions
+
+Context allows grouping, filtering, and narrative reconstruction.
+
+---
+
+### 4. Story Engine
+
+The Story Engine converts structured session data into readable narratives.
+
+Example output:
+
+> “During this session, the user performed system updates, encountered package conflicts, and resolved them through dependency correction.”
+
+This transforms raw logs into human-understandable explanations.
+
+---
+
+### 5. Analytics Engine
+
+Sentinel computes session-level and multi-session insights:
+
+- signal counts
+- error frequency
+- productivity indicators
+- session scoring (command vs error vs note balance)
+
+This enables trend detection and performance insight.
+
+---
+
+### 6. Reporting System
+
+Sentinel generates structured reports:
+
+- daily summaries
+- weekly breakdowns
+- monthly rollups
+
+Reports include:
+- session highlights
+- activity patterns
+- notable events
+
+---
+
+## Key Differentiators
+
+Sapphire Sentinel differs from traditional tools by:
+
+1. Converting terminal activity into narrative form
+2. Structuring work into contextual sessions
+3. Classifying activity into meaningful signal types
+4. Providing analytics across sessions
+5. Prioritizing human understanding over raw logging
+
+---
+
+## Intended Use Cases
+
+- Software development tracking
+- System administration auditing
+- Cybersecurity investigation workflows
+- Homelab and infrastructure management
+- Technical learning and review
+
+---
+
+## Future Expansion (Sentinel Insight)
+
+Planned enhancements include:
+
+- cross-session intelligence
+- searchable command memory
+- anomaly detection
+- client-ready reporting
+- system-wide activity correlation
+
+---
+
+## Summary
+
+Sapphire Sentinel is not a logging tool.
+
+It is a system designed to transform terminal activity into structured, contextual, and understandable knowledge.