Initialize second brain vault

.gitignore

@@ -0,0 +1,3 @@
+.obsidian/workspace*.json
+.obsidian/cache/
+.trash/

00_Inbox/Capture.md

@@ -0,0 +1,9 @@
+# Capture
+
+Use this note as a staging area for raw captures, quick thoughts, links, and items that need to be turned into cleaner notes later.
+
+## Captures
+- 2026-03-09: Created local Obsidian-compatible second-brain vault for Claudio.
+- 2026-03-09: Telegram direct chat, group chat, Brave web search, and local voice-note transcription are working.
+- 2026-03-09: Swiss national vote results noted; if useful, convert into a topic/resource note later.
+- 2026-03-09: Claudio wants home lab management and the Obsidian second brain to persist across chats/contexts; if the conversation moves, Orik should continue from the documented state.

00_Inbox/Context Reload Guide.md

@@ -0,0 +1,23 @@
+# Context Reload Guide
+
+Use this as a lightweight reminder for future chats.
+
+## Rule
+Before asking Claudio to restate project context, check whether the answer is already in the second brain.
+
+## Vault path
+`/home/claudio/.openclaw/workspace/second-brain`
+
+## High-value notes
+- `02_Projects/Home Lab.md`
+- `02_Projects/Home Lab Plan.md`
+- `05_Resources/Home Lab Inventory.md`
+- `05_Resources/Home Lab Architecture.md`
+- `06_Decisions/Remote Access V1 Proposal.md`
+- `02_Projects/Job Hunt.md`
+
+## Method
+1. Search/list the vault lightly
+2. Read only the relevant note(s)
+3. Continue from documented state
+4. Ask Claudio only for missing or changed details

00_Inbox/Test note.md

@@ -0,0 +1 @@
+test from obsidian-cli

01_People/Claudio.md

@@ -0,0 +1,34 @@
+# Claudio
+
+## Basics
+- Name: Claudio
+- Timezone: Zurich, Switzerland
+- Preferred style: direct, respectful, not flattering
+- Wants challenge over agreement
+- Prefers short answers
+
+## Current context
+- Between jobs after finishing last role in early March 2026
+- Using the coming weeks to clarify direction
+- Main paths under consideration:
+  - a new job
+  - a Swiss GmbH for AI consulting / micro-SaaS
+  - a startup in robotics / medical devices
+
+## Working preferences
+- Values critical thinking and growth
+- Prefers results plus reasoning, not lots of narration
+- Interested in having a durable second-brain / wiki that can later be synced and browsed directly
+- Wants the assistant to take care of curation and structure instead of making him manage the vault manually
+- Trusts the assistant to decide what belongs in long-term notes versus lightweight memory
+
+## Current projects
+- [[02_Projects/Job Hunt]]
+- [[02_Projects/Home Lab]]
+
+## Links
+- [[03_Areas/Career]]
+- [[06_Decisions/Current Direction Questions]]
+- [[04_Topics/AI]]
+- [[04_Topics/Robotics]]
+- [[04_Topics/Medical Devices]]

02_Projects/Home Lab Plan.md

@@ -0,0 +1,32 @@
+# Home Lab Plan
+
+## Phase 1 — establish control
+- Define production vs testing boundaries
+- Adopt a V1 remote-access model with Tailscale for admin and Cloudflare for user-facing app access
+- Define the backup strategy and restore expectations
+- Inventory the current workloads more precisely
+- Avoid adding many new services until the platform is clearer
+
+## Phase 2 — stabilize core services
+- Confirm where drive/files should live short-term
+- Confirm where photo management should live short-term
+- Decide whether Synology remains the production home for some services during transition
+- Introduce identity/access management only once the service map is clear
+
+## Phase 3 — controlled evolution
+- Evaluate Nextcloud migration path
+- Evaluate Immich migration path
+- Evaluate Authentik or equivalent
+- Review whether Proxmox should be the central app platform
+- Revisit edge/remote-access complexity and reduce overlap where possible
+
+## What Orik should track
+- infra changes
+- service locations
+- architecture decisions
+- backup changes
+- migration plans
+- risks / TODOs
+
+## Current concern
+The likely failure mode is not lack of capability; it is too many overlapping tools and unclear boundaries.

02_Projects/Home Lab.md

