Aggregator, intake with deployment, catalog, first curated entries #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "night-2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Four pieces, each built, reviewed adversarially and fixed separately, then merged here and tested together (
cargo test --workspace: all pass; clippy clean).ogc-db-aggregate): raw contributions and curated measurements → the complete/v1directory and a privatereport.md. Size variants, builds with a change-point rule, weekly cap, MAD outliers, weighted median/p25/p75, k ≥ 3 and ≥ 2 weeks gate for crowd cells, anchor check, confidence, recommendation (≥ medium on both file systems), tiers, anomaly gate with--approve, deterministic output. Golden datasets: flood, slow poisoning, update with change-point, bimodal sizes, gen blocklist. The curated format has a schema (model/schema/curated.schema.json).ogc-intake): unix socket only, one route, validation with ogc-db-proto, PoW and replay by stamp, shuffled weekly spool, kill switches on SIGHUP. deploy/: nginx, BunkerWeb (1.6.x) and systemd settings for the VM behind BunkerWeb and the Tailscale tunnel, so the submit host keeps no client address on disk; webhook deployment of both sites; a canary that sends requests from a marker address and searches every log, spool and state file (passes locally with nginx and with BunkerWeb 1.6.15). Owner checks are listed indeploy/README.md.ogc-db-catalog): names of published games and copies of their Steam header images, ≤ 1 request/s, cached; the site shows the copies from our own host.curated/SOURCES.md.A local dry run on the curated entries (aggregator → catalog → aggregator with names → site) builds the real site: 9 games, all with names, images and a Windows tier.
public/is not committed yet.