docs(spec): Discovery-Tracking-Baseline P1 (WORKFLOW §3.3)#54
Merged
Conversation
Architektur-Briefing vor Code für ein tägliches Discovery-Tracking- Dashboard, das messbar macht, ob die Discovery-Investments der letzten Sprints (sitemap-sync, MoltGuard-Discovery-Trio, moltguard- Remote-Migration) wirken. Adressiert die 6 Lars-Fragen aus dem Sprint-Auftrag: 1. METRIKEN (5): GSC + nginx-Bot-Hits (FastAPI + nginx static + /guard proxy) + GitHub Stars/Clones/Views + Self-Probes (Discovery-Surface-Health). Quelle + Aufwand + Privacy pro Metrik. 2. WO TRACKEN: Empfehlung (a) neuer Block auf existierendem /admin/dashboard (14 Endpoints schon live, admin_auth.py + admin_rbac.py existieren). Niedrigster Implementation-Aufwand + höchste Wahrscheinlichkeit täglicher Lars-Konsumtion. 3. AGGREGATIONS-FREQUENZ: täglicher Snapshot 00:30 UTC in neue PostgreSQL-Tabelle discovery_snapshots mit JSONB-payload (schema- flexibel ohne ALTER TABLE). 4. BASELINE-SNAPSHOT: P2 heute Abend Pflicht — ohne Baseline kein Delta-Messpunkt morgen. 5. PRIVACY: 4 Quellen-DSGVO-Status verifiziert (3 schon konform via bestehender Schicht, nur nginx /var/log/nginx/access.log braucht neuen Anonymisierungs-Step im Parser). Keine IPs in discovery_snapshots.payload persistiert — nur User-Agent-Counts. 6. EXISTING TOOLING: 14 admin-endpoints schon live, request_log- Tabelle DSGVO-konform, caller_labels + known_callers existieren. Lücke: nur Discovery-Surface-Aggregation fehlt, nicht die Infrastructure. 9 Open Decisions in §9 für Lars-Sichtung. P2-Pflicht heute Abend (Baseline), P3 Dashboard-Implementation danach. Reine Doku, kein Code, kein Deploy.
4 tasks
HaraldeRoessler
pushed a commit
to HaraldeRoessler/moltrust-api
that referenced
this pull request
May 22, 2026
Migration per Discovery-Tracking-Baseline SPEC (PR MoltyCel#54 merged 2026-05-20) §3.5 + §4 + §6 P2. Schema: - BIGSERIAL primary key - DATE-unique (one row per day; UPSERT-safe) - JSONB payload (schema-flexible — V1 fields can grow without ALTER TABLE) - source_run_status enum (ok/partial/failed) for daily-cron-health visibility Idempotent (IF NOT EXISTS on table + index). Baseline row for 2026-05-21 will be INSERTed manually post-migration-apply (SPEC §3.6 — Pflicht-Termin heute Abend für Delta-Messbarkeit morgen). Cron-Script (scripts/discovery_snapshot.py) folgt in P3.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
P1-SPEC für ein tägliches Discovery-Tracking-Dashboard, das messbar macht, ob die Discovery-Investments der letzten Sprints (sitemap-sync PR #30, MoltGuard-Discovery-Trio PRs #48/#51/#32, moltguard-Remote-Migration PR #52 → moltguard #1+#2) wirken. Reine Doku, kein Code, kein Deploy.
Adressiert die 6 Lars-Fragen
/admin/dashboard— 14 Endpoints schon live,admin_auth.py+admin_rbac.pyexistieren. Niedrigster Implementation-Aufwand.discovery_snapshots-Tabelle (PostgreSQLmoltstackDB, JSONB-payload für Schema-Flexibilität).request_log+ moltguardrequestLoggerschon last-octet-anonym. Nur nginx/var/log/nginx/access.logbraucht neuen Anonymisierungs-Step im Parser. Discovery-Snapshots persistieren keine IPs, nur User-Agent-Counts.request_log,caller_labels,known_callers, alle/admin/dashboard/*-Endpoints. Lücke ist nur die Discovery-Surface-Aggregation, nicht die Infrastructure.Phasen-Plan
/admin/dashboard/discovery-Endpoint + Frontend-Block9 Open Decisions (§9) für deine Sichtung
~/.moltrust_secrets(Empfehlung: PAT, niedrigste neue Surface)Pre-Commit-Diff-Verifikation (§8)
Genau 1 neues File, etabliertes
docs/specs/YYYY-MM-DD_xxx-SPEC.md-Schema, kein Fremd-Scope.Branch-Hygiene (§11.4)
Branch ab frischem
origin/main(0 behind), Worktree~/moltrust-api-H— kein shared anchor.§2.3 Cross-Review
Skip — reine Doku, kein Auth-/Credential-/Token-Pfad. Re-evaluate falls P3-Implementation unerwartet GSC-OAuth oder GitHub-PAT-Integration mitbringt (siehe §9.6).
Test plan