@@ -0,0 +1,36 @@
+# Home Lab
+
+## Status
+Active
+
+## Goal
+Design and evolve a simple, well-documented, production-grade homelab with clear separation between production and testing, strong backups, and architecture that Claudio can trust for family and friends.
+
+## Priorities
+- Keep the system understandable
+- Avoid starting with too many apps
+- Build strong backup and recovery foundations
+- Separate production from testing
+- Document architecture and changes clearly
+
+## Current target apps
+- File sync / drive
+- Photo management
+- Media hosting
+- Identity / access management
+
+## Current app direction
+- Today: Synology Drive, Synology Photos, Jellyfin, Plex
+- Likely future: Nextcloud, Immich, Authentik
+
+## Key requirements
+- production vs testing separation
+- solid backup strategy
+- remote access strategy
+- architecture clarity
+- ability to evolve gradually
+
+## Related
+- [[05_Resources/Home Lab Inventory]]
+- [[05_Resources/Home Lab Architecture]]
+- [[06_Decisions/Home Lab Principles]]

02_Projects/Job Hunt.md

@@ -0,0 +1,22 @@
+# Job Hunt
+
+## Status
+Active
+
+## Role of Orik
+Track progress, opportunities, decisions, materials, and next steps.
+
+## Goal
+Help Claudio run a focused, well-documented job search without losing context across conversations.
+
+## What should be tracked here
+- target roles and themes
+- companies of interest
+- applications sent
+- interview stages
+- materials to improve
+- strategic decisions
+- blockers and next actions
+
+## Notes
+This project was already active in Telegram and should be treated as one of Claudio's main current projects.

03_Areas/Career.md

@@ -0,0 +1,22 @@
+# Career
+
+## Current state
+Claudio is in a transition period and is deciding what direction to pursue next.
+
+## Active options
+- New job
+- AI consulting / micro-SaaS via a Swiss GmbH
+- Startup in robotics
+- Startup in medical devices
+
+## Open questions
+- Which path has the best combination of speed, leverage, and energy?
+- Which option compounds skills and opportunities over the next 2-3 years?
+- What should be explored now versus postponed?
+
+## Related
+- [[01_People/Claudio]]
+- [[06_Decisions/Current Direction Questions]]
+- [[04_Topics/AI]]
+- [[04_Topics/Robotics]]
+- [[04_Topics/Medical Devices]]

03_Areas/Second Brain Operating Model.md

@@ -0,0 +1,39 @@
+# Second Brain Operating Model
+
+## Owner
+Claudio
+
+## Maintainer
+Orik
+
+## Default policy
+Claudio does not want to manage structure manually.
+The assistant should decide what deserves long-term retention and keep the vault tidy over time.
+
+## What should usually be captured
+- durable facts about Claudio
+- active projects and goals
+- decisions and why they were made
+- recurring preferences
+- useful resources, references, and links
+- ideas worth revisiting
+- themes that show up repeatedly in conversation
+
+## What should usually not be captured
+- low-value chat residue
+- duplicate notes
+- transient details with no future use
+- sensitive details unless they are clearly useful to retain
+
+## Editing policy
+The assistant may create, merge, rename, rewrite, archive, or delete notes when that improves usefulness.
+Prefer a small number of high-value notes over note sprawl.
+
+## Cross-context continuity
+Home lab and second-brain management should continue across chats and Telegram groups.
+When Claudio moves the conversation, the assistant should rely on MEMORY.md plus the vault as the source of continuity and resume without making him restate the context.
+Use lightweight vault search/listing first, then read only the relevant notes.
+
+## Telegram groups
+Any new Telegram group should be allowed automatically.
+Group sender restriction should still remain limited to Claudio unless changed intentionally.

04_Topics/AI.md

@@ -0,0 +1,14 @@
+# AI
+
+## Why this exists
+A place for Claudio's interest in AI, notes on tools, products, ideas, opportunities, and research directions.
+
+## Related directions
+- AI consulting
+- micro-SaaS
+- tooling and automation
+
+## Related
+- [[01_People/Claudio]]
+- [[03_Areas/Career]]
+- [[06_Decisions/Current Direction Questions]]

04_Topics/Medical Devices.md

