72 lines
16 KiB
Markdown
72 lines
16 KiB
Markdown
# vssa-storm
|
||
|
||
_Last sync: 2026-08-12 12:20 UTC_
|
||
|
||
## Purpose
|
||
|
||
VSSA client investigation and evidence gathering.
|
||
|
||
## Current assets
|
||
|
||
- Gitea organization: `vssa-v1`
|
||
- Repository: <https://gitea.lego-cloud.eu/vssa-v1/documentation>
|
||
- Repository worktree: `/opt/data/vssa-documentation`
|
||
- Published Docusaurus site: <https://pages.apps.lego-cloud.eu/vssa-v1/documentation/>
|
||
- Client navigation has first-level **Overview** and an expanded **Registry** group containing 290 ordered client dossiers. System navigation follows the same hierarchy with 420 ordered system dossiers. Systems Dossiers are generated from canonical client system-table rows; the latest validated registry contains 420 unique systems from 621 observations, with conservative alias rules in `data/system-aliases.json` and machine-readable output at `/data/systems-registry.json`.
|
||
- Each generated Systems Dossier now includes canonical system-level analysis for production cloud/on-premises/hybrid hosting, original delivery kickoff, and latest production release. The source is `data/system-analysis.json`; known values require direct system-level URLs and supporting quotes, while missing evidence remains explicit rather than inferred.
|
||
- Overview, Clients, Systems, Methodology, and Data now use separate Docusaurus docs-plugin instances and dedicated sidebars. Generated system relationships use reusable React evidence cards, and every generated client/system dossier has a de-duplicated References index. `SYS-*` IDs are documented as internal deterministic SHA-1-derived registry IDs, not public-source identifiers.
|
||
- Every generated client system table has a **System dossier** column. Each of the 621 client observations displays its canonical `SYS-*` ID and links directly to one of the 420 internal system dossiers; generation fails if any observation is unlinked.
|
||
- Gitea Actions workflow: `.gitea/workflows/pages.yml`; successful `main` builds publish through the mounted LEGO Cloud Pages root.
|
||
- 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 documentation continuous research`) runs at `0 */2 * * *` and reports to this channel.
|
||
- Each run audits all 290 records, deeply researches up to 10 missing/weak/stale dossiers, continuously improves client/system/contractor evidence and documentation, reviews conservative system identity rules, validates the complete Docusaurus build, pushes evidence-backed changes, verifies Actions, and checks the deployed Pages backend.
|
||
- Research must prefer primary sources and must not infer providers/systems without corroborating evidence.
|
||
- Every run explicitly searches CPVA's official search portal for exact client/system names and relevant projects, treating result pages as discovery only until an opened CPVA source proves the claim. It also maintains per-record References indexes and preserves dedicated sidebars and evidence cards.
|
||
- Discord user `476287310627864587` is the designated CVP IS instructor for `https://viesiejipirkimai.lt/epps/viewCFTSAction.do`. Every run reads that user’s new channel guidance, validates reusable portal mechanics, patches `client-investigator`, and searches procurement stages from RFI/market consultation through tender, award, contract, amendment, and completion. Records are mapped to exact clients and canonical systems only when supported; stage semantics prevent an RFI/RFP/bid from being presented as an award, supplier engagement, implementation, production use, hosting, or completion.
|
||
- The job workdir and remote now target `/opt/data/vssa-documentation` and `vssa-v1/documentation`; it must not edit generated Docusaurus output.
|
||
- **Latest rotation (2026-08-12 12:11 UTC):** clients 161–170 were reviewed. Client 167 (Gruzdžių vaikų socializacijos centras) gained a high-confidence **Mano dienynas** observation from official client/provider sources; commit `15020a8ed0cec6869d9a0e5ae0d70753acfab69f` and Actions run `2344` were verified successful. Coverage is 79 researched, 193 partial, 18 no-public-evidence, and 0 pending; the registry remains 420 systems and now has 622 observations. Next rotation: clients 171–180. Subscription period, currency of the 2022 rules, implementation/integration supplier, hosting, and support allocation remain unknown for client 167.
|
||
|
||
## Availability continuity
|
||
|
||
- On 2026-08-12, Lego designated Discord user `476287310627864587` to teach Hermes use of the CVP IS procurement portal (`https://viesiejipirkimai.lt/epps/viewCFTSAction.do`) for finding and mapping RFIs, RFPs, specifications, awards, contracts/amendments, and completion records to VSSA clients and systems. This is a **CONFIRMED process directive**; exact portal procedures remain **UNKNOWN** until taught and validated. Recurring job `88833e00b4a2` was configured to ingest the instructor's channel guidance and preserve procurement-stage semantics.
|
||
- On 2026-08-12, commit `15020a8` added one defensible Mano dienynas observation for client 167, increasing the registry to 622 observations while retaining 420 canonical systems. Validation, deployed-content checks, authenticated remote readback, and Gitea Actions run `2344` succeeded. CPVA exact-name searches for clients 161–170 returned no applicable findings.
|
||
- On 2026-08-12, commit `4756f0d` added a generated **System dossier** column to every client “Cloud services and systems”/structured systems table. All 621 observations link by displayed `SYS-*` ID to valid canonical system routes covering 420 systems. Local validation/build passed, authenticated source readback succeeded, and Gitea Actions run `2343` completed successfully including Pages publication. Public access continues to return the intended Keycloak `302` redirect.
|
||
- On 2026-08-12, commit `d3b833b` reorganized both Clients and Systems sidebars into exactly two first-level entries: **Overview** and an expanded **Registry** group containing the ordered individual dossiers (290 clients and 420 systems). Local validation/build and rendered sidebar checks passed, authenticated Gitea readback confirmed both sidebar files, and Actions run `2342` completed successfully including the Pages publish step. Public access continues to return the intended Keycloak `302` redirect.
|
||
- On 2026-08-12, commit `95d2a9c` split Overview, Clients, Systems, Methodology, and Data into dedicated Docusaurus sidebars; documented that `SYS-*` values are deterministic internal IDs generated from canonical identity keys rather than public identifiers; replaced system relationship tables with reusable React evidence cards; added de-duplicated References indexes to all 290 client and 420 system dossiers; and updated recurring job `88833e00b4a2` to search CPVA's official `https://cpva.lt/paieska` endpoint for client/system mentions while retaining only verified evidence. Validation/build and representative rendered-route checks passed, Gitea Actions run `2341` succeeded, and public Pages retained its expected Keycloak `302` protection.
|
||
- On 2026-08-12, commit `a6ca8ab` added infrastructure/lifecycle analysis fields to all 420 then-current unique system records, updated the machine-readable registry to schema version 2, added identity-safe validation/bootstrap handling, and updated the recurring research job to investigate these fields continuously. Initial values remain `unknown` until direct evidence is found; no hosting or dates were fabricated from existing client observations. Validation/build passed, Gitea Actions run `2340` succeeded, and the Pages backend returned HTTP 200 with the three fields, schema-v2 registry, and raw canonical analysis file. Public access remains Keycloak-protected (`302`).
|
||
- On 2026-08-12, commit `1542674` reorganized the portal around researched user tasks after reviewing GOV.UK content-design/writing guidance, W3C WAI design guidance, and USWDS card/table guidance. Global navigation is now Overview, Clients, Systems, Methodology, and Data; the homepage prioritizes client browsing, system exploration, and evidence search; scope metrics distinguish clients, systems, and observations; generated overview/directory/system-registry guidance explains ordering, statuses, counts, and safe interpretation; provenance documents the machine-readable registry. The rationale is recorded in `docs/content-organization-research.md`. Validation/build passed, desktop visual and browser checks found no clipping/JS errors, Gitea Actions run `2335` succeeded, and the Pages backend returned HTTP 200 for all representative routes and search. Public access remains Keycloak-protected (`302`).
|
||
- The first scheduled continuous-research invocation at 22:00 UTC failed because the model provider reported overload. The next invocation completed at 00:12 UTC, validated all 290 clients plus 419 system routes/620 observations, pushed commit `b34670484501f0ddd27154c19b7605bf00f3efdd`, and verified successful Gitea Actions run `2333`. Public Pages correctly redirected unauthenticated traffic to Keycloak (`302`), while direct backend checks returned HTTP 200 for representative client/system routes and the registry.
|
||
- On 2026-08-11, the visible navbar/site label was changed from `VSSA Documentation` to `VSSA - Clients & Systems` in commit `d062598`. Gitea Actions run `2332` succeeded and the Pages backend returned HTTP 200 with the new label.
|
||
- On 2026-08-11, commit `e0efc31` flattened the Client Dossiers sidebar and added Systems Dossiers: 621 canonical evidence observations consolidated into 421 conservative unique-system records, 421 generated system routes, client/system provenance links, reviewed alias rules, machine-readable JSON, search indexing, and build validation. Gitea Actions run `2331` succeeded. The Pages backend returned HTTP 200 for the homepage, client 001, systems registry, representative centralized-government-IT dossier, registry JSON, and search index. Public Pages became Keycloak-protected concurrently and now correctly returns HTTP 302 to `/oauth2/start` for unauthenticated requests; this is infrastructure authentication, not a deployment failure.
|
||
- On 2026-08-11, the dedicated VSSA-styled Docusaurus landing page and native local search were published in commit `d43effe`. The design uses the official VSSA navy/blue visual language, locally bundled Public Sans, the official mark, square geometry, a separate `/overview/` documentation route, and live registry-derived metrics. Gitea Actions run `2330` completed successfully. The public homepage, overview, directory, local 3 MB search index, and logo returned HTTP 200; a browser query for `kanceliarija` returned multiple dossier results and opened client 001 successfully. Search is generated and executed inside the static site with no external search service.
|
||
- On 2026-08-11, `vssa-v1/vssa-clients` was renamed to `vssa-v1/documentation` with history preserved. The main worktree and 20 linked-worktree pointers were repaired and verified. Docusaurus 3.10.2 now renders all 290 dossiers from generated MDX-safe copies, preserves canonical source artifacts, and publishes byte-identical raw artifacts with SHA-256 hashes. Gitea Actions run `2329` completed successfully for commit `0a2144f`, and the public LEGO Cloud Pages homepage, directory, representative dossier routes, and raw manifest returned HTTP 200.
|
||
- 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: `1537072799775203358` (2026-08-12 12:18 UTC). Lego designated user `476287310627864587` as the CVP IS instructor and directed the recurring job to learn the procurement portal workflow and map supported procurement records to VSSA clients and systems.
|
||
- Previous processed human message: `1537067600998047804` (2026-08-12 11:57 UTC). Lego requested internal system-dossier links in every client cloud-services/systems table; commit `4756f0d` implemented and verified the links as recorded above.
|
||
- Previous processed human message: `1537058117223972915` (2026-08-12 11:20 UTC). Lego requested Overview/Registry hierarchy for both Clients and Systems sidebars; commit `d3b833b` implemented it.
|
||
- Previous processed human messages: `1537047891309494343`–`1537049333352894514` (2026-08-12 10:39–10:45 UTC). Lego required recurring infrastructure/lifecycle research, dedicated top-level sidebars, clarification of generated `SYS-*` IDs, reusable relationship cards, CPVA searching, and per-record reference indexes; commits `a6ca8ab` and `95d2a9c` implemented these requirements.
|
||
- Latest processed human message: `1536934392302141461` (2026-08-12). Lego requested an immediate research-led overall page improvement cycle focused on best practices for content organization; the deployed result is recorded above.
|
||
- Latest processed human message: `1536859431533281312` (2026-08-11). Lego requested the site label `VSSA - Clients & Systems`; it was published and verified as recorded above.
|
||
- Latest processed human message: `1536847412382015629` (2026-08-11). Lego requested a flat Client Dossiers sidebar, a unique Systems Dossiers registry, and continuous documentation/research automation; all three were implemented and published as recorded above.
|
||
- Latest processed human message: `1536845732613591160` (2026-08-11). Lego reported that the new landing page and search were not visible; inspection confirmed the changes had only existed locally. Hermes committed and pushed them, verified successful Actions run `2330`, and confirmed the public deployment and search behavior.
|
||
- Latest processed human message: `1536835494909055107` (2026-08-11). Lego directed Hermes to rename the repository to `documentation`, convert it to Docusaurus, add Gitea Actions, and publish through LEGO Cloud Pages; the completed state is recorded above.
|
||
- Previous 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`.
|