Cyan Eclipse Press

Agent-native static-site publish pipeline — R2-shelf publishing with zip-permission and timestamp forensics baked in; runs both production sites today.

In developmentToolNo bench verdict recordedPublishing Infrastructure

Vendor: Cyan Eclipse Technologies · Platforms: CLI pipeline (local)

What it does

Publishes to an R2 shelf with a signed manifest; the server-side cron pulls and verifies — shelf manifest listing is checked after every publish
Overwrite-only sync discipline: hand-maintained repo-only files are never deleted by a publish
Productizing as slate item T3; runs in production in-house today as deploy-pipeline/publish.py — the hosted tier is later

Problems it addresses

My agent-built site deploys by hand and every deploy risks a permission or staleness surprise
I need a publish step that proves what landed, not one that hopes

Not tested

Standalone product certification — this is a real in-house artifact being productized (connectors/tools slate T-series); no Test Bench card exists for it as a standalone product yet, and none is claimed

Evaluation-intake listing

This listing records the tool's place in the Bazaar's evaluation and monitoring pipeline, with the evidence gathered so far printed above — verdict, scope, and not-tested items included. It is not sold on this site, and its presence in the catalog is not a claim beyond that evidence. The service behind every verdict is the bench: what a bench run buys →