Stella Ops Customer Agreement

Version: 1.0.0 · Status: ISSUED. Adopted for release by the manufacturer of record on 2026-09-16 (adoption record). This document is the Q-16-ruled instrument (full-customer-agreement-now, owner 2026-08-25; receipt in Q-16 settlement record).

Issued is not accepted. This version may be presented to a customer. It becomes operative against that customer only when they affirmatively accept this released, versioned copy under §11, and the acceptance record must carry the version and full SHA-256 of both this document and the Schedule 2 document it identifies.

What contractual effect the operator terms have before that, stated once. The eIDAS operator terms have contractual effect to the extent they are validly incorporated into an agreement accepted by the Customer. Before that acceptance, their publication describes product requirements and the intended responsibility allocation; publication alone does not establish the Customer's agreement to that allocation. The distinction matters most for recipients who obtained a copy of the Licensed Work anonymously.

Support must not request customer logs or evidence without a separately documented confidentiality/data-protection basis (§8.2).

Review status, stated precisely because the words have defined meanings here. Counsel reviewed the complete operative text on 2026-09-15 (round 2) and found the principal architecture sound and the liability-cap defect cured, while declining to issue the then-current text: "I would nevertheless not issue this exact 0.2.0-draft." Every correction it identified is applied here.

Both review rounds are ASSESSEDand not COUNSEL-REVIEWEDas decisions/README.md defines those terms: no named, identified legal professional has reviewed this operative text, and the round-1 reviewer expressly declined to be recorded as satisfying that criterion. Release rests on the manufacturer of record's own decision, which is what ADOPTED means in the same table. That is a deliberate, recorded choice and not an oversight — counsel corrected the belief that it could not be: "My earlier statement that I was not providing a signed advocate's opinion did not mean that such an opinion is generally a statutory precondition to forming an ordinary B2B software agreement." Professional-signoff governance is kept out of this instrument.

Two clauses settled by owner decision at issue, both recorded in the adoption record: §7.2(d) is mutual rather than Licensor-only, restoring counsel's bilateral drafting; and §7.2(b)'s fee base now includes separately priced support, so a support-paying customer is not left with a cap of zero.

Drafting provenance: the section plan and Schedule 1 are counsel's, from the 2026-08-23 reply; §§9a, 10, 11.4 and the Schedule 2 identification follow the 2026-09-15 round-1 reply; the liability, precedence, survival and notices corrections follow round 2.

1. Parties and contracting structure

1.1 Licensor. Е-САЛЮШЪНС ЕООД (e-Solutions EOOD), a company registered in Bulgaria, UIC (EIK) 175177528 ("Licensor"). The chain-of-title confirmation for the Stella Ops work is recorded in busl/README.md(Q-18, owner 2026-08-23).

1.2 Customer. The legal entity identified in the acceptance record under §11 ("Customer").

1.3 Merchant of record. Where an order is processed through Cleverbridge, Cleverbridge acts as reseller/merchant of record for that purchase transaction. Licensor is the contracting party responsible for the software licence and for the obligations expressly assumed under this Agreement. Cleverbridge's role, and its rights and obligations concerning the purchase transaction, are governed by the applicable transaction terms and by mandatory law. Nothing in this Agreement excludes an obligation independently owed by Cleverbridge. The licence to the Licensed Work is granted by Licensor.

2. Licence incorporation and precedence

2.1 The "Licensed Work" is the Stella Ops software as delivered to Customer, licensed under the Business Source License 1.1 as shipped with that copy (busl/) and, where applicable, a separate commercial licence or Additional Use Grant agreed with Licensor.

2.1a Previously delivered copies. Nothing in this Agreement determines which licence governed a previously delivered copy of the Licensed Work merely by describing the Licensed Work as BUSL-licensed. Rights in such a copy remain subject to the applicable law and to any licence or agreement validly applicable to that copy.

2.2 Order of precedence, highest first: (a) a signed order form or commercial licence naming this Agreement; (b) this Agreement including its Schedules; (c) the BUSL-1.1 licence text accompanying the delivered copy; (d) the product documentation. Nothing in this Agreement modifies the BUSL-1.1 text or reduces the copyright permissions it grants.

