How traynertunder2047/hsoc works
HSOC is documented as a local-first home-security desktop application, but the repository describes itself as an initial skeleton: its README says the directory READMEs are organizational placeholders, not implemented features. The intended workflow is a user operating the desktop dashboard alongside a local Go core/service, with SQLite as the core’s sole-writer store. The tree also preserves planned specialist Rust and Python modules, security-rule domains, and protocol contracts. These are shown as capabilities, not as verified runtime stages. Only the Go-to-database write relationship is explicitly documented; other connections are omitted.
Main entry points: internal Go core/service · database SQLite database
Components 11
Desktop application
- Dashboard
desktop
Local runtime
- Go core/service
internal - Specialist modules
rust - Auxiliary analysis
python
Security domains
- Detection rules
rules/detection - Correlation rules
rules/correlation - IoT rules
rules/iot - Vulnerability rules
rules/vulnerability
Contracts and storage
- IPC and messages
protocols - SQLite database
database
Other components
- Home user
Connections 1
- Go core/service → SQLite database: writes
README.md