Page 1 of 1

VRP Private Pilot Application

# VRP PRIVATE ENGINEERING EVALUATION ## INVITATION ONLY --- # STATUS The public Pilot intake has concluded. VRP is no longer accepting open public Pilot applications. Engineering evaluation is conducted only by invitation and case-by-case technical review. This policy exists to maintain engineering quality, protect evaluation capacity, and ensure that reviews remain technically meaningful. Public architecture remains available. Protected runtime implementation remains private. --- # CURRENT PROGRAM STATUS VRP_PUBLIC_APPLICATIONS=CLOSED GENERAL_PILOT_INTAKE=CLOSED INVITATION_ONLY=ENABLED ENGINEERING_REVIEW=CASE_BY_CASE ENGINEERING_CAPACITY=LIMITED PROTECTED_RUNTIME=PRIVATE PROTOCOL_DEVELOPMENT=ACTIVE PUBLIC_SPECIFICATION=AVAILABLE --- # BEFORE REQUESTING EVALUATION Organizations are expected to review the public engineering specification before requesting an evaluation. https://github.com/Endless33/VRP-specification" target="_blank">https://github.com/Endless33/VRP-specification The public specification documents: • protocol architecture • continuity model • session semantics • transport independence • deterministic runtime behavior • protocol invariants • state-machine design • recovery model • replay protection • authority handling • evidence-first validation • security boundaries • threat model • integration concepts • engineering rationale The public documentation is intended to support independent architectural review without exposing the protected runtime. --- # ENGINEERING READINESS VRP has reached a stage where architectural principles, public specifications, validation methodology, and engineering evidence are available for independent review. Current development is focused primarily on runtime maturation rather than architectural redesign. Current priorities include: • runtime hardening • deterministic execution • long-duration stability • recovery behavior • authority handling • replay protection • evidence architecture • adversarial validation • performance profiling • protocol evolution Public architecture is considered stable. Protected implementation continues to evolve. --- # INITIAL CONTACT Organizations that believe VRP is relevant to their infrastructure may introduce themselves by email. jumpingvpn@proton.me Please include: • organization name • company website • engineering contact • deployment environment • continuity challenges • evaluation objectives • why VRP is relevant Please do not include: • production credentials • private keys • proprietary source code • confidential infrastructure information • regulated customer data --- # IMPORTANT Sending an email: • does not create a Pilot application • does not reserve engineering capacity • does not establish review priority • does not guarantee a response • does not guarantee future participation • does not create a commercial relationship Engineering review is discretionary. --- # IF AN ORGANIZATION IS SELECTED VRP may, at its sole discretion: • request additional technical information • schedule engineering discussions • provide evaluation material • define validation boundaries • issue organization-specific documentation • decline further participation Selection is based on engineering relevance, technical alignment, and available engineering capacity. Submission order does not determine selection. --- # PROTECTED RUNTIME The VRP Protected Runtime remains private. Public documentation does not grant access to: • protected runtime implementation • internal algorithms • synchronization mechanisms • proprietary continuity logic • protected source code • unpublished architecture • production deployment rights • licensing rights • ownership of VRP intellectual property Observable protocol behavior may be evaluated. Protected implementation remains protected. --- # PUBLIC MATERIAL Public repositories and engineering documentation remain available. Public availability should not be interpreted as an open Pilot invitation. Documentation may be: • expanded • updated • reorganized • archived • replaced • made private without prior notice. --- # FUTURE PARTICIPATION If external engineering evaluation becomes available in the future, the process may differ from previous programs. Future participation may require: • invitation • engineering qualification • identity verification • infrastructure readiness • defined evaluation scope • security review • updated legal agreements • revised commercial terms Previous contact does not establish future priority. --- # FINAL STATUS VRP_PUBLIC_APPLICATIONS=CLOSED GENERAL_PILOT_INTAKE=CLOSED INVITATION_ONLY=ENABLED ENGINEERING_REVIEW=CASE_BY_CASE ENGINEERING_CAPACITY=LIMITED PUBLIC_SPECIFICATION=AVAILABLE PROTECTED_RUNTIME=PRIVATE PROTOCOL_DEVELOPMENT=ACTIVE --- # VRP — VEIL ROUTING PROTOCOL Public Engineering Specification https://github.com/Endless33/VRP-specification Evaluation Status **Invitation Only** Engineering Status **Active Development** Public Architecture **Available** Protected Runtime **Private**

