From 7a3eeece726a03fb08edba1dc2101a0604be62c7 Mon Sep 17 00:00:00 2001 From: Anthony Volk <14987227+anth-volk@users.noreply.github.com> Date: Mon, 26 Oct 2026 18:34:48 +0400 Subject: [PATCH 1/5] Describe Orrery publication without the closed authorization route docs/orrery-publication.md still named PolicyEngine/calibration-diagnostics#208 as a prerequisite for remote publication. That PR was closed unmerged, and the collector will publish Orrery graph files itself instead. Add a Status section: no upload is published today, queued jobs stay pending with their files preserved, the collector's artifact intake (PolicyEngine/microcosm-collector#12) and graph worker replace the direct upload, and the Hugging Face staged bundle holds the same files. Drop the #208 prerequisite from the configuration and migration sections. Co-Authored-By: Claude Opus 5.5 --- docs/orrery-publication.md | 28 +++++++++++++++++++++++----- 1 file changed, 23 insertions(+), 5 deletions(-) diff --git a/docs/orrery-publication.md b/docs/orrery-publication.md index e073acd931..07f197f1c6 100644 --- a/docs/orrery-publication.md +++ b/docs/orrery-publication.md @@ -38,6 +38,27 @@ under an existing publication ID. No population H5 or content-store arrays are included; only allowlisted graph declarations, execution receipts and reviewed aggregate summaries can be published publicly. +## Status + +No upload is published today. The runs application accepts an upload only +after the collector authorizes it, and the collector has no authorization +endpoint: PolicyEngine/calibration-diagnostics#208, which would have added +one, was closed unmerged. Builds still queue uploads as described above. A +queued job stays pending in the emitter's local queue, its files stay in the +preserved directory, and no retry can succeed. + +The collector will publish Orrery graph files itself instead. Builds will +submit the files to the collector's artifact intake +(PolicyEngine/microcosm-collector#12), and the collector's graph worker will +build and publish the Orrery graph files from them. The direct upload to the +runs application will then be removed. + +By default, a build queues an upload only when it also stages its artifact +bundle to Hugging Face, under `staged//`. That bundle holds the same +files, so the Orrery graph files can be rebuilt from it later. This does not +hold for an interrupted build, a build run with `--publish-orrery` without +remote staging, or a build whose Hugging Face staging failed. + ## Configuration | Setting | Source and consumer | Provisioning | @@ -48,9 +69,7 @@ aggregate summaries can be published publicly. | `XDG_CACHE_HOME` | Optional existing cache-location setting | Defaults to the user's cache directory | The separately deployed runs application retains its Vercel Blob configuration. -Authenticated production publication also requires -PolicyEngine/calibration-diagnostics#208 deployed, and the runs application's -publication API. Producer tests do not contact either hosted service. +Producer tests do not contact the runs application or the collector. No new Microcosm runtime variable or secret is required. Tests isolate ambient credentials and caches and use fake HTTP or explicit loopback services. @@ -97,5 +116,4 @@ an existing workstation, upgrade any old unversioned queue using the preceding Microcosm implementation. Versioned telemetry and graph jobs keep their existing IDs, eligibility, path and Alembic revision; do not delete a queue to migrate. No new runtime variable, credential, hosted service or infrastructure is required -by this migration. The previously required hosted authorization/API deployments -remain prerequisites for remote publication. +by this migration. From 5a8a1c6fdc56b9c82e8c8c4ea795c7fba83a898b Mon Sep 17 00:00:00 2001 From: Anthony Volk <14987227+anth-volk@users.noreply.github.com> Date: Mon, 26 Oct 2026 20:00:28 +0400 Subject: [PATCH 2/5] Name the files builds will submit to the collector, and the bundle exceptions The Status section said builds will submit "the files" to the collector's artifact intake, which reads as the Orrery graph files. Per the collector's submission contract, builds submit the graph's inputs (graph.schema.json, graph.execution.json, upstream files and the private native evidence) and the collector's Orrery worker builds graph.orrery.json itself. Also say that the staged bundle holds every file of the queued upload plus graph.execution.json, that default queuing depends on remote staging being enabled, and that the bundle is missing when Hugging Face staging did not complete, not only when it failed. Co-Authored-By: Claude Opus 5.5 --- docs/orrery-publication.md | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/docs/orrery-publication.md b/docs/orrery-publication.md index 07f197f1c6..fde0718087 100644 --- a/docs/orrery-publication.md +++ b/docs/orrery-publication.md @@ -47,17 +47,22 @@ one, was closed unmerged. Builds still queue uploads as described above. A queued job stays pending in the emitter's local queue, its files stay in the preserved directory, and no retry can succeed. -The collector will publish Orrery graph files itself instead. Builds will -submit the files to the collector's artifact intake -(PolicyEngine/microcosm-collector#12), and the collector's graph worker will -build and publish the Orrery graph files from them. The direct upload to the +The collector will build and publish the Orrery graph files itself instead. +Builds will submit the graph's inputs to the collector's artifact intake +(PolicyEngine/microcosm-collector#12): `graph.schema.json`, +`graph.execution.json`, the `upstream-.json` files and the native +evidence files, which the collector keeps private. They will not submit +`graph.orrery.json`: the collector's Orrery worker will build it from the +schema and the execution overlay and publish it. The direct upload to the runs application will then be removed. -By default, a build queues an upload only when it also stages its artifact -bundle to Hugging Face, under `staged//`. That bundle holds the same -files, so the Orrery graph files can be rebuilt from it later. This does not -hold for an interrupted build, a build run with `--publish-orrery` without -remote staging, or a build whose Hugging Face staging failed. +By default, a build queues an upload only when remote staging is enabled, and +after queuing it stages its artifact bundle to Hugging Face under +`staged//`. That bundle holds every file of the queued upload, plus +`graph.execution.json` when execution was recorded, so the Orrery graph files +can be rebuilt from it later. This does not hold for an interrupted build, a +build run with `--publish-orrery` while staging is local-only or disabled, or a +build whose Hugging Face staging failed or did not complete. ## Configuration From b5e2bb31693dfbd07f7ad63a31dcead033d1fd35 Mon Sep 17 00:00:00 2001 From: Anthony Volk <14987227+anth-volk@users.noreply.github.com> Date: Mon, 26 Oct 2026 20:55:43 +0400 Subject: [PATCH 3/5] Point the README at the graph publication status and the emitter pin The README said UK builds attempt immutable publication without saying that no upload is published today, and it linked a "deferred migration prerequisites" heading that the doc no longer has. Co-Authored-By: Claude Opus 5.5 --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 32912b3a68..232de7e68b 100644 --- a/README.md +++ b/README.md @@ -48,7 +48,8 @@ until you restart the kernel, load it by path with UK build completion automatically exports Orrery execution graphs, attempts immutable publication before Hugging Face artifact staging, and preserves -durable retry jobs and receipt snapshots. See +durable retry jobs and receipt snapshots. No upload is published today; see +[the status of graph publication](docs/orrery-publication.md#status). See [graph publication](docs/orrery-publication.md) for configuration and retry. Supported US and UK build commands start one local emitter service with separate @@ -56,8 +57,8 @@ telemetry and graph-publication workers. Microcosm supplies build metadata and graph files; the required `microcosm-emitter` package owns authentication, durable queues and delivery. Telemetry and graph publication are internal libraries in that single package, not separate installations. -This draft migration requires a published emitter release before merge; see the -[migration prerequisites](docs/orrery-publication.md#deferred-migration-prerequisites). +Microcosm pins one exact emitter release; see the +[emitter dependency](docs/orrery-publication.md#emitter-dependency). The telemetry worker reports live progress to the hosted collector when the operator's existing Hugging Face login is accepted; otherwise it retains the events locally and the build continues. This live event path is independent of the From d271b85041b57c651f8204c7dcd6013c54d3cf59 Mon Sep 17 00:00:00 2001 From: Anthony Volk <14987227+anth-volk@users.noreply.github.com> Date: Mon, 26 Oct 2026 21:06:13 +0400 Subject: [PATCH 4/5] Say the collector keeps a licensed build's Orrery graph private The Status section said the collector's Orrery worker will build graph.orrery.json and publish it. The collector's submission contract (docs/artifact-submissions.md, Disclosure, on the microcosm-collector#12 branch) says the worker records every Orrery artifact derived from a submission with licensed_data: true as private, never makes it public itself, and that it becomes public only after output clearance. UK builds use licensed microdata, so the worker will not publish their graphs. Co-Authored-By: Claude Opus 5.5 --- docs/orrery-publication.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/orrery-publication.md b/docs/orrery-publication.md index fde0718087..a9db6a2643 100644 --- a/docs/orrery-publication.md +++ b/docs/orrery-publication.md @@ -47,14 +47,16 @@ one, was closed unmerged. Builds still queue uploads as described above. A queued job stays pending in the emitter's local queue, its files stay in the preserved directory, and no retry can succeed. -The collector will build and publish the Orrery graph files itself instead. -Builds will submit the graph's inputs to the collector's artifact intake +The collector will build the Orrery graph files itself instead. Builds will +submit the graph's inputs to the collector's artifact intake (PolicyEngine/microcosm-collector#12): `graph.schema.json`, `graph.execution.json`, the `upstream-.json` files and the native evidence files, which the collector keeps private. They will not submit `graph.orrery.json`: the collector's Orrery worker will build it from the -schema and the execution overlay and publish it. The direct upload to the -runs application will then be removed. +schema and the execution overlay. The worker keeps the graph of a build that +used licensed microdata, as UK builds do, private; it becomes public only +after output clearance. The direct upload to the runs application will then +be removed. By default, a build queues an upload only when remote staging is enabled, and after queuing it stages its artifact bundle to Hugging Face under From 04820dcb1e125489cf98fca0c5091279dd6fd27e Mon Sep 17 00:00:00 2001 From: Anthony Volk <14987227+anth-volk@users.noreply.github.com> Date: Mon, 2 Nov 2026 17:03:49 +0400 Subject: [PATCH 5/5] Say that builds queue an Orrery upload only with --publish-orrery Main now leaves graph publication off unless --publish-orrery asks for it, so the status section no longer says builds queue uploads by default. Co-Authored-By: Claude Opus 5.5 --- README.md | 5 +++-- docs/orrery-publication.md | 12 ++++++------ 2 files changed, 9 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 232de7e68b..6395becbf1 100644 --- a/README.md +++ b/README.md @@ -47,8 +47,9 @@ until you restart the kernel, load it by path with ## Build progress and staging run files UK build completion automatically exports Orrery execution graphs, attempts -immutable publication before Hugging Face artifact staging, and preserves -durable retry jobs and receipt snapshots. No upload is published today; see +immutable publication before Hugging Face artifact staging when +`--publish-orrery` asks for it, and preserves durable retry jobs and receipt +snapshots. No upload is published today; see [the status of graph publication](docs/orrery-publication.md#status). See [graph publication](docs/orrery-publication.md) for configuration and retry. diff --git a/docs/orrery-publication.md b/docs/orrery-publication.md index 8689bc82f5..caa591a726 100644 --- a/docs/orrery-publication.md +++ b/docs/orrery-publication.md @@ -44,7 +44,8 @@ aggregate summaries can be published publicly. No upload is published today. The runs application accepts an upload only after the collector authorizes it, and the collector has no authorization endpoint: PolicyEngine/calibration-diagnostics#208, which would have added -one, was closed unmerged. Builds still queue uploads as described above. A +one, was closed unmerged. A build run with `--publish-orrery` still queues an +upload as described above; without it, the default, a build queues none. A queued job stays pending in the emitter's local queue, its files stay in the preserved directory, and no retry can succeed. @@ -59,11 +60,10 @@ used licensed microdata, as UK builds do, private; it becomes public only after output clearance. The direct upload to the runs application will then be removed. -By default, a build queues an upload only when remote staging is enabled, and -after queuing it stages its artifact bundle to Hugging Face under -`staged//`. That bundle holds every file of the queued upload, plus -`graph.execution.json` when execution was recorded, so the Orrery graph files -can be rebuilt from it later. This does not hold for an interrupted build, a +When a build queues an upload with remote staging enabled, it then stages its +artifact bundle to Hugging Face under `staged//`. That bundle holds +every file of the queued upload, plus `graph.execution.json` when execution +was recorded, so the Orrery graph files can be rebuilt from it later. This does not hold for an interrupted build, a build run with `--publish-orrery` while staging is local-only or disabled, or a build whose Hugging Face staging failed or did not complete.