Kwaku Danso
98678ff5a3
Three threads of work land here together to close out Tier 2.
### Block H follow-ups — day-of check-in
- Scanner is now an "open on your phone" magic-link flow. Hosts on
desktop mint a scoped JWT via POST /events/{id}/scanner-ticket and
render its URL into a QR; phone scans it and lands on /scanner with
the ticket as bearer. The ticket carries Audience=scanner so it can
never substitute for a session token.
- Plus-one confirmation at the door: scan → POST /check-in/preview to
fetch guest + expected party size → confirm buttons ("Just them",
"Party of N", custom) → POST /check-in. No more silent arrival_count=1.
- Offline scan queue: failed POSTs go into an IndexedDB store and drain
on the 'online' event with poison-message protection.
- Day-of arrivals headline widget on the event overview, gated to the
host's local calendar date so it doesn't dominate the page weeks out.
- Tab nav restyled with inline heroicons + scrollable segmented control;
Check-in moves to the rightmost slot.
- PWA: manifest + service worker scoped to /scanner, generated 192/512
icons (Go scripted renderer in scripts/gen-scanner-icons.go).
- Confirmation email QR was rendering broken because html/template
rewrites data: URLs to #ZgotmplZ; mark the value as template.URL.
- Email "open your invitation" link 404'd because we had no token to
put after /rsvp/. Threaded AccessLink through the RSVPConfirmed NATS
event from the API at submit time.
### Block G remainder — geolocation + threshold preview
- Pluggable GeoResolver in the fraud engine (NullResolver, IPApiResolver
for the free ip-api.com fallback, MaxMindResolver behind GG_GEOIP_DB_PATH).
Wrapped in a Redis cache (30d TTL). Geo flows through both gRPC and
NATS scoring paths.
- geo_jump scoring feature: >500km in <1h flags ("accessed from Lagos
and Paris within 12 minutes"); >500km in <6h is a softer signal. The
existing single-signal cap keeps a lone geo_jump in MEDIUM.
- FraudScored event carries geo_country/city/lat/lon; ApplyScore uses
COALESCE so a later re-score without geo doesn't wipe earlier data.
- Threshold-slider live preview: GET /events/{id}/security/thresholds/preview
returns band counts the host's existing access events would have
fallen into under the proposed thresholds. Debounced (250ms) widget
under the Advanced sliders so the host gets concrete feedback instead
of guessing.
### Cross-cutting — audit, tier-gating, feature flags
- audit_log table + internal/audit.Recorder (async fire-and-forget on
detached context so an audit blip never fails the real action). Wired
into branding update, thresholds update, allowlist add/remove,
collaborator invite/role-change/remove, message create/send-now/cancel.
- Tier-gating: extended billing.Limits with MaxCollaborators,
CustomBranding, Scanner, Broadcasts. Free = none; Pro = 5 + all;
Business = unlimited. Gates the scanner-ticket, message create,
branding put, and collaborator invite endpoints with 402 +
structured upgrade payload. Auto-reminders, fraud detection, and
analytics deliberately stay on every tier — those are safety + visibility
features, not upsell levers.
- Feature flags: feature_flags table + internal/flags.Store with 30s
in-memory refresh, stable sha256(key + user_id) percent bucketing,
unknown-key-defaults-on. Six Tier 2 flags pre-seeded. Three handlers
(branding, broadcasts, scanner) check the kill switch ahead of the
tier gate so ops can pull a feature back without a redeploy.
### Verified
- go test ./... + fraud-engine pytest (12/12 incl. 3 new geo_jump tests + 5
new flags tests).
- docker compose build + up across api, fraud-engine, notifier, frontend.
- /health endpoints 200; migrations 0014 + 0015 applied; 6 flags
seeded; audit_log table + partial indexes confirmed.
- Fraud-engine logs confirm geo resolver kind=CachedGeoResolver provider=auto.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
73 lines
2.7 KiB
Go
73 lines
2.7 KiB
Go
package natspub
|
|
|
|
import (
|
|
"time"
|
|
|
|
"github.com/google/uuid"
|
|
)
|
|
|
|
type AccessAttempted struct {
|
|
EventID uuid.UUID `json:"event_id"`
|
|
GuestID uuid.UUID `json:"guest_id"`
|
|
TokenID uuid.UUID `json:"token_id"`
|
|
AccessLogID uuid.UUID `json:"access_log_id"`
|
|
Fingerprint map[string]any `json:"fingerprint,omitempty"`
|
|
IPAddress string `json:"ip_address,omitempty"`
|
|
UserAgent string `json:"user_agent,omitempty"`
|
|
Referrer string `json:"referrer,omitempty"`
|
|
OccurredAt time.Time `json:"occurred_at"`
|
|
}
|
|
|
|
type FraudScored struct {
|
|
EventID uuid.UUID `json:"event_id"`
|
|
GuestID uuid.UUID `json:"guest_id"`
|
|
TokenID uuid.UUID `json:"token_id"`
|
|
AccessLogID uuid.UUID `json:"access_log_id"`
|
|
Score int `json:"score"`
|
|
Risk string `json:"risk"`
|
|
Reasons []string `json:"reasons"`
|
|
ScoredAt time.Time `json:"scored_at"`
|
|
// Tier 2 Block G — geolocation enrichment. All optional because
|
|
// private IPs and lookup failures leave them unset. The API
|
|
// consumer copies these onto access_logs.geo_* so the host UI can
|
|
// render "opened from Lagos, Nigeria" without having to do the
|
|
// lookup itself.
|
|
GeoCountry *string `json:"geo_country,omitempty"`
|
|
GeoCity *string `json:"geo_city,omitempty"`
|
|
GeoLat *float64 `json:"geo_lat,omitempty"`
|
|
GeoLon *float64 `json:"geo_lon,omitempty"`
|
|
}
|
|
|
|
type RSVPConfirmed struct {
|
|
EventID uuid.UUID `json:"event_id"`
|
|
GuestID uuid.UUID `json:"guest_id"`
|
|
RSVPID uuid.UUID `json:"rsvp_id"`
|
|
Response string `json:"response"`
|
|
PlusOnes int `json:"plus_ones"`
|
|
RiskScore *int `json:"risk_score,omitempty"`
|
|
SubmittedAt time.Time `json:"submitted_at"`
|
|
// AccessLink is the full URL the guest can return to in order to
|
|
// view (or edit) their confirmation — the same magic invitation URL
|
|
// they used to submit the RSVP. Populated by the API at submit time
|
|
// so the notifier can include it in the confirmation email (and
|
|
// fallback link beneath the inline QR). Empty on legacy events.
|
|
AccessLink string `json:"access_link,omitempty"`
|
|
}
|
|
|
|
// InvitationSend asks the notifier to dispatch a guest invitation email.
|
|
// Carries everything the email template needs so the worker doesn't have
|
|
// to re-fetch event/guest details from Postgres on every send.
|
|
type InvitationSend struct {
|
|
EventID uuid.UUID `json:"event_id"`
|
|
GuestID uuid.UUID `json:"guest_id"`
|
|
TokenID uuid.UUID `json:"token_id"`
|
|
GuestName string `json:"guest_name"`
|
|
GuestEmail string `json:"guest_email"`
|
|
HostName string `json:"host_name"`
|
|
EventName string `json:"event_name"`
|
|
Venue string `json:"venue,omitempty"`
|
|
EventDate time.Time `json:"event_date"`
|
|
Link string `json:"link"`
|
|
IssuedAt time.Time `json:"issued_at"`
|
|
}
|