2.2a Subject-specific precedence, and the body-versus-schedule rule. A separately agreed confidentiality or data-protection instrument governs conflicts on its expressly covered subject matter, subject to mandatory law. It changes the liability allocation in §7 only where the parties expressly agree that change. Between the body of this Agreement and a Schedule, the body governs except where a Schedule is expressly given priority on its subject matter — as Schedule 1 is for responsibility for Operator Material (§3.1) and Schedule 2 is for the eIDAS product boundary (§4.1). A Schedule's priority on its own subject matter does not extend to the formation, amendment or liability provisions of this Agreement.

2.2b What an order can and cannot vary. An order varies Licensor's obligations only to the extent expressly agreed between Licensor and Customer. A transaction record generated by a merchant of record does not vary them merely by naming this Agreement.

2.3 Order, fees and entitlements. The product, licence entitlement, term and fees for a purchase are those identified in the accepted order or other transaction record for that purchase. This Agreement does not itself set fees or payment terms, and does not vary the payment obligations in the applicable transaction terms; where those terms and this Agreement address different subjects, each governs its own.

2.4 The complete contractual package. For a given purchase the contractual package consists of this Agreement with Schedules 1 and 2 as identified in it, the accepted order or transaction record under §2.3, the BUSL-1.1 licence text accompanying the delivered copy, and any separately agreed confidentiality or data-protection instrument (including any arrangement under §8.4). Conflicts are resolved by §2.2. This clause does not displace, vary or erase the merchant of record's separate contract with Customer, and does not affect rights already granted under a licence accompanying a copy already delivered.

3. Operator-supplied material

3.1 Customer's selection of providers, lawful acquisition of trust material, rights, confidentiality and data-protection responsibilities are governed by Schedule 1 (Operator-Supplied Trust Material and Evidence), which prevails over inconsistent product documentation on those subjects.

4. Product boundary

4.1 In performing the eIDAS functionality, the Licensed Work performs local technical validation only. This clause describes that functionality and does not characterise or warrant any other function of the Licensed Work. It is not a qualified trust service, does not certify providers or material, and does not determine the legal effect of any signature, seal, timestamp, item of evidence or transaction. The operative boundary statements for eIDAS-configured deployments are those of Schedule 2 (eIDAS Operator Terms) as identified in that Schedule, and they prevail over any summary or paraphrase of them in this Agreement. The identified, accepted text of Schedule 2 governs; no repository test, and no later version of one, determines the content of the contract.

4a. Defined terms used in the warranties

4a.1 "Documentation" means the official technical documentation identified for the applicable software release in the accepted order or in the release package for that release, together with any changes subsequently agreed under §11.4.

4a.2 "Supported version" means a release identified as supported for the Customer in the accepted order or under the support or lifecycle policy identified in it. Where neither identifies one, the release delivered to Customer is the supported version for the purposes of §§5.2 and 6.1.

5. Operational responsibilities

5.1 Customer operates the deployment and is responsible for: configuration; the source, versioning and maintenance of trust-material and update packs; access control to the deployment and its evidence stores; the system environment (hardware, OS, network, container platform); and the retention and export regimes Customer applies to evidence the deployment produces.

5.2 This clause does not reduce Licensor's obligation to perform the local technical checks expressly described in the Documentation when a supported version of the Licensed Work is correctly configured.

5.3 Support and maintenance. Any support, maintenance or service-level commitment applies only as defined in the accepted order or in a separate support document identified in it. This Agreement does not create a service level, and no support commitment is implied by this Agreement alone.

6. Warranties and disclaimers

6.1 Licensor warrants that a supported version of the Licensed Work, correctly configured, performs the local technical checks expressly described in the Documentation in all material respects.

6.2 Customer gives the warranty of rights in operator-supplied material set out in Schedule 1 clause 3. That warranty is central to the reference-only-no-vendoring allocation and is given to Licensor contractually.

6.3 Except as stated in §6.1 and to the maximum extent permitted by applicable law, the Licensed Work is provided "AS IS" without further warranty, and the Schedule 1 clause 8 disclaimer applies to all operator-supplied material.

7. B2B indemnity and liability allocation

7.1 Indemnity. The Schedule 1 clause 9 B2B indemnity applies. Its exception — that the indemnity does not apply to the extent a claim was caused by Licensor's breach of this Agreement, wilful misconduct or other liability that cannot lawfully be excluded — limits the Customer's indemnity obligation. It is not, and must not be read as, an exclusion of every Licensor breach from the limitation of liability in §7.2. Reimbursement of a fine or penalty under that indemnity is recoverable only to the extent such reimbursement is permitted by the law applicable to that sanction.

