[V2][individual] Deadline Detector - Architecture and folder contract

[kryputh]

Goal

Create the isolated architecture contract for this tool as a self-contained mini-product.

Tool: Deadline Detector

Release tier: V2

Audience: individual

Required labels

This issue must carry these campaign labels:

• GrantFox OSS
• Maybe Rewarded
• Official Campaign
• Tooling Ecosystem
• V2 Later Tool
• Individual Tool

Implementation folder

All work for this issue must stay inside:

text tools\v2\individual\deadline-detector/

V2 later-release tool. Build the tool as complete isolated work, but do not link it to the main app yet.

Do not modify the main application shell, dashboard layout, navigation system, authentication, wallet core, mail rendering engine, existing inbox architecture, existing routing, Stellar integration core, database schema, or existing design system.

Deliverables

• Define internal module boundaries for components, services, hooks, tests, and docs.
• Document data ownership, dependencies, and integration constraints.
• Add folder-local architecture notes without touching core app files.

Acceptance criteria

• The tool has a clear folder-local architecture plan.
• The issue work does not modify the main app shell, routing, inbox architecture, wallet core, Stellar core, or design system.
• The specs explain what future contributors may and may not change.
• Files changed by this issue are limited to $rel/.
• The contribution is reviewable as a self-contained mini-product change.

OSS contributor notes

Keep the work small and reviewable. Prefer local fixtures, local docs, local tests, and folder-local components/services/hooks. If the tool needs a future connection to the main mail app, write that as a follow-up issue instead of adding the integration here.

[shadrach68]

please assign this to me

[mxrtins04]

Good day mediator, can i be assigned this issue please?