notify

This repository is the development source for the notify skill.

notify is intended to evolve into a small delivery-governance and delivery-execution layer. It should become the place where notification requests are validated, deduped, and sent, rather than leaving each producer system to own its own long-term direct-send path.

Current Scope

Today the repo is still small. Its current implemented helper flow is:

• bootstrap-any-files

That helper remains valid, but it should be understood as one specific use case rather than the whole future architecture of notify.

Intended V1 Direction

The next implementation step is to add a minimal generic execution path that can:

• accept a structured notification_request
• validate request shape and route fields
• apply dedupe using dedupe_key
• execute a real send path
• return a minimal notify result

This is the first step toward letting systems such as reminder-system hand delivery work to notify instead of keeping direct-send as the intended long-term architecture.

Current Entry Points

Current specific helper flow:

• run/bootstrap-any-files.py

Planned generic execution entrypoint:

• run/execute-request.py

Lightweight validation entrypoint:

• scripts/validate_notify.py
• current non-live stages:
  • self-check
  • contract-check
  • install-copy-check
  • skills-install-check

Runtime data policy:

• by default, notify stores dedupe state under its own skill-relative data/ directory
• NOTIFY_DEDUPE_PATH may override that location when validation or isolation is needed

Relationship To reminder-system

The intended long-term boundary is:

• reminder-system owns reminder orchestration
• notify owns delivery governance and delivery execution

The first practical integration target is a minimal notification_request handoff from reminder-system into notify.