7.2 Limitation of liability. Subject to §7.3 and to the maximum extent permitted by applicable law:

(a) Licensor's aggregate liability arising out of or in connection with this Agreement, for all claims taken together, is limited to the fees paid or payable for the Licensed Work for the twelve (12) months preceding the first event giving rise to liability. It is one combined limit for the Agreement, not a separate limit per claim, per order or per event.

(b) For that purpose, fees include amounts paid for the Licensed Work through a merchant of record or other authorised reseller, so the cap operates identically however the purchase was transacted, and include fees paid or payable for separately priced support or other services supplied under this Agreement.

(c) Where no fees are paid or payable within the fee base specified in this clause, including qualifying free and evaluation use, the monetary cap under this clause is zero, subject always to §7.3 and any other mandatory restriction on limiting liability.

(d) Neither party is liable to the other for indirect or consequential loss. This exclusion is mutual and applies to Customer and Licensor alike.

(e) Clause (d) is not an exclusion of all loss of profit. A loss of profit that is a direct consequence of a breach remains recoverable so far as the law applicable to the claim allows, subject to its requirements of causation and foreseeability.

(f) Clause (d) does not reduce any amount payable by Customer under the Schedule 1 clause 9 indemnity. That indemnity is a primary obligation to meet defined third-party claims, not a claim for damages between the parties, and a sum falling within it is payable whether or not it would otherwise be characterised as indirect or consequential loss.

7.3 Liability that cannot be limited. Nothing in this Agreement excludes or limits liability for intentional misconduct or gross negligence, or for any other liability that applicable law does not permit to be excluded or limited. Article 94 of the Bulgarian Obligations and Contracts Act voids an advance agreement excluding or limiting liability for intent or gross negligence, and this clause states that result expressly rather than relying on the general saving above. This clause prevails over every exclusion or limitation in this Agreement and its Schedules, including §7.2 and Schedule 1 clauses 8 and 9. References in this Agreement and its Schedules to "wilful misconduct" and to "intentional misconduct" have the same meaning and are read as one category. Nothing in this Agreement affects a right or power belonging to a person who is not a party to it, or the powers of a competent authority.

7.4 Indemnity administration. A party seeking indemnity shall notify the other without undue delay of the claim, shall not admit liability or settle the claim without the indemnifying party's written consent, and shall give the indemnifying party control of the defence and reasonable cooperation at the indemnifying party's cost. Failure to notify relieves the indemnifying party only to the extent it is prejudiced by the delay.

7.5 Limits on the indemnifying party's control. The indemnifying party may not settle a covered claim without the indemnified party's prior written consent where the settlement admits fault on its behalf, imposes a non-monetary obligation on it, or fails to provide an effective release of the covered claim. Consent shall not be unreasonably withheld for a settlement that is fully funded by the indemnifying party and provides an unconditional release without an admission or non-monetary obligation. These procedures do not prevent either party from meeting a procedural deadline, complying with a legal duty, responding to a competent authority, or obtaining independent representation where there is a material conflict of interest.

8. Data protection and confidentiality

8.1 In the ordinary self-hosted model, Customer determines which evidence is processed and controls the deployment; Licensor does not receive Customer evidence in normal operation.

8.2 If logs, packs or transaction evidence are transferred to Licensor or its support personnel for support, incident investigation or diagnostics, that transfer occurs only under a separately documented confidentiality and data-protection basis (a support data-processing annex, order-form term, or equivalent) agreed before the transfer. Absent such a documented basis, support personnel must not request and Customer should not supply such material.

8.3 Each party keeps the other's non-public information confidential and uses it only to perform this Agreement. This obligation does not apply to information that is or becomes public without breach of this Agreement, was lawfully known to the receiving party without a duty of confidence, or is independently developed without use of the disclosing party's information. Each party may disclose such information where required by law or a competent authority, and to its professional advisers and to service providers who need it to perform this Agreement and are bound by confidentiality obligations no less protective than these.

8.4 Processor arrangements. Where Licensor processes personal data on Customer's instructions — which is determined by the processing actually performed and not by the fact that the Licensed Work is self-hosted — the parties shall put in place the contractual arrangements required by Article 28 of Regulation (EU) 2016/679 before that processing begins. A confidentiality undertaking alone does not satisfy that requirement.

9. Term, termination and survival

