VENTEXCONNECTSECURITAS EX VIGILANTIA
Live demoTrust Center
Open Connect
Product development / public

What changed. What will be reviewed next.

The changelog records evidenced changes. The roadmap shows direction and acceptance gates—not guaranteed delivery dates.

01SITE-2026.08.02-B2026-08-02
02SITE-2026.08.022026-08-02
03SITE-2026.08.012026-08-01
SITE-2026.08.02-Bsite

Media, research and measurable website quality

Approved press assets, an honest research intake, privacy-preserving audience measurement and reproducible SEO, accessibility, performance and header checks expand the product site.

  • Press and media kit with machine-readable facts
  • Open university and research process without invented partnerships
  • Cookie-free daily aggregates without visitor identifiers
  • Individual social cards and structured data
  • Request-nonce CSP and automated quality audit
SITE-2026.08.02site

Public product transparency

Comparison, roadmap, responsible disclosure and a protected contact path expand the public product website.

  • Fair comparison matrix backed by primary sources
  • Public change history and directional roadmap
  • Disclosure policy and standards-based security.txt
  • Contact form with validation, rate limiting and SMTP delivery
SITE-2026.08.01site

Evaluation, documentation and status

The product site added a local Mission Room demo, long-form technical documentation and honest status monitoring.

  • Guided Mission Room simulator without production data
  • Six technical documentation chapters
  • Status API and RSS feed with explicit not-monitored state
  • German and English architecture whitepapers
CONNECT-2026.07.31security

Encrypted conversation preferences

Supported clients read selected conversation preferences from encrypted state. The plaintext fallback remains until the separately approved M1-D step.

  • M1-B completed in substance
  • Realtime summaries moved to encrypted reads
  • Coverage made measurable per device
  • M1-D explicitly not approved yet
CONNECT-2026.07.30operations

Reproducible release evidence

Signature verification, independent rebuild and DNS-bound key checks connect source state to the bytes actually delivered.

  • Manifest and Ed25519 signature outside the server
  • Byte comparison of the published build
  • Expected public key through an authoritative DNS channel
  • Service worker refuses unknown release files
POLICY / CHANGE CONTROL

Release communication without theatre.

An entry means the change is visible in the repository and its associated evidence. It does not automatically mean every instance has already been updated.