FA-77693 / Legal deadline computation / Member archive

Service by publication: schedule validity and completion date: successive weeks · case 03

A schedule publishing Monday then Friday of the next week is rejected although the weeks are successive.

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Stipulated: service by publication requires at least four publications, one in each of successive calendar weeks (weeks run Sunday to Saturday), with no two in the same week. Service is complete on the 28th day after the first publication, and the response is due 30 days after completion (a closed last day moves to the next open day). Return {"valid": false} or {"valid": true, "complete", "respond"}.

Why this case matters

Docketing systems compute filing and response deadlines from trigger events; a wrong date can forfeit a right.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
uneven successive weeks	`{"valid": false}`	`{"complete": "2024-04-29", "respond": "2024-05-29", "valid": true}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.