Právní dokumenty

Eranative enterprise transformation master services agreement draft

Document stanoveno ve vaší smlouvě; version stanoveno ve vaší smlouvě; controlling language stanoveno ve vaší smlouvě; date stanoveno ve vaší smlouvě.

MSA01 Parties and authority

Provider SMARTEDTECH SL, registration NIF B66970831, address Carrer Agricultura, 16, 1º, 9ª, 08320 El Masnou (Barcelona), Spain; Customer stanoveno ve vaší smlouvě, registration stanoveno ve vaší smlouvě, address stanoveno ve vaší smlouvě. Signatory authority is recorded in stanoveno ve vaší smlouvě. Eranative is a brand, not a substitute for the contracting legal entity.

MSA02 Services and precedence

Services are limited to accepted SOW stanoveno ve vaší smlouvě and scope hash stanoveno ve vaší smlouvě. Precedence: signed change order; applicable SOW and commercial schedule; DPA for its data-processing subject matter; this agreement, subject to mandatory law. Catalogues, demonstrations and AI drafts do not independently create delivery commitments.

MSA03 Delivery and acceptance

Each deliverable has objective acceptance tests, an owner, customer dependencies and review period stanoveno ve vaší smlouvě. The Customer records acceptance or reasoned nonconformity. Defect correction belongs to the agreed scope; additional work follows change control. The system defaults to explicit acceptance; deemed acceptance requires a separately approved legal clause.

MSA04 Fees tax and payment

One-time, recurring, usage-based and third-party charges are separately disclosed. Currency stanoveno ve vaší smlouvě; tax treatment stanoveno ve vaší smlouvě; payment schedule stanoveno ve vaší smlouvě. No binding offer without approved pricing. Recurring service starts upon usable delivery and acceptance unless the SOW expressly defines another arrangement. Failed provisioning follows stanoveno ve vaší smlouvě. Duplicate or provider-caused technical calls are not charged as customer use.

MSA05 Change control

A change request states scope, fee, schedule and data/security impact and creates a new scope hash. No implementation before authorized acceptance. Defects are not relabelled as paid scope changes. Customer or external-provider delays are recorded with their schedule effect.

MSA06 Customer duties and third parties

The Customer supplies accurate information, content rights, authorized access, representatives and acceptance cooperation. Integration approval identifies data, destinations and purposes. Third-party fees, licences, limits and API dependencies are disclosed. Revocation includes an impact preview and remediation of externally committed actions where supported.

MSA07 Intellectual property

Customer content, data and organization configuration remain the Customer's. Pre-existing SDKs, shared templates and platform code remain the Provider's. Bespoke code ownership/licensing is specified in stanoveno ve vaší smlouvě. Open-source and third-party components retain their licence terms. Exit deliverables are enumerated in the SOW and exit schedule.

MSA08 Confidentiality and data

Confidential information is used only for service purposes by authorized persons with suitable protection. Personal-data roles are assigned per processing activity in the DPA. No customer-data model training or independent marketing without a separate lawful and contractual basis. Retention, deletion, transfers and incident duties follow the applicable schedules.

MSA09 AI and oversight

AI may assist with suggestions, summaries, classification and tasks, subject to context-specific verification. Legal, clinical, employment and other high-impact decisions require authorized human control and the applicable regulatory profile. Consumption follows the AI schedule.

MSA10 Term suspension and termination

Start stanoveno ve vaší smlouvě; term stanoveno ve vaší smlouvě; renewal stanoveno ve vaší smlouvě. End-of-term cancellation, work pause and permission revocation are distinct actions. Suspension notice, reasons, cure period stanoveno ve vaší smlouvě, access and fee effects are specified. Emergency restriction is limited to necessary scope. Historical records and permitted exports remain subject to lawful retention.

MSA11 Liability and disputes

Counsel must complete and approve liability cap stanoveno ve vaší smlouvě, exclusions stanoveno ve vaší smlouvě, insurance stanoveno ve vaší smlouvě, governing law stanoveno ve vaší smlouvě and forum stanoveno ve vaší smlouvě. Unfilled fields block acceptance. Mandatory rights remain unaffected.

MSA12 Notices and evidence

Legal contacts legal@eranative.com; SMARTEDTECH SL, NIF B66970831, Carrer Agricultura, 16, 1º, 9ª, 08320 El Masnou (Barcelona), Spain. Acceptance evidence includes party, authority, document version/hash, scope hash, time, method and verified receipt. Internal deployment authorization does not replace customer contract acceptance.

MSA13 Price status ladder and bindingness (v4 addendum)

Each price line is in one of four states: INTERNAL_HYPOTHESIS (never shown to Customer), APPROVED_ESTIMATE_RANGE (non-binding; binding:false), BINDING_QUOTE (an OFFERED quote fixed by document_hash and scope_hash), ACTIVE_TARIFF (tariff in force). Only BINDING_QUOTE and ACTIVE_TARIFF lines create a payment obligation. Maintenance/operations hours (default 2 h/week) are OFFER_REQUIRED and quoted separately.

MSA14 Merchant entity condition

A quote becomes binding and collection may start only once the Provider's contracting entity (merchant) is set to SMARTEDTECH SL with a registered tax profile (stanoveno ve vaší smlouvě). Until then only estimates are shared; acceptance/checkout is refused by the system with code MERCHANT_UNKNOWN.

MSA15 Scope hash and change

An accepted quote is bound to exactly one Blueprint version via scope_hash. Any Blueprint change produces a new scope_hash, supersedes the quote and routes through the change protocol (CR). Trace chain: requirement_id → blueprint_component_id → quote_line_id → contract_deliverable_id → build_task_id → test_id → evidence_ref → release_ref.

MSA16 Owner test doubles and verification level

Where a component runs against a test double instead of the production owner ("simulated"), Provider marks it in the portal; verification level for such components is capped at VERIFIED_LOCAL and does not count toward acceptance. Go-live (release GO) is performed only for versions with evidence (evidence_ref) and a passed canary.