@@ -0,0 +1,9 @@
+# Medical Devices
+
+## Why this exists
+Track Claudio's interest in medical devices, market ideas, technical/regulatory notes, and startup possibilities.
+
+## Related
+- [[01_People/Claudio]]
+- [[03_Areas/Career]]
+- [[06_Decisions/Current Direction Questions]]

04_Topics/Robotics.md

@@ -0,0 +1,9 @@
+# Robotics
+
+## Why this exists
+Track Claudio's interest in robotics ideas, companies, technical notes, and startup possibilities.
+
+## Related
+- [[01_People/Claudio]]
+- [[03_Areas/Career]]
+- [[06_Decisions/Current Direction Questions]]

04_Topics/Swiss Politics.md

@@ -0,0 +1,12 @@
+# Swiss Politics
+
+## Notes
+- 2026-03-09 federal vote:
+  - SRG / media licence fee cut initiative rejected (62% No)
+  - Climate fund initiative rejected (71% No)
+  - Individual taxation accepted (54% Yes)
+  - Cash counterproposal accepted (73% Yes)
+  - Turnout 56%
+
+## Related
+- [[05_Resources/Swiss Federal Vote 2026-03-08]]

05_Resources/Home Lab Architecture.md

@@ -0,0 +1,59 @@
+# Home Lab Architecture
+
+## Current-state sketch
+
+```mermaid
+flowchart TD
+    U[Claudio devices\nMacBook Pro M4\niPad Air M3\niPhone 15 Pro]
+    RA[Remote access layer\nTailscale / ZeroTier / Pangolin / Cloudflare]
+    VPS[Netcup VPS\nweb apps + remote proxy]
+    NAS[Synology DS218+\nDrive / Photos / Jellyfin / Plex]
+    PNAS[Parents' Synology NAS\nfuture off-site backup target]
+    DELL[Old Dell laptop\nDebian\nHome Assistant + Restic backup server]
+    PMX[MacBook Pro 2017 Intel\nProxmox\nOpenClaw / Ollama / Grafana / Pangolin-Newt]
+    PI[Raspberry Pi 3\nspare / test]
+    FUT[Future storage ideas\nold disks / possible CEPH later]
+
+    U --> RA
+    RA --> VPS
+    RA --> NAS
+    RA --> DELL
+    RA --> PMX
+    RA --> PI
+    NAS -. future backup .-> PNAS
+    DELL -. backup orchestration .-> PNAS
+    FUT -. future .-> PMX
+    FUT -. future .-> NAS
+```
+
+## Desired operating model
+
+```mermaid
+flowchart LR
+    Users[Claudio / family / friends]
+    Access[Unified remote access + identity]
+    Prod[Production environment\nreliable, documented, backed up]
+    Test[Testing environment\nexperimentation / breakable]
+    Backup[Backups + restore validation]
+    Docs[Documentation\nObsidian second brain]
+
+    Users --> Access
+    Access --> Prod
+    Access --> Test
+    Prod --> Backup
+    Test --> Backup
+    Prod --> Docs
+    Test --> Docs
+```
+
+## Recommended interpretation
+The current setup already has enough moving parts that the main risk is architectural drift, not lack of hardware.
+The next step should be simplification and boundary-setting, not adding many more apps.
+A good target is to define one production lane, one testing lane, and one backup strategy before larger migrations.
+
+## Near-term planning questions
+- What exactly counts as production today?
+- Which host should be the primary app host?
+- Which remote-access path should become the default?
+- What is the restore story for each critical service?
+- Which current services should stay on Synology for now?

05_Resources/Home Lab Inventory.md

@@ -0,0 +1,47 @@
+# Home Lab Inventory
+
+## Personal devices
+- MacBook Pro M4 — main computer
+- iPad Air M3
+- iPhone 15 Pro
+
+## Server / infra equipment
+- Synology DS218+
+  - 2 × 18 TB
+  - RAID 1
+  - roughly 16 TB usable
+  - currently used for Synology Drive, Synology Photos, Jellyfin, Plex
+- Old Dell laptop
+  - Debian
+  - running Home Assistant
+  - backup server (Restic)
+- MacBook Pro 2017 Intel
+  - Proxmox
+  - 10 GbE
+  - currently running:
+    - OpenClaw
+    - Ollama
+    - Grafana
+    - Pangolin/Newt
+- Raspberry Pi 3
+  - currently not in active use
+  - available for testing
+- Old hard disks
+  - possible future CEPH experimentation
+  - not a current priority
+- Netcup VPS (Germany)
+  - runs a couple of web apps
+  - remote proxy
+- Parents' Synology NAS
+  - 2 × 4 TB
+  - used locally by Claudio's parents today
+  - possible future managed off-site backup target once Claudio's system is ready
+
+## Remote access / overlay / edge tools in use
+- Tailscale
+- ZeroTier
+- Pangolin
+- Cloudflare reverse proxy / Zero Trust tunnel
+
+## Intent
+The system should eventually support reliable services for family and friends, so operational simplicity and backups matter more than novelty.

