# vssa-storm

_Last sync: 2026-08-11 20:33 UTC_

## Purpose

VSSA client investigation and evidence gathering.

## Current assets

- Gitea organization: `vssa-v1`
- Repository: <https://gitea.lego-cloud.eu/vssa-v1/vssa-clients>
- Repository worktree: `/opt/data/vssa-clients`
- Source registry: `source/message.txt`, containing 290 numbered clients.
- Required output: one concise Markdown dossier per client with exact name, one-sentence purpose, systems/clouds, plain-language system meaning, precise client relationship, identified contractor/company and role, direct evidence, confidence, and short gaps.
- Investigation skill: `client-investigator`; recurring runs must deepen contractor research and patch the skill only with validated reusable practices.

## Automation

- Cron job `88833e00b4a2` (`VSSA client cloud/system investigation`) runs at `0 */2 * * *` and reports to this channel.
- Each run audits all 290 records, deeply researches up to 10 missing/weak/stale dossiers, updates the index, commits and pushes evidence-backed changes, and verifies remote state.
- Research must prefer primary sources and must not infer providers/systems without corroborating evidence.

## Availability continuity

- On 2026-08-11, Gitea 1.27.0 initially left web/API healthy while all Git transport operations crashed in the Go runtime during `moduledataverify1`. Gitea was subsequently updated to `1.27.1`; SSH and Smart HTTP recovered. The queued VSSA commit `6fc42ab` was pushed and remotely verified, leaving local `main` synchronized with `origin/main`.
- **CONFIRMED recovery decision/status (2026-08-11 19:05–19:06 UTC):** after Lego asked Hermes to recheck, live verification showed Gitea `1.27.1`, REST API, SSH Git, and HTTPS Git all healthy. The queued VSSA client-dossier commit `6fc42ab` was pushed, remote `INDEX.md` was read back, and local `main` matched `origin/main`. No VSSA delivery blocker remained from this incident.
- On 2026-08-04 at 20:05–20:42 UTC, Lego (`root_at_skic`) repeatedly asked whether Hermes was alive. These messages are evidence of the broader Hermes availability incident, not a change to the VSSA investigation scope. The incident was subsequently investigated in `#jarvis-jr-v1-hermes-setup`.

## Terminology

- In repository and Gitea workflow guidance, **mutation** means an operation that changes data or state (for example editing, committing, pushing, changing settings, or deleting). “Discovery before mutation” means inspect and confirm the target repository and its current state before making changes.

## Source anchor

- Latest processed human message: `1536812738679021618` (2026-08-11 19:05 UTC). Lego asked Hermes to check Gitea after remediation; the subsequent verified result is recorded above.
- Previous incident message: `1536807021674762261` (2026-08-11 18:42 UTC), asking what was wrong with Gitea and how to resolve it.
- Previous availability message: `1534300468530905170` (2026-08-04 20:42 UTC). Lego asked whether Hermes was alive; no VSSA project scope or status changed.
- Previous terminology message: `1533032343021813930` (2026-08-01 08:43 UTC), requesting clarification of “mutation”.
- Previous durable directive: `1532810727847624884` (2026-07-31 18:02 UTC), confirming the concise one-file-per-client format, plain-language system meaning, contractor/company research, deep public investigation, and iterative improvement of `client-investigator`.