VENTEX PILOT / PUBLIC OPERATING KIT

From interest to a controlled field trial.

A complete operating set for selection, kick-off, a 30-day evaluation and an evidence-based final decision. Publicly usable and deliberately excluding live operational or classified data.

PUBLIC RELEASE / 2026.08SECURITAS EX VIGILANTIAWorking templates, not legal advice, certification or operational approval
02 / OPERATING MODEL

One system across the complete pilot lifecycle.

01

Qualify

Evaluate workflow, team, data class, learning value and ownership before issuing an invitation.

02

Bound

Confirm charter, roles, critical workflow, targets, stop criteria and permitted test data in writing.

03

Observe

Record task success, assistance, control integrity, reproducibility and impact separately.

04

Decide

Continue, correct or stop with an owner, deadline and next measurement.

03 / OUTREACH

Reviewed outreach templates

Ready to adapt, never intended for indiscriminate bulk outreach. Every message needs a concrete recipient-specific reason.

OUT-01 / ORGANISATION

Organisation or security provider

Subject: Controlled 30-day pilot for secure team communication

Hello [Name],

VENTEX Connect is a European-oriented communication platform for operational teams. For the next controlled cohort we are looking for two to ten active participants and one bounded communication workflow.

The pilot uses only synthetic, anonymised or non-sensitive internal test data. Before the first sign-in we define the objective, metrics and stop criteria. The result is a documented Continue, Correct or Stop decision - not an audit or blanket production approval.

If [recipient-specific workflow] is relevant to your team, I would be glad to send the two-page overview or spend 20 minutes checking whether the use case is suitable at all.

Kind regards
Ramon Galiano
VENTEX Connect
SECURITAS EX VIGILANTIA
OUT-02 / RESEARCH

University or research group

Subject: Bounded research pilot for secure operational communication

Dear [Title Name],

VENTEX Connect is examining how identity, device change, revocation and communication workflows can be evaluated through a controlled messenger pilot. We are not seeking an endorsement, but critical methodological feedback.

The public 30-day approach separates expectation, observation, impact, reproducibility and decision. Sensitive live data is excluded; participation must not be presented as institutional approval.

Could this be relevant to [department] as a student evaluation, review or bounded test case? I would be glad to provide the complete playbook and research boundary.

Kind regards
Ramon Galiano
VENTEX Connect
OUT-03 / FOLLOW-UP

Respectful follow-up

Subject: Brief follow-up on the VENTEX communication pilot

Hello [Name],

One brief clarification regarding my message from [date]: this is not a proposal for immediate production use. It is a 30-day, single-workflow evaluation with synthetic data, documented stop criteria and a written conclusion.

If the timing is not right, no reply is needed. If [specific reason] may be relevant, I can simply send the pilot overview without any meeting obligation.

Kind regards
Ramon Galiano
04 / CHARTER

What must be decision-ready before the first sign-in

  • One falsifiable pilot claim
  • Accountable Lead, Pilot Lead, Security Owner and active participants
  • One core workflow with start, finish, target and safe fallback
  • Permitted and excluded data classes
  • Stop criteria, escalation and restart authority
  • Retention, deletion and access to evidence
  • A fixed Continue, Correct or Stop decision date
05 / INTERVIEW

Interview without leading questions

  1. 01What were you trying to achieve at that moment?
  2. 02How did you know the step was complete?
  3. 03Which information or feedback was missing?
  4. 04What alternative would you have used in day-to-day work?
  5. 05Could the issue be reproduced, and under which conditions?
  6. 06What would the real-world impact be: inconvenience, delay, wrong decision or security boundary?
06 / EVIDENCE MATRIX

A finding is more than feedback.

EXPECTED

Pre-recorded state or control effect

OBSERVED

Visible behaviour with time and context

IMPACT

Effect on task, control and decision

REPRODUCED

Repeatability, environment and counter-check

DECISION

Accept, correct, retest or stop

07 / DECISION RECORD

The conclusion creates a decision, not a marketing slide.

The report records sample, system version, data class, metrics, deviations, open blockers and boundaries. A case study is published only with separate approval, anonymises observations and does not conceal negative outcomes.

Start pilot application