9.1 This Agreement runs from Customer's acceptance under §11 until terminated. Either party may terminate for the other's material breach not cured within thirty (30) days of written notice.

9.2 Termination does not affect the BUSL-1.1 rights attached to copies already delivered, to the extent that licence grants them independently of this Agreement.

9.3 Survival. The following survive termination: accrued claims; Schedule 1 clauses 3, 5, 6, 7, 8 and 9; §§7, 8, 10, 12 and 13; §11's provisions preserving accepted versions, their digests and the correction history; and, for so long as Customer continues to use a delivered copy, the operational and representation duties in Schedule 2 concerning eIDAS results and retained or reused Operator Material.

9.4 The affirmative warranty does not survive as a continuing promise. Termination ends Licensor's obligation under §6.1 to perform going forward. Claims that accrued in respect of performance before termination survive under §9.3. The disclaimers in §6.3 and Schedule 1 clause 8 survive without limit of time.

9.5 Nothing in this clause creates a right for Licensor to disable, restrict or withdraw a delivered copy of the Licensed Work, or reduces the copyright permissions granted by the licence accompanying that copy.

9a. Business customers and mandatory consumer rights

9a.1 This Agreement is offered for business and professional use. The Customer confirms that it enters into this Agreement for purposes connected with its trade, business or profession.

9a.2 If mandatory law nevertheless treats the Customer as a consumer, nothing in this Agreement excludes or restricts any statutory withdrawal right or other mandatory consumer protection, or transfers an obligation away from the party legally responsible for it. Applicable withdrawal information and procedures shall be provided by the responsible contracting party before the relevant transaction is concluded.

9a.3 A confirmation of business purpose under §9a.1 is evidence of the character of the transaction; it does not determine the Customer's legal classification.

10. Governing law, jurisdiction and dispute resolution

10.1 Governing law. This Agreement is governed by the laws of the Republic of Bulgaria, excluding its conflict-of-law rules and the United Nations Convention on Contracts for the International Sale of Goods, without excluding any mandatory law that cannot lawfully be excluded.

10.2 Jurisdiction. Subject to mandatory jurisdiction rules, the courts having subject-matter jurisdiction in Sofia, Bulgaria shall have exclusive jurisdiction over disputes arising out of or in connection with this Agreement, including its formation, validity, interpretation, performance and termination.

10.3 Escalation before proceedings. Before commencing proceedings on the merits, the parties shall seek in good faith to resolve the dispute through their designated management representatives for thirty (30) days following receipt of written notice describing the dispute. This requirement does not prevent a party from seeking interim or protective relief from a competent court, or from commencing proceedings necessary to preserve a claim before an applicable deadline. It does not require either party to settle.

10.4 Mandatory rights. Nothing in this clause restricts any mandatory consumer protection or jurisdictional right.

10.5 Scope. This clause governs this Agreement. It does not vary the governing law, forum or dispute-resolution terms of the merchant of record's separate contract with Customer.

11. Acceptance, authority and documentary evidence

11.1 This Agreement is accepted affirmatively and per version: acceptance names the exact version and full SHA-256 digest of the accepted release of this document and of Schedule 2 as identified in it. Full digest values are recorded, not abbreviated ones. A digest is evidence of which text was accepted; it is not, by itself, evidence of the signatory's identity, authority or assent, which come from the acceptance process and its retained record.

