Rehearsal and Acceptance

Scope

DCinside sends the full extraction queue and logs would-be picks while operators continue publishing. Surf does not publish during the scoring-only rehearsal. The publishing API is a dependency for later publishing stages, not for this rehearsal. Operator suitability, duplicate review and overlap with operator picks are reviewed separately and are not scoring-rehearsal pass criteria. The client-facing weight-management and outcomes endpoints remain outside this integration. Daily operator outcomes are shared separately; a long-lived upload destination for 1/6/24/48-hour counts and hide times remains a readiness item.

Acceptance criteria

These criteria incorporate DCinside’s September 30 reply and subsequent operator-independent pool policy. The earlier first-score-or-25-minute hold was never activated. The proposed new switch, 2026-10-15 00:00 KST / cycle 20261015T0000, is not confirmed; record the actual switch and cohort assignment without silently reclassifying historical measurements. Whether to backfill previously removed posts remains undecided; resending does not revive them. Passing code tests or a short load test does not establish the three-day SLA.

Criterion	Requirement
Duration	Three consecutive days, including three overnight windows, after a few hours of joint test cycles.
Cadence and delivery	Fixed five-minute cycles, 288 per day; at least 99% delivered. A no-data gap over 15 minutes triggers an alert.
Response time	At least 99% of cycles return within 60 seconds from sending, including at most one retry. Only the current cycle’s response can inform that cycle’s decision.
First score	Unchanged: return `waiting` before queue entry plus 15 minutes. At least 99% receive their first score within two cycles after that mark. Saved/hidden decisions remain in the denominator; immediate deleted/aged_out removals before the mark retain the early-removal exclusion. First scoring does not end retention.
Refresh	Re-score every eligible pending candidate every cycle.
Retention and removals	Saved/hidden labels do not change the pool. DCinside keeps delivering engagement every cycle until deleted or aged out under its 24-hour age filter, then sends the removal promptly with original event `decided_at`. There is no automatic server expiry. Saved/hidden remain accepted for compatibility, and any received removal still applies before scoring.
Recovery	Same-cycle exact replay is immutable. Re-including candidates/removals in another cycle is idempotent by `gall_id` plus `post_no`; state and responses survive restart.
Reconciliation	Daily sent/received/scored counts reconcile with 100% post-ID joins, including between-cycle entrants sent with `source="unknown"` when needed. Count unique entrants by original queue-entry KST date; distinguish first scores, repeated scoring events, removal receipts and client-side operator labels. Saved/hidden decisions no longer generate removal receipts under this policy. Record actual policy switch and cohort assignment.
Drills	A planned 20-minute sender stop verifies the 15-minute alert; late responses must be skipped. Planned drills are excluded from delivery/response percentages and reported separately, scheduled in weekday working hours.
Images	JPEG, 1,024-pixel long edge, about nine images at 75 KB each when present. Images may arrive one or two cycles later; raw scoring uses the candidate’s image count and must not wait. Image delivery is outside pass criteria.

A late response or GET recovery can reconcile data but never turns a missed decision deadline into a success. Semantic LLM deduplication is optional and is not a prerequisite for this scoring-only SLA. The sender owns retention, deletion/age removal delivery and operator labels. First-score reconciliation is calculated separately from unique post identities and score results; API counters do not provide a built-in SLA calculator. Hidden alone does not veto picks; the client skips actual current-board posts, and operator intervention follows publication/unpublication. API last-20 tier windows are not a complete board inventory. Compare post-decision scores separately because they use cycle-time evidence. See the worker handoff. The projected average 1,960 / peak 2,220 pending posts requires representative capacity verification, including near-24-hour histories and dedup work. Current-pool latency and the 5,000-row per-array protection do not prove the new pool meets the 60-second deadline. Pre-send engagement collection is outside that response budget. See service protections.

Agreed integration and remaining readiness

Topic	Status
Transport	HTTPS API, inline scores plus GET recovery, and the v1.3 image PUT layout.
Credentials	One long-lived key sent privately to the partner contact; rotation on either side’s request. Verify the agreed sender IP and public reachability.
Timestamps	RFC 3339, partner sends `+09:00`; KST `YYYYMMDDTHHMM` cycle ID. Allow 60 seconds of future-cycle clock tolerance.
Model	Delivered Model 0924, down-vote weight 0, original 15-minute queue-entry scoring point. Earlier scoring requires a separate validated model change.
Alert	`ext_dcinside_surf`, tagging Byungkun. Surf contact and actual delivered-alert evidence remain to be completed. A durable watchdog outbox entry alone does not prove delivery.
Start	Verify deployed artifact, durable recovery, real `scored_at`, representative full-queue deadline measurements and alert delivery; then agree the joint test and three-day start.

The implementation stores receipts, prepared cycles, queue state and immutable final results durably. For newly prepared cycles, scored_at records raw model score completion before the bounded deduplication wait; subtracting received_at from it does not measure final response latency. The 15-minute eligibility gate does not wait for image uploads. Source implementation and local test results must be distinguished from deployed and jointly observed SLA evidence.

Later publishing stages

Stage 1 covers hours without assigned operators: outside weekday 09:30–18:30 KST, plus weekends and public holidays, on Main and Light. DCinside may start at 02:00–07:00 and expand in steps as its own schedule setting. The Night tier stays out. Daytime interleaving during operator hours remains Stage 2; publishing controls remain DCinside’s responsibility.

Source messages

These source links require access to the shared Slack channel.

Getting Started

Scoring API

Images API

Weights and Outcomes

Operations

Scope

Acceptance criteria

Agreed integration and remaining readiness

Later publishing stages

Source messages

​Scope

​Acceptance criteria

​Agreed integration and remaining readiness

​Later publishing stages

​Source messages

Scope

Acceptance criteria

Agreed integration and remaining readiness

Later publishing stages

Source messages