A plan should show
where it came from.
Deadline Loom is an Astro app made with AI development assistance for the DEV Sanity Challenge, Path Two. It grew from a real research problem: event pages, official rules, and listing sites can show different dates or prize claims. A deadline deserves the same provenance as any other consequential fact.
Browse the public source repository ↗ · Download the complete source code (ZIP) ↗
What the app actually does
The workbench reads competition records, evidence sources, claims, revisions, and review decisions from a public Sanity dataset when connected. If no project is configured or a read fails, it displays an explicitly labeled local fixture. Work estimates, an earlier-deadline rehearsal, and planning notes stay in your browser. They are never presented as organizer facts or published approvals.
The planner orders selected work by the earliest deadline, then turns estimated effort into elapsed time using a daily-capacity assumption. Human minutes are added separately. It shows slack, missed deadlines, and a different clock display without changing the actual instant. The ICS export preserves UTC event times and links back to the source.
The Sanity model
competition → evidenceSource sourceClaim → competition + evidenceSource evidenceRevision → competition + evidenceSource reviewDecision → exact reviewed evidenceRevision projectNote → estimates, setup notes, simulation labels
Sources and proposed changes are independent documents. Sanity references preserve the relationship instead of copying a date into every screen. A reviewer can inspect the original claim, propose a revision, and keep a decision attached to that revision in Studio. The public reader refreshes once a minute while the tab is visible. Published decisions appear in the decision memory.
Truthful by construction
- The sample evidence was checked on October 2, 2026. Source links and check dates remain visible.
- A 24-hour-earlier deadline is a labeled counterfactual. It is not an announcement from an organizer.
- Prize amounts are prospective. No entry, exported event, or green schedule means cash has been earned.
- Effort estimates are assumptions that the reader can change.
- Local planning decisions become stale when the plan inputs or recorded source dates change.
Build boundaries
Scenario edits do not write to Sanity. Authenticated editors manage published content in Studio. The browser uses no write token, contains no private participant details, and cannot mutate the dataset. This keeps a public judge demo separate from the editorial workflow.
Source text remains evidence. Deadline Loom does not execute instructions found in a source page.