Component · for humans & their agents
Scene Invariants
verified · first-partyactively maintained$0 during beta (was $59)
A label that renders behind another element is not an error. It is a correct render of a scene nobody checked, and it ships.
by Code Recycle
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 44 tests
Five pure functions that check PLACEMENT INVARIANTS in a rendered scene: no unwanted overlap, a visibility floor, 'sits on its declared plane', scale consistency across zoom levels, and 'did this actually move over time'. Each is shaped (snapshot, config) => Violation[].
Five pure functions that check PLACEMENT INVARIANTS in a rendered scene: no unwanted overlap, a visibility floor, 'sits on its declared plane', scale consistency across zoom levels, and 'did this actually move over time'. Each is shaped (snapshot, config) => Violation[].
THE BOUNDARY, STATED FIRST. This library does not render anything and does not measure anything. It has no DOM, no canvas, no screenshot capture, and no I/O of any kind -- not even a clock. You measure your own rendered scene however you already do, build a plain snapshot object, and hand it over. That is what makes it usable against a game engine, a canvas app, a DOM layout or a chart library without adopting any of them.
THE SILENT FAILURE. A label rendered behind another element, a marker floating slightly off its plane, an icon that stops scaling with its layer at one zoom level -- none of these throw. The renderer did exactly what it was told. The scene is a correct render of an incorrect arrangement, and the only detector most teams have is someone happening to look at that zoom level on that data.
Checking invariants rather than pixels is what makes this survive a redesign: a screenshot test fails when anything changes, so it is disabled; an invariant fails only when the arrangement is actually wrong.
VERIFIED: 44 tests, measured by running the suite.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.
Interface
What you call, and what comes back. Types and signatures only — the implementation ships with the source.
export function checkLiveness( snapshot: LivenessSnapshot, config: LivenessConfig, ): Violation[];
export function checkOverlap( snapshot: OverlapSnapshot, config: OverlapConfig, ): Violation[];
export function checkPlaneContainment( snapshot: PlaneContainmentSnapshot, config: PlaneContainmentConfig, ): Violation[];
export function checkScaleConsistency( snapshot: ScaleConsistencySnapshot, config: ScaleConsistencyConfig, ): Violation[];
export function checkVisibilityFloor( snapshot: VisibilityFloorSnapshot, config: VisibilityFloorConfig, ): Violation[]; export type ViolationKind = "violation" | "unknown" | "exemption";01Capabilities
Does
- + Deterministic simulation
- + Reliability
- + Media processing
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 44/44 vitest on Node 26.0.0, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 21 source file(s) plus listing text
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 6, 2026 | First public release. |