Module due 

The due-brief (first-author-path plan 08): a schema declares its deadline axis (memstead_schema::DueAxis), the engine renders “what is due next” as one deterministic markdown brief.

Deterministic given (store, today): no model call, no scoring — filter, sort, render. The only environmental input is the current date, taken once per invocation and passed in (injectable in tests). Ordering: overdue first, then ascending by date, ties broken by entity id. The renderer lives here so the CLI and UniFFI serve byte-identical content (the projection-brief precedent); there is deliberately no MCP tool — briefs are the CLI/app family.

Read-only mounts participate: a due date in an installed compliance mem is precisely the multi-stakeholder case, and a brief is a read surface. Third-party entries carry their origin label and render as quoted data — a stranger’s mem states a deadline, it does not instruct.

Enums

DueWindow

A parsed relative window: <N>d days, <N>m calendar months, <N>y calendar years.

Constants

DEFAULT_DUE_WINDOW

The default window applied when --within is omitted — stated in the CLI help and the changelog rather than unbounded.

Functions

civil_from_days_pub

Public epoch-days → civil-date conversion for callers that derive “today” from SystemTime (the UniFFI surface). Same algorithm the window math uses.

parse_due_window

Parse a relative window (90d, 6m, 2y). The error names the accepted forms — the caller wraps it in its surface’s typed envelope.