Silentlapse

Organizations track certificates, insurance, licenses and contracts by expiration date, yet many AI and software trust artifacts lose relevance when the underlying service changes without the artifact's date changing. A vendor may replace a model, add a subprocessor, change a training practice or alter a product version while the old model card, impact assessment or contractual review remains on file. The supplied research confirms a date-driven register with a free five-record tier, a $19 monthly starter and $49 monthly professional plan; these are observed market references, not fixed product pricing. It also confirms version-binding primitives and finds no product that binds trust evidence to a vendor's declared service version and detects non-date drift. Silentlapse creates a many-to-many binding among vendor, service, component, version, deployment, artifact, covered entity, control scope and observation period. It watches only approved sources and records exact observations, capture time, confidence, contradiction and source rights. A version change does not automatically invalidate every artifact: the system produces a potential scope-break candidate and routes it to the artifact owner, legal, security, privacy or procurement reviewer. Declaration, observed change, entity match, candidate, qualified disposition, remediation, replacement evidence, vendor acceptance and downstream risk decision remain separate. A signed credential or transparency-log entry proves integrity and issuance of a payload, not truth, completeness, current applicability or operating effectiveness.

A vendor-risk, security, privacy, legal or AI-governance leader at an enterprise managing trust evidence for many changing software and model services.