Cyan Eclipse Bazaar — Terms
Version 1.0 · Effective 29 October 2026 · Cyan Eclipse Technologies LLC
Cyan Eclipse Technologies LLC ("CETech", "we") operates the Cyan Eclipse Verity Bench (the bench program historically built on Cyan Eclipse Assay and Cyan Eclipse Cupel, internal tools that are never sold or licensed), offered through Cyan Eclipse Bazaar. By ordering a bench service — a full certification bench or a scoped re-bench — you agree to these Terms. Contact: steven@cetech.ai.
1.1 A bench order buys the evaluation: the ordered product is executed against its own published claims, under the bench's published battery for its scope, and issued a sealed, scope-printed scorecard whose evidence a third party can recompute offline.
1.2 Deliverables: (a) the sealed scorecard (verdict, scope, battery identity, evidence references); (b) the evidence pack underlying it, delivered to the ordering customer; (c) publication of the verdict record in the Bazaar verdict feed under §5.
1.3 The fee is owed regardless of verdict. A failure is a deliverable of exactly the same standing as a pass. No refund, credit, or re-run right arises from an unfavourable verdict.
2.1 You pay for the evaluation, never the outcome. No fee, payment tier, subscription, or other consideration buys, influences, delays, suppresses, or softens a verdict, a battery result, a scope statement, or the publication of any of them. Findings and verdicts render identically for paying and non-paying parties.
2.2 The bench's builders do not certify their own work: the bench is operated independently of the product engineering that builds CETech's own products, and CETech's own products are benched under the same batteries and publish under the same rules as third-party products.
2.3 Referral fees and outcome-contingent pricing are refused as a matter of standing policy and form no part of any bench engagement.
3.1 Every scorecard states its scope in the record itself: what was tested, under which battery version, on which product version, under which transport (for example fixture, sandbox, hosted, live), and what was not tested. The scope statement is part of the verdict.
3.2 Quoting a verdict without its scope qualifier — in marketing, a listing, a filing, or anywhere else — is a material breach of these Terms. The only permitted short form is the verdict word together with its scope (for example "PASS — fixture transport"), never the verdict word alone where the scope was narrower than the reader would assume.
3.3 Certification, where a verdict supports it, certifies the stated scope only. A bench verdict is not a warranty of fitness, security, or compliance for any purpose outside that scope, and is not a compliance determination (see §8).
4.1 Intake. A bench runs from an intake packet: the product's published claims (the exact claim list the bench will test), the product version and access route, fixtures where the scope requires them, and known gaps the customer declares. A claim not in the packet is not tested and not implied. Incomplete packets do not start the clock; the bench's door check is mechanical and its result is receipted.
4.2 Claims are tested as published. The bench tests the product against its own published claims as they stood at intake. Editing a claim after intake does not change the battery for that run; it is material for the next run or a re-bench.
4.3 Conduct of the run. Bench execution occurs on CETech infrastructure (including sacrificial bench hosts) against fixture or sandbox transport unless the ordered scope expressly includes a hosted or live leg. The bench never tests against production third-party systems, never holds customer funds or credentials beyond the access the intake packet grants for the run, and destroys run-scoped access material at run close.
4.4 Timing. The bench issues the scorecard when the run completes and the verdict is signed. No completion date is promised in these Terms; an order page or order confirmation that states a window states the operative commitment for that order.
5.1 A verdict is never silently edited. A verdict record is replaced only by a superseding record, or withdrawn; SUPERSEDED and WITHDRAWN are real, published states in the verdict feed, and the latest record per product is the current one.
5.2 Failures publish on the same terms as passes, in the same feed, in the same form.
5.3 A customer may respond to its verdict record with a linked response (acknowledgement, fix claim, or WONTFIX), which renders beside the record. A fix claim changes no state by itself: the state changes on a re-bench (§6) whose record supersedes under §5.1.
5.4 CETech may withdraw a verdict record on its own initiative only for bench error (wrong product version, battery defect, evidence corruption), stating the reason in the withdrawal record. Withdrawal for any other reason — including customer request, payment, or pressure — does not exist.
6.1 A scoped re-bench ($150, price book §4) re-verifies the delta: the declared change and its blast radius, under the delta-bench rule. It produces its own scorecard and supersedes under §5.1 for the scope it covers; scopes it does not cover keep their prior records and dates.
6.2 A full re-bench is required, and a scoped re-bench will be refused by name, where the change is one the delta rule classifies as a full-bench event (including upstream API, data-source, or schema changes, custody or trust-boundary changes, or a change to the claim surface itself).
6.3 Re-bench fees are owed on the same terms as §1.3: the fee buys the re-evaluation, whatever it finds.
Full certification bench: $500 per product. Scoped re-bench: $150 per fix round. Cert + badge year-1 bundle ($1,500) is not sold under these Terms: its badge component is governed by a separate badge license that is not yet open (§9). Prices are as approved in the CETech price book (2026-10-26) and restated here for the order flow; the price book governs if a restatement ever drifts.
The bench evaluates products against their own published claims. It does not determine that any product complies with any law, regulation, standard, or procurement requirement, and no scorecard may be represented as doing so. Where a customer uses a scorecard in its own compliance file, the determination recorded there is the customer's, made under the customer's authority, on evidence we supply.
No badge, seal, certification mark, or display rights of any kind (display_rights: none). No listing placement, ranking, or discovery advantage on the Bazaar. No monitoring subscription (continuous monitoring for third-party listings is in preparation, is not sold under these Terms, carries no price here, and has no promised start date). No licence to the bench's own tools — Cyan Eclipse Assay and Cyan Eclipse Cupel are internal tools and are never sold, licensed, or delivered.
10.1 What CETech warrants. The run was performed as described in §4; the sealed report is the run's actual output; the verdict record has not been edited after issuance (§5.1).
10.2 Limits. Our total liability for any claim arising from a bench order is capped at the amounts the claimant paid CETech for that order. We are not liable for decisions any party makes in reliance on a verdict beyond its stated scope, or for indirect or consequential losses. Nothing here limits liability that cannot be limited under applicable law.
10.3 Governing law. The laws of the State of Florida (baseline adopted 2026-10-27).
10.4 Changes. Revisions are versioned, dated, and archived; a revision never alters the terms of an order already placed or a verdict already issued. Material revisions bind future orders on notice; orders in flight complete under the version they were placed under.
Cyan Eclipse Technologies LLC · Tallahassee, Florida · steven@cetech.ai