Cyan Eclipse Stocktake

Catalog / manifest / storefront consistency auditor — the drift checker that keeps this Bazaar at drift=0, productizing as a CLI + CI tool.

In developmentToolNo bench verdict recordedCertification & Testing

Vendor: Cyan Eclipse Technologies · Platforms: CLI (local), CI action (planned)

What it does

One source of truth (the scorecard ledger) checked against every surface that repeats a verdict: catalog entries, product manifests, README tables, storefront bench lines
Machine-safe fields sync automatically; prose stays human-owned and is verified, never rewritten
Runs at every Eclipse publish pass — passes 1–4 all closed at drift=0; the discipline is the product: a catalog that contradicts itself is a defect, not a typo
Productizing as slate item T4 (CLI + CI action); runs in-house today as bazaar-mcp/sync_verdicts.py

Problems it addresses

My catalog says certified, my README says pending, my storefront says nothing — which is true?
Every surface repeats my product's status and they drift apart between releases

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 →