A prospective route for existing recipients

An existing recipient can request clearly identified terms for future use from Е-САЛЮШЪНС ЕООД (e-Solutions EOOD), UIC 175177528, the Stella Ops Licensor. Use the published legal contact, legal@stella-ops.org, with subject Stella Ops - prospective terms for an existing copy.

This route does not charge for or characterise prior use. It does not require you to concede which licence governed a copy you already hold. Accepting a new agreement does not establish that you accepted it, BUSL restrictions, fees, an indemnity, a liability cap or a Sofia forum previously. The Customer Agreement’s section 2.1a expressly preserves that distinction.

This page describes a process, not an automatic permission grant, an invoice, or a settlement of historical claims. Publication of this page does not itself create customer acceptance.

1. Identify the prospective request

Provide the Customer’s legal entity and registration identity, the representative’s business contact, and the release/repository and immutable image digest if available. A mutable tag alone may identify several different copies; if the digest is unknown, request help identifying the copy before terms are assigned to it. State the intended future use and requested start date.

You do not need to admit a prior breach or accept a legal characterisation of past use. Do not send application logs, trust packs, credentials or operational evidence for this request. Any separate support-data transfer requires the Agreement’s section 8 basis first.

2. Select a clearly identified route

Route	What the Licensor must identify before acceptance
Corrected replacement release	The replacement version and immutable digest, its complete applicable licence and notice materials, the future permissions offered, and any prospective fees/support terms. A candidate awaiting publication is not an available release.
Prospective permission for the existing copy	The exact existing copy and an expressly agreed prospective permission instrument/order, with its scope, effective date and identified terms. Merely naming the Customer Agreement or today’s canonical BUSL text does not select the permission that governed the historical copy.

The Licensor contract owner confirms the offered permission and any commercial terms. The Customer Agreement does not by itself rewrite the copyright licence on an earlier copy. A separate permission instrument or agreed order must say what it grants from its prospective effective date; it must not say that the recipient received or accepted those terms when they originally acquired the copy. Third-party components retain their own applicable terms.

3. Receive the complete offer before accepting

The offer identifies:

The Customer and Licensor, release/digest and chosen route.
The permission instrument, exact text/version/digest and prospective effective date.
The issued Customer Agreement and its identified Schedule 2, both versions and full digests.
Future fees, entitlements, term, support and applicable documentation, or an explicit absence of a paid commitment where appropriate. No retrospective fee or charge for prior use is introduced.
The acceptance channel and receipt event, delivery method and records-retention arrangements.

The effective date must not precede the acceptance event used for this prospective arrangement. The Customer can open, save and reproduce the complete terms before becoming committed. Downloading a replacement or paying a merchant alone is not the retained contractual record.

4. Accept and retain prospectively

An authorised Customer representative affirmatively accepts the identified package through the acceptance procedure. The Licensor retains attributable evidence and delivers the accepted texts and receipt to the Customer. Where a merchant cannot retain versions/digests, use the Licensor-controlled fallback before the transaction is committed.

The record identifies the prospective effective date through its accepted order and permission instrument. Preserve the previous-copy identification separately; do not overwrite it with the replacement digest. Neither the receipt nor its wording may backdate acceptance or imply that a newly attached notice proves what a recipient received earlier.

5. Existing rights and historical questions remain separate

This process neither declares an earlier copy public domain nor declares that every earlier recipient lacked lawful use rights. It does not waive historical claims, confirm earlier permissions or settle a historical dispute. Any such arrangement needs its own express authorisation and separate text; it must not be hidden in this prospective process.

Declining this offer does not itself determine the recipient’s existing rights. Nothing in this process authorises disabling an already delivered copy. The Agreement’s section 9.5 preserves that boundary. A question about a particular historical copy must be assessed on its own evidence.

Operator completion check

The Licensor contract owner checks the proposed offer and retained record against each condition:

Check	Required result
Prior-use fee	None; no retrospective charge introduced by this route.
Prior-use characterisation	No admission, concession or determination required.
Permission for future use	Expressly identified; not inferred from a current mutable repository page.
Timing	Prospective effective date at or after the recorded acceptance event.
Customer Agreement package	Both document versions and full digests retained and validated.
Historical claim release/settlement	Absent from this route; separately authorised if ever requested.
Delivery and custody	Accepted package and receipt delivered; independently retained by the Licensor.

Do not mark the route exercised for a real recipient on the strength of this procedure or a synthetic example. Completion requires that recipient’s attributable prospective acceptance.