11.2 Acceptance record (modelled on counsel's Enclosure E block. The operational attestation Schedule 2 requires for eIDAS deployments is an additional operational-attestation requirement, not a separate legal acceptance; it corroborates this acceptance and gates the functionality, and it does not establish agreement to these terms by itself):

I confirm that I am authorised to bind [full legal name and registration identifier of Customer]. On behalf of Customer, I accept the Stella Ops Customer Agreement, version [version], SHA-256 [digest], issued by Е-САЛЮШЪНС ЕООД / e-Solutions EOOD, and make the representations and warranties contained in it, including Schedules 1 and 2 as identified in it. I understand that this record evidences contractual acceptance. It is not an attestation, signature or qualified trust service supplied by Stella Ops or by the Licensor.

11.3 The record includes the signatory's name, title, signature method, date and customer identifier, and the version and full digest of both this Agreement and the Schedule 2 document identified in it — recorded in the acceptance record itself or in an immutable acceptance manifest linked to it. It is retained by both parties.

11.4 Amendment, and when a new version requires fresh acceptance. Licensor may issue a new version of this Agreement.

(a) Whether a change is material depends on its legal effect, not on its description. A change that alters, or could reasonably alter, a party's rights, obligations, remedies or exposure requires fresh acceptance of the new version under §11.1.

(b) Material changes include, without limitation, changes to the allocation of responsibility for Operator Material, the warranties, the indemnity, the limitation of liability, the data-protection or confidentiality position, the governing law or forum, the acceptance mechanism, the identified Schedule 2, the term or termination rights, the fees or entitlements identified under §2.3, and any support commitment identified under §5.3. This list is illustrative and not exhaustive. Accepting a new order under an unchanged version of this Agreement is not an amendment of it: an additional transaction under already agreed machinery is documented through its order, while a change to the governing bargain requires acceptance under this clause.

(c) A change that does not alter legal effect — typographical or grammatical correction, cross-reference or formatting repair — may be issued as a new version without fresh acceptance. A clarification qualifies only if it neither changes nor could reasonably change the interpretation of an obligation, right or remedy; where its legal effect is reasonably debatable, fresh acceptance is required.

(d) Editorial publication is not amendment. Issuing an editorially corrected version does not replace or amend a version already accepted. Until Customer accepts a later version, the version Customer accepted continues to govern. Licensor preserves the accepted text and its digest unchanged and maintains an append-only correction history: existing entries are not overwritten, and subsequent corrections are recorded as additional entries. No amendment operates retroactively on an acceptance already given.

11.5 Record of issued versions. The full SHA-256 digest of each issued version of this Agreement, and of the Schedule 2 document identified in that version, is recorded in the version register published with it (customer-agreement-versions.sha256), and the exact text of an issued version and of its identified Schedule 2 is retained in the release bundle of the release that carries it. An acceptance under §11.1 identifies those recorded versions and digests, and not the current state of a mutable file path. Licensor generates the customer-facing acceptance package from those canonical sources rather than from a separately edited copy.

12. Notices

12.1 Notices under this Agreement — in particular notices of dispute (§10.3), termination (§9.1), an indemnity claim (§7.4) and a proposed material amendment (§11.4) — are given in writing to the address each party identifies for that purpose in the accepted order or acceptance record, and to Licensor at the registered address of Е-САЛЮШЪНС ЕООД (e-Solutions EOOD) published in its statutory imprint.

12.2 A notice is effective on actual receipt by the party to whom it is addressed. Receipt is evidenced by that party's acknowledgement, by a recorded-delivery signature, or by a delivery confirmation from the email service used for an address the parties have agreed for notices. This is a deliberate choice of receipt-based evidence: dispatch, transmission and the passage of time do not by themselves make a notice effective under this Agreement.

12.3 Two exceptions prevent a party from defeating a notice by avoiding it, and they are the only ones. A notice is treated as received (a) where the addressee refuses a correctly addressed notice or it is returned undelivered, on the date of that refusal or return; or (b) where the addressee has not kept current the notice address it identified under §12.1, on the date delivery to that identified address was attempted. Neither exception applies where the sender knew, or had been notified in writing of, a current address for that party.

13. Export control and sanctions

13.1 Each party complies with the export-control, sanctions and trade-restriction laws applicable to it in its own performance of this Agreement.

13.2 Customer is responsible for the lawfulness of the destinations, end uses and end users to which it deploys, transfers or gives access to the Licensed Work, and for obtaining any authorisation its own jurisdiction requires. Subject always to §13.1, Licensor does not undertake to assess Customer's deployments, and nothing in this Agreement is a representation that the Licensed Work may lawfully be used in every jurisdiction. This clause does not transfer to Customer any compliance duty that applicable law places on Licensor.

13.3 Neither party is obliged to act where doing so would expose it to a penalty under a sanctions regime applicable to it.

Schedule 1 — Operator-Supplied Trust Material and Evidence

This Schedule forms an integral part of this Agreement and contains obligations owed by the Customer to the Licensor. It is not guidance, an acknowledgement template or background information. Acceptance of this Agreement under §11 is acceptance of this Schedule.

Counsel's clause text, character-for-character, from decisions/eidas-counsel-thread-licence-text-and-customer-agreement-reply.md. Do not paraphrase.

1. Definitions. “Operator Material” means any trust-material pack, trust list, certificate, validation policy, timestamp token, OCSP response, archive evidence or other third-party material that Customer, or a person acting on Customer’s behalf, selects, obtains, supplies, configures or makes available for use by the Stella Ops eIDAS functionality.

2. Provider selection and contracting. Customer, and not Licensor, selects each qualified trust service provider or other provider and is solely responsible for entering into and complying with any contract required to obtain or use Operator Material. Licensor does not supply, resell, sublicense, endorse or certify Operator Material and is not a party to the relationship between Customer and any provider.

3. Rights and lawful use. Customer represents and warrants, whenever it supplies or uses Operator Material, that it possesses all contractual rights, intellectual-property rights, permissions, consents, authorisations and lawful bases necessary to obtain, copy, store, disclose to the Licensed Work, process, validate, retain and export that Operator Material. Customer further represents and warrants that its use of Operator Material complies with applicable law, confidentiality obligations, data-protection requirements and the terms imposed by the relevant provider.

4. Operator responsibility. Customer is responsible for obtaining Operator Material from its chosen source, maintaining the versions required for its intended use, configuring the Licensed Work to refer to the correct material, controlling access to that material and determining the retention and export requirements applicable to it. This clause does not reduce Licensor’s obligation to perform the local technical checks expressly described in the Documentation when a supported version of the Licensed Work is correctly configured.

5. Scope of the Stella Ops result. A state or result emitted by the Licensed Work records only a local technical validation against the Operator Material and version identified in that state or result. It is not a qualified trust service, a certification of a provider or Operator Material, legal advice, or a determination that a signature, seal, timestamp, item of evidence or transaction has any particular legal effect.

6. No QTSP representation. Neither Licensor nor Stella Ops is a qualified trust service provider by reason of the eIDAS functionality. Customer must not state or imply that Licensor or Stella Ops selected the provider, supplied the Operator Material, issued the underlying evidence, performed a qualified validation service or acts as a qualified trust service provider.

7. Preservation of context. When Customer reproduces, exports or communicates a Stella Ops validation state, Customer must preserve the associated provider or pack identifier, pack version, validation-state identifier and mandatory disclaimer. Customer must not remove or alter that information in a manner likely to cause the state to be understood as a qualified-service claim or a determination of legal effect.

8. Disclaimer concerning Operator Material. To the maximum extent permitted by applicable law, Licensor gives no warranty concerning the provenance, authenticity, completeness, freshness, legal status, licensing status or legal or evidential effect of Operator Material or concerning any provider selected by Customer. Licensor is not responsible for loss arising from Customer’s provider selection, absence of required rights, unlawful use, incorrect configuration, outdated or incomplete Operator Material, or breach of clause 6, except to the extent the loss was caused by Licensor’s breach of an express obligation concerning the documented operation of the Licensed Work or by liability that cannot lawfully be excluded.

9. B2B indemnity. Where Customer acts in the course of business, Customer shall defend, indemnify and hold Licensor harmless from third-party claims, regulatory proceedings and reasonable costs to the extent arising from Customer’s breach of clauses 2, 3, 6 or 7, or from Operator Material supplied by or for Customer. This indemnity does not apply to the extent the claim was caused by Licensor’s breach of this Agreement, wilful misconduct or other liability that cannot lawfully be excluded.

10. Priority. This section prevails over inconsistent product documentation or technical guidance concerning responsibility for Operator Material. It does not modify the BUSL-1.1 text or alter the copyright permissions granted by that licence.

Schedule 2 — eIDAS Operator Terms (incorporated by reference)

Schedule 2 consists of the document entitled "Stella Ops eIDAS operator terms", version 2.0.0, identified by SHA-256 80f7357bf5452af86eaefa5b70598074decc378c39c985f9139cfcf166dfd5fd, supplied with this Agreement. That identified document forms an integral part of this Agreement for every deployment that configures the eIDAS functionality, and acceptance of this Agreement under §11 is acceptance of it. A reference to its repository location (eidas-operator-terms.md) identifies that specific version and does not incorporate later changes to it. Amendments are governed by §11.4.

(Reissued at version 2.0.0 in this draft. Counsel's round-2 §5.3 required the incorporated document to be separated from the internal review record it carried — draft-status history, named tests, a dated website inspection and open owner decisions were all inside the customer-facing contract. The contractual terms keep their path; the review provenance and control evidence moved to eidas-operator-terms-internal-record.md, which is not incorporated. Because the incorporated text changed, the version and digest are reissued with it: "There is no justification for retaining the old digest while changing the incorporated text.")