feat: Add foundational documentation for security, workflow, and project management

- Create SECURITY.md to outline security policies and practices.
- Establish WORKFLOW.md detailing the project lifecycle from planning to retrospective.
- Introduce decision log structure in decisions/README.md for tracking architecture decisions.
- Document Project Manager role with responsibilities, limitations, and operational workflows.
- Implement templates for ADRs, bugs, meetings, projects, retrospectives, RFCs, roadmaps, and sprints.
- Set up memory logs for architecture and company-wide lessons learned.
- Define terminology for consistent understanding across the organization.

memory/company-memory.md

@@ -0,0 +1,23 @@
+# Company Memory
+
+Cross-cutting facts about how Local LLC actually operates in practice — process patterns and
+organizational decisions that emerged from experience, not policy declared up front. Policy
+itself belongs in the root docs (`README.md`'s repository map); this file is what those docs
+don't capture. See [../MEMORY.md](../MEMORY.md) for what belongs here vs. elsewhere.
+
+## Log
+
+*No entries yet. This company is pre-v0.1 operational — the first real entries will come from
+the first sprint's retrospective (`templates/RETROSPECTIVE.md`) and the first planning sessions
+run under `FOUNDER.md`.*
+
+Format for new entries:
+
+```
+### YYYY-MM-DD — <short title>
+
+<the fact or decision>
+
+**Why:** <the reasoning or incident behind it>
+**How to apply:** <what this should change about future behavior>
+```