Metztli “moon”

PAC surface at a glance

Metztli’s PAC integration is config-only. It reads exactly one endpoint, /config/metztli (columns enabled and config_json), and never queries cards, files, or the index. It registers no poca:// deep link; its intent filters are webcal, .ics, and text/calendar for device-calendar subscriptions.

The calendar config block

When the app’s app_config.json carries a calendar object, Metztli builds a data-driven cycle engine from it. Without one (or with enabled: 0) it falls back silently to the built-in Anāhuac engine.

{
  "calendar": {
    "displayName": "Our Calendar",     // default "PAC Calendar"
    "id": "our-calendar",              // default "pac-calendar"
    "epoch": "2026-03-20",             // ISO date anchoring cycle position 0
    "primaryCycleIndex": 0,
    "glyphCycleIndex": 0,              // which cycle names the day glyph
    "notes": ["…"],
    "cycles": [ {                      // required, at least one
      "name": "Day signs",
      "labels": ["…", "…"],          // required, non-empty
      "period": 20,                    // default labels.length
      "epochOffset": 0
    } ]
  }
}

Each cycle advances one label per day and wraps at its period; every day is computed from the epoch at runtime, so the PAC ships no per-day payloads.

Authoring notes

• Glyph art is local. Day glyphs come from drawables bundled in the app, keyed by Anāhuac sign names. Custom label sets render as text until matching art ships in-app.
• Day signs, trecenas, and moon phases in the default calendar are computed by built-in engines, not read from the card.
• Engine swap is reactive: inserting a card with a calendar block flips the app without a restart.