mentu-calendar 0.1.0

Deterministic, offline, host-independent calendar scheduling engine (RFC 5545 + IANA tzdata).

mentu-calendar

Deterministic, offline, host-independent calendar scheduling for agents and services. Structured JSON in → structured JSON out, with byte-identical output on any machine.

A clean-room implementation of RFC 5545 (recurrence), RFC 8536 (TZif), and the IANA tzdata database — no ambient clock (you pass now), no host time zone (time zones are explicit), no network, no state.

Why

• Deterministic — the same input JSON produces byte-identical output JSON. Reproducible in your own CI against the published conformance vectors.
• Offline & host-independent — no network, no host clock, no host time-zone database. Zones come from a pinned IANA release (the tzdata wheel), read per-zone.
• Half-open [start, end) intervals — back-to-back events do not conflict.
• Auditable & vendorable — pure Python, Apache-2.0, zero closed binaries; installs clean and passes standard dependency scanning (pip-audit, SBOM).

Install

pip install mentu-calendar

Requires Python ≥ 3.12. Dependencies: python-dateutil and the pinned tzdata wheel.

Library

from mentu_calendar import dispatch

out = dispatch("resolve_timezone", {"zoneId": "America/Mexico_City", "instant": {"epochMs": 1736942400000}})
# {"ok": True, "result": {...}, "meta": {...}}

CLI

mentu-calendar call find_slots --input request.json   # or pipe JSON on stdin
mentu-calendar --schema [op]                          # JSON request schema(s)
mentu-calendar --self-test
mentu-calendar --version

Exit codes: 0 success, 1 operation error, 2 CLI/input error.

Operations

resolve_timezone, check_availability, detect_conflicts, find_slots, create_event_plan, reschedule_event_plan, cancel_event_plan, expand_recurrence, next_occurrence.

Mutating operations return plans/diffs only — a provider adapter performs any live writes.

MCP server

A dependency-free stdio MCP server exposes all nine operations as tools for agent runtimes (Claude Desktop, IDE agents, …):

mentu-calendar-mcp        # JSON-RPC 2.0 over stdio; each operation is a tool

Example Claude Desktop config:

{ "mcpServers": { "calendar": { "command": "mentu-calendar-mcp" } } }

Contract & conformance

The full specification is spec/SPEC.md; the versioned request schemas are in spec/schemas/ (JSON Schema draft 2020-12). Golden { input, expected } fixtures under conformance/vectors/ are the binding definition of correct behavior — run them against your build:

python conformance/run.py            # against the installed package

Correctness is additionally locked by property tests (determinism, offline, host-state independence) and differential testing against an independent implementation over thousands of randomized inputs.

Guarantees

Fully offline, no telemetry, no ambient clock, no secrets, nothing leaves the process — see COMPLIANCE.md. Security policy: SECURITY.md.

Provenance

A clean-room implementation of public standards — RFC 5545, RFC 8536, and the IANA tzdata database — built on the Python standard library (zoneinfo), python-dateutil (an independent RFC 5545 implementation), and the tzdata wheel. No proprietary code.

License

Apache-2.0 — see LICENSE and NOTICE.