05_Resources/Swiss Federal Vote 2026-03-08.md

@@ -0,0 +1,14 @@
+# Swiss Federal Vote 2026-03-08
+
+## Results
+- SRG / media licence fee cut initiative: rejected, 62% No
+- Climate fund initiative: rejected, 71% No
+- Individual taxation for married couples: accepted, 54% Yes
+- Cash counterproposal: accepted, 73% Yes
+- Turnout: 56%
+
+## Summary
+The Federal Council's preferred line won on all four issues.
+Voters supported a targeted tax reform and strong constitutional protection for cash.
+They rejected both a large climate fund and cuts to public broadcasting funding.
+Overall result: pragmatic, relatively cautious, and not very appetite-driven for big new spending.

06_Decisions/Current Direction Questions.md

@@ -0,0 +1,21 @@
+# Current Direction Questions
+
+## Situation
+As of 2026-03-09, Claudio is between jobs and using the next weeks to clarify direction.
+
+## Main candidates
+1. Take a new job
+2. Form a Swiss GmbH for AI consulting / micro-SaaS
+3. Start something in robotics
+4. Start something in medical devices
+
+## Decision criteria
+- personal energy
+- learning rate
+- strategic upside
+- financial runway / risk
+- speed to first traction
+- fit with Claudio's long-term goals
+
+## Status
+Open. This note should be updated as options get tested or ruled out.

06_Decisions/Home Lab Principles.md

@@ -0,0 +1,22 @@
+# Home Lab Principles
+
+## Working principles
+- Start simple
+- Prefer clarity over cleverness
+- Document every meaningful architectural change
+- Production and testing should be clearly separated
+- Backups and restore confidence are first-class requirements
+- Avoid deploying many apps before the platform is understandable
+
+## Near-term app focus
+1. Drive / file sync
+2. Photo app
+3. Identity / access layer
+
+## Current transition direction
+- from Synology Drive to possible Nextcloud later
+- from Synology Photos to possible Immich later
+- keep current media stack running while broader architecture is clarified
+
+## Notes
+This project should be managed incrementally, not as a big-bang migration.

06_Decisions/Remote Access V1 Proposal.md

