operations-planning

Event planning: tasks/checklists with due dates relative to event start

What it is for

# operations-planning

Event planning library crate: tasks/checklists with due dates relative to event start.

Architecture

This crate provides planning items (tasks/checklists) that can be linked to:

• A single encounter (for one-time events)
• A recurring series (for recurring events)

Key Design Decisions

1. FK XOR Constraint: Each planning item must link to exactly one of:

• encounter_id (for single events)
• series_id (for recurring events)

This prevents polymorphic linking while maintaining referential integrity.

2. Relative Due Dates: Items can have:

• Absolute due date (due_at)
• Relative offset (due_offset_days - negative = before event)

3. Task Dependencies: Items can depend on other items for simple task graphs.

Example

use operations_planning::{PlanningItem, compute_due_date};
use chrono::{Duration, Utc};

// Create a task due 2 weeks before event start
let item = PlanningItem::for_encounter(encounter_id, "Book venue")
.with_description("Reserve the meeting room")
.due_offset(-14);

// Compute actual due date based on event start
let event_start = Utc::now() + Duration::days(30);
let due_date = compute_due_date(&item, event_start);

Capabilities

postgres (other)

PostgreSQL storage for planning items.

How to use it

No examples/ target and no doctest in this crate's rustdoc. The tests listed under Verification are the closest executable usage.

Module structure

operations_planning

• postgres

Public surface

`postgres`

Re-exports. Exported here, defined elsewhere.

Boundary

Reaches into foundation, identity.

Shares tier operations with 40 other crates: operations-approval-workflow, operations-assessments, operations-block-imaging, operations-boot-media, operations-browser-agent-worker, operations-camera-discovery, operations-camera-liveview, operations-camera-registry, … (40 total).

_What this crate deliberately does NOT own is a judgment. No committed registry records one for it, so none is stated here._

Where it sits

Tier flow. Which tiers this crate's own edges cross.

flowchart LR
  n_operations["operations"] --> n_foundation["foundation"]
  n_operations["operations"] --> n_identity["identity"]

Dependencies

Runtime, in this workspace.

Runtime, from outside the workspace.

Development, from outside the workspace.

Build. None.

Depended on by. 2 workspace crates.

Signal flow — what reaches this crate, and what it reaches.

flowchart LR
  n_application_planning["application-planning"] -->|uses| SELF
  n_foundation_test_support["foundation-test-support"] -->|uses| SELF
  SELF["operations-planning"]
  SELF -->|runtime| n_foundation_basemodels["foundation-basemodels"]
  SELF -->|runtime| n_identity_parties["identity-parties"]
  classDef self fill:#1f883d,stroke:#1f883d,color:#fff;
  class SELF self;

Feature flags

flowchart LR
  n_default["default"]
  n_postgres["postgres"] --> n_dep_sqlx["dep:sqlx"]

Targets

Error model

No public error type was detected: no public item declares a type named *Error, and no public signature returns one.

Operational characteristics

No unsafe block, unsafe fn, unsafe impl or unsafe trait was found by the parser anywhere in this crate's source.

Configuration

No environment variable is read with a literal name anywhere in this crate. A variable whose key is computed at run time cannot be listed here, and is not claimed to be absent.

Related capabilities

2 workspace crates depend on this one: application-planning, foundation-test-support.

Verification

Evidence by module. How often each public module is named by something executable.

What the tests establish, by name:

• test_cascade_delete_from_encounter — tests/integration.rs
• test_cascade_delete_from_series — tests/integration.rs
• test_compute_due_date_with_absolute — tests/integration.rs
• test_compute_due_date_with_offset — tests/integration.rs
• test_create_item_for_encounter — tests/integration.rs
• test_create_item_for_series — tests/integration.rs
• test_delete_item — tests/integration.rs
• test_get_item_not_found — tests/integration.rs
• test_item_with_dependency — tests/integration.rs
• test_items_sorted_by_order — tests/integration.rs
• test_list_incomplete_items — tests/integration.rs
• test_list_items_for_assignee — tests/integration.rs
• test_list_items_for_encounter — tests/integration.rs
• test_list_items_for_series — tests/integration.rs
• test_update_item — tests/integration.rs
• test_update_status — tests/integration.rs
• test_xor_constraint_both_null_fails — tests/integration.rs
• test_xor_constraint_both_set_fails — tests/integration.rs
• test_exports — src/lib.rs
• test_compute_due_date_absolute — src/models.rs
• test_compute_due_date_none — src/models.rs
• test_compute_due_date_offset — src/models.rs
• test_planning_item_for_encounter — src/models.rs
• test_planning_item_for_series — src/models.rs
• test_planning_status_parsing — src/models.rs
• test_planning_status_terminal — src/models.rs
• test_status_roundtrip — src/postgres.rs

Documentation coverage

pie showData
    title Public items with rustdoc
    "Documented" : 9
    "No rustdoc detected" : 0

Metrics

pie showData
    title Public API by kind
    "function" : 9

pie showData
    title Rust source composition
    "Code" : 520
    "Blank or comment" : 196

Generation

Rendered by tools-corpus corpus readme from repository evidence alone, renderer schema 2, lexicon current. No model, network service or database was consulted. Regenerate with tools-corpus corpus readme --write; verify with --check.