testsAndMisc/linux_configuration/docs/DOCS-security-hardening-analysis.md
Krzysztof kuhy Rudnicki 49d82511c3 Adopt the four markdown namespaces and gate them
Renames this repo's markdown onto README.md / CLAUDE*.md / DOCS*.md /
TODO*.md so a future session can tell a live task from a finished
record without reading the file to find out.

TODO files carry the literal "REMOVE ME AFTER FINISH" and are deleted
when the work lands. Enforced by the md-naming pre-commit hook and CI
workflow, both delegating to the shared gate in kuhyx/utils so this
repo's idea of a valid name cannot drift from every other repo's.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A47aX5DJwmA3QFn3pkEWi7
2026-08-24 15:55:46 +02:00

17 lines
797 B
Markdown

# Security Hardening Analysis & Implementation Prompt
## Executive Summary
This document analyzes six digital wellbeing/security scripts and provides a detailed implementation prompt for hardening them against tampering. The analysis is based on thorough code review of the entire codebase.
---
Split into one file per part to stay under the 250-line cap.
- [Part 1: Current State Analysis](security-hardening/01-current-state.md)
- [Part 2: Language Considerations](security-hardening/02-language-choice.md)
- [Part 3: Implementation Prompt](security-hardening/03-implementation.md)
- [Part 4: Agent Personas](security-hardening/04-agent-personas.md)
- [Part 5: LLM README Files](security-hardening/05-llm-readmes.md)
- [Part 6: Test Script Template](security-hardening/06-test-template.md)