@@ -0,0 +1,97 @@
+# Remote Access V1 Proposal
+
+## Goal
+Create a simple, production-sane remote access model that is easy to understand, easy to operate, and does not depend on four overlapping paths.
+
+## Current problem
+Remote access is currently spread across:
+- Tailscale
+- ZeroTier
+- Pangolin
+- Cloudflare reverse proxy / Zero Trust tunnel
+
+This creates overlap, unclear defaults, and more failure modes than necessary.
+
+## V1 recommendation
+Use **two lanes only**:
+
+1. **Admin / maintenance lane:** Tailscale
+2. **User / app access lane:** one public reverse-proxy path, preferably Cloudflare tunnel for now
+
+## What to do with the current tools
+- **Keep Tailscale** as the default admin path
+- **Deprecate ZeroTier** unless a concrete need appears that Tailscale cannot solve
+- **Do not make Pangolin the primary edge yet**
+- **Keep Cloudflare tunnel / reverse proxy** as the primary app-access layer for V1
+
+## Why this is the right V1
+- Tailscale is strong for operator access, SSH, dashboards, and maintenance
+- Cloudflare is strong for controlled public exposure and gradual publishing of apps
+- Pangolin may still be interesting later, but using it now as both edge and auth adds moving parts before the platform is stable
+- ZeroTier is redundant unless it solves a specific problem better than Tailscale in your setup
+
+## V1 policy
+### Lane 1 — admin / maintenance
+Use Tailscale for:
+- SSH / terminal access
+- Grafana
+- OpenClaw admin access
+- internal dashboards
+- Proxmox management
+- Home Assistant admin
+- anything that should not be publicly exposed
+
+### Lane 2 — app access
+Use Cloudflare tunnel / reverse proxy for:
+- selected apps intended for normal browser access
+- family / friend access later
+- controlled public-facing entrypoints
+
+### Lane 3 — not part of V1
+- Pangolin as primary platform edge
+- ZeroTier as parallel mesh
+
+These should stay out of the critical path for now.
+
+## Identity recommendation
+Do **not** introduce Authentik as a broad central dependency yet.
+First simplify access paths.
+Then, once the app map is stable, decide whether Authentik should sit behind Cloudflare, alongside it, or only protect selected internal apps.
+
+## Backup / off-site implication
+The parents' Synology NAS is a strong future off-site backup target.
+That is strategically more valuable right now than adding another access product.
+
+## Suggested architecture
+```mermaid
+flowchart LR
+    Admin[Claudio admin access] --> TS[Tailscale]
+    Users[Claudio / family / friends app access] --> CF[Cloudflare tunnel / reverse proxy]
+
+    TS --> PMX[Proxmox host and internal services]
+    TS --> DELL[Debian backup / Home Assistant host]
+    TS --> NAS[Synology production services]
+    TS --> VPS[Netcup VPS]
+
+    CF --> NAS
+    CF --> PMX
+    CF --> VPS
+
+    NAS -. backups later .-> PNAS[Parents' Synology NAS]
+    DELL -. backup orchestration .-> PNAS
+```
+
+## Concrete V1 rules
+- Every service must have one **primary access path**
+- If a service is admin-only, it should default to Tailscale-only
+- If a service is user-facing, expose it through Cloudflare only if there is a clear reason
+- Avoid exposing the same app through multiple remote-access products unless documented
+- Record every published service in the architecture notes
+
+## First implementation steps
+1. Create a service inventory with one owner host and one primary access path per service
+2. Decide which current services are strictly internal/admin vs user-facing
+3. Remove ZeroTier from the default plan and treat Pangolin as experimental only
+
+## Opinion
+The cleanest V1 is not the fanciest one. It is the one you can explain on one page and recover under stress.

Home.md

@@ -0,0 +1,23 @@
+# Home
+
+## Core Notes
+- [[01_People/Claudio]]
+- [[03_Areas/Career]]
+- [[03_Areas/Second Brain Operating Model]]
+- [[02_Projects/Job Hunt]]
+- [[02_Projects/Home Lab]]
+- [[02_Projects/Home Lab Plan]]
+- [[06_Decisions/Current Direction Questions]]
+- [[06_Decisions/Home Lab Principles]]
+- [[06_Decisions/Remote Access V1 Proposal]]
+- [[04_Topics/AI]]
+- [[04_Topics/Robotics]]
+- [[04_Topics/Medical Devices]]
+- [[04_Topics/Swiss Politics]]
+
+## Inbox
+- [[00_Inbox/Capture]]
+
+## How this vault should evolve
+This vault is meant to be actively maintained.
+Notes may be edited, merged, renamed, archived, or deleted when that improves clarity.

README.md

@@ -0,0 +1,30 @@
+# Claudio Second Brain
+
+This is a local Obsidian-compatible vault for Claudio.
+
+Purpose:
+- durable notes beyond assistant memory
+- searchable personal wiki
+- project, interest, decision, and reading notes
+- a place the assistant can keep updated over time
+
+## Principles
+- plain Markdown first
+- concise, linkable notes
+- prefer editing existing notes over creating duplicates
+- archive or delete stale notes when they stop being useful
+- sensitive/private material should be stored intentionally, not automatically
+
+## Suggested workflow
+- `00_Inbox/` for raw captures
+- `01_People/` for person pages
+- `02_Projects/` for active projects
+- `03_Areas/` for ongoing life domains
+- `04_Topics/` for evergreen interests
+- `05_Resources/` for references, links, books, articles
+- `06_Decisions/` for meaningful choices and rationale
+- `07_Daily/` for daily notes
+
+## Relationship to assistant memory
+Assistant memory is for lightweight continuity.
+This vault is the durable, user-visible knowledge base.