────────────────────────────

APPLICATION REQUIREMENTS

Applications should be submitted using accurate organizational information.

Applicants are expected to provide truthful contact details and represent the organization they identify.

Requests submitted using intentionally false identities, misleading organizational information, or fraudulent contact details may be declined without further review.

Submission of an application does not create any obligation for either party.

The project reserves the right to decline, suspend, or discontinue Pilot discussions at any stage.

────────────────────────────

PILOT CONFIDENTIALITY

Technical discussions may require mutual confidentiality before access to non-public materials is granted.

The public Validation Kit is intended for independent evaluation.

The protected runtime, internal engineering documentation, and proprietary implementation are not part of the public evaluation.

────────────────────────────

ENGINEERING EXPECTATIONS

The Pilot is intended for organizations performing genuine technical evaluation.

It is not intended for anonymous technology collection, unrestricted source-code requests, or speculative inquiries unrelated to deployment.

Constructive technical questions are welcome.

Engineering collaboration is encouraged.

────────────────────────────

PROJECT RESERVATION

Pilot capacity is intentionally limited.

The project reserves the right to modify Pilot availability, pricing, licensing terms, and evaluation priorities without prior notice.

Acceptance into the Pilot Program is determined solely by the project after technical review.

────────────────────────────

NEXT STEP

If your organization is interested in evaluating VRP for a real deployment, submit your request below.

Thank you for your interest.

We look forward to hearing from serious partners.

────────────────────────────

NO OBLIGATION

Submission of an application does not create any contractual relationship.

No organization is entitled to pilot participation.

No organization is entitled to technical support.

No organization is entitled to future access.

The VRP author may approve, reject, suspend, terminate, postpone, or modify any pilot participation at any time, with or without notice, and at the sole discretion of the VRP author.

────────────────────────────

IMPORTANT

The evidence is public.

Some repositories are public.

Organizations evaluating VRP already have access to sufficient public material for technical review.

If a flaw exists, present it.

If additional validation is required, apply.

This process exists for evaluation.

Not indefinite observation.

Not silent monitoring.

Not passive collection of public evidence.

The pilot window is controlled by the author.

Access is not guaranteed.

Acceptance is not guaranteed.

Response is not guaranteed.

Future access is not guaranteed.

────────────────────────────

CONTINUITY OF DEVELOPMENT

Validation continues.

Development continues.

Testing continues.

VRP will continue to evolve regardless of pilot participation.

Organizations interested in evaluating continuity-first networking should apply before July 31, 2026.

After that date, pilot availability, pricing, participation rules, evaluation scope, and access conditions may change without notice.

────────────────────────────

Payment

Commercial payment instructions are provided only after a Pilot application has been reviewed and approved.

Available payment methods may include:

• International bank transfer

• Cryptocurrency (BTC, ETH, LTC)

• Other methods by agreement

Authorized Application — Required Acknowledgements

I confirm that my organization received explicit written authorization from the VRP Program to complete this form, and that the submitted authorization reference is valid, current, organization-specific, and non-transferable.

I understand that submission of this form does not guarantee acceptance, a response, scheduling, pricing, Pilot capacity, licensing, access to the Protected Runtime, or any future commercial relationship.

I confirm that I am authorized to represent the identified organization and that the organization, representative, sponsor, intended beneficiary, evaluation purpose, and all third parties involved have been disclosed accurately and completely.

I understand that this application does not grant source-code access, ownership, exclusivity, production-deployment rights, redistribution rights, sublicensing rights, transfer rights, reverse-engineering rights, or access to protected implementation internals.

I confirm that the requested evaluation is intended solely for legitimate technical validation and not for unauthorized extraction, reproduction, replication, redistribution, competitive reconstruction, circumvention, or misuse of protected VRP components or evaluation materials.

I understand that false, incomplete, inconsistent, misleading, or unverifiable information, unauthorized submission, undisclosed third-party involvement, or violation of evaluation boundaries may result in rejection, suspension, or termination without a detailed explanation.

VRP Private Pilot Application

Authorized Application — Required Acknowledgements

Failure / Disruption Scenarios

Expected Operational Value

Evaluation Goals

Target Environment

Company / Organization

Contact Email