Skip to content

Epic: zarr serving next phase #1181

Closed
11 of 13 issues completed
Closed

Description

@neuromechanist

Epic #1095 (directory-format support: MEF3, CTF .ds, 4D/BTi; raw-vs-derived scope) closed 2026-08-22. Its cleanup, plus the serving-side work it exposed, is what's left. This epic organizes that, per Yahya's request (2026-09-01) to reorganize the zarr backlog rather than let it sprawl across unlinked issues.

Sub-issues

Backfill and correctness (finishing what #1095 started)

Serving contract roadmap (the N-series referenced in #1065 and #1178)

Transfer efficiency

Staging

Strategic connection to the NEMAR MCP server (#1065)

#1178's serving-efficiency work is not only a cost/latency fix for the browser viewer — it is a prerequisite for #1065. An MCP (or any serverless/agent) consumer of the zarr data plane needs exactly the properties #1178 describes: bounded request counts per read (so a tool call doesn't fan out into hundreds of Range requests), cacheable/deterministic byte ranges (so repeated agent queries hit the edge instead of S3), and a declared view pyramid (so a client doesn't have to probe for it). #1065's read_window/render_overview tools inherit #1178's chunk geometry directly — see the chunk-geometry comment #1065 already carries (nm000103, 4 s inner shards) predicting exactly the request-count problem #1178 measures. Fixing #1178 on the producer/edge side makes the MCP tools cheap by construction rather than by client-side workaround. Cross-referenced on #1178 directly.

Not restructuring #1065 itself — it already tracks its own phasing — but noting the dependency here since it changes how #1178 should be prioritized: the browser-viewer case and the future MCP case both need the same fix.

Explicitly out of scope for this epic

Left off deliberately, still open, still real, but tactical/ops rather than "what does zarr serving look like next":

Activity

  1. neuromechanist commented on Sep 3, 2026

    @neuromechanist
    ContributorAuthor

    Epic merged into dev via PR #1206 (regular merge, a8054de). Phases 1-10 and 12 landed; phase 11 (closeout ops: release to main, engine bump ack on Hallu, staging cron flip to dev, docs#15) is tracked in the release that follows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions