Controlled Configuration Services Addendum

The affected Workspace must complete two full, consecutive, successfully paid monthly billing periods verified in Nightvault's authenticated billing record, while its paid Base Plan is active and in good standing. Trial, free, paused, suspended, refunded, charged-back, failed, or disputed periods do not count. The calibration period cannot be waived for an individual Customer.

Eligibility permits an authorized Customer sponsor to submit a sanitized request for review. Nightvault may accept, decline, defer, narrow, or request clarification in its reasonable discretion. Eligibility does not guarantee review, approval, proposal, capacity, priority, timing, or delivery.

OperalonOS remains a shared, Nightvault-controlled product. Controlled Configuration does not provide a customer-specific fork, separate codebase, source-code access or license, escrow, on-premises or Customer-controlled deployment, dedicated engineering team, staff augmentation, managed operations, a separate Customer product, exclusivity, perpetual maintenance, or control of the product roadmap.

Nightvault retains final control over feasibility, architecture, implementation method, reusable components, security, release sequencing, testing, deployment, supportability, product evolution, suspension of unsafe work, and retirement of configurations, subject to the Agreement and mandatory law.

A pre-SOW request must contain only the minimum business objective, current workflow, desired outcome, affected OperalonOS area, and non-sensitive constraints needed for triage. It must not contain Customer Personal Data, Customer Confidential Information, credentials, secrets, payment-card data, production exports, or re-identifiable customer records.

Customer Materials may be supplied only after a SOW identifies the permitted data, purpose, environment, access, retention, deletion, and security controls. A request or SOW does not expand supported data categories, providers, processing locations, certifications, audit rights, or security commitments.

No project begins until both parties accept an exact Configuration SOW and Nightvault confirms that eligibility, authority, payment authorization, scope, capacity, security, privacy, provider, environment, and release conditions are satisfied. Nightvault may refuse to commence or may contain an unsafe technical act when a required condition is absent.

Each SOW must identify the affected Workspace, business objective, in-scope work, exclusions, Deliverables, dependencies, responsibilities, approved environments and providers, objective acceptance criteria, review period, Fees, invoice triggers, payment terms, target dates, support classification, and authorized representatives.

Controlled Configuration is separately priced. No Base Plan or Boost Fee includes project work. Fees, taxes, invoice triggers, expenses, and payment dates are those expressly stated in the accepted SOW. Subscription Fee adjustments under the Business Terms do not reprice a Configuration SOW.

A change to scope, Deliverables, dates, dependencies, acceptance criteria, project Fees, or another permitted project field requires a mutually accepted written Change Order before implementation. A new preference, use case, or requirement is a change request, not a defect.

Nightvault will identify each Deliverable and provide the agreed test access and validation evidence. The Customer must test against the objective acceptance criteria during the SOW review period and give a specific written rejection describing each reproducible non-conformity. Nightvault will use commercially reasonable efforts to correct verified non-conformities within the agreed scope.

Silence does not amend the Agreement or waive rights. Any deemed-acceptance mechanism must be expressly stated in the SOW, be permitted by the Agreement and applicable law, and begin only after complete delivery and test access are verifiably available.

The Customer retains its rights in Customer Data and pre-existing Customer Materials. Nightvault and its licensors retain all rights in OperalonOS, software, models, workflows, interfaces, documentation, designs, tools, reusable components, methods, know-how, configurations, improvements, derivative technology, and materials of general application.

Unless a SOW expressly identifies a separable non-software Deliverable and an agreed assignment, each Deliverable is Nightvault technology licensed to the Customer only for authorized use with the Services during the applicable subscription. No source code, exclusivity, product fork, or restriction on Nightvault using general skills, ideas, patterns, and reusable technology is granted.

The Customer is responsible for lawful instructions and for obtaining and maintaining the permissions, accounts, licenses, notices, consents, and authority required for its systems, data, providers, personnel, and Customer-controlled actions. Nightvault does not control third-party availability, terms, APIs, or product changes.

Nightvault will not execute an action inside a Customer-controlled production account unless the exact actor, account, action, scope, timing, and authority required by the SOW and Agreement have been verified.

Support, compatibility, maintenance, migration, and target dates apply only as expressly stated in the SOW or applicable Service Level Schedule. No perpetual support or backward-compatibility obligation is implied.

Nightvault may improve, replace, migrate, suspend, or retire a configuration when reasonably required by product architecture, security, law, provider changes, or maintainability, subject to the Agreement, the SOW, applicable notice obligations, and mandatory rights.

This Addendum applies while an incorporated SOW remains in effect. Termination or expiry of the related subscription or SOW ends the Customer's right to use affected configuration Deliverables except where the SOW expressly provides otherwise. Accrued payment obligations and provisions intended by their nature to survive continue according to the Agreement.

A project termination, refund, credit, suspension, or remedy is available only as expressly provided by the Agreement, this Addendum, the accepted SOW, or mandatory law. A request, estimate, invoice, or payment does not create an unstated remedy or delivery commitment.

General questions may be sent to contact@operalonos.com. The public contact form is not Controlled Configuration intake. Contractual notices must use the notice route in the Agreement or accepted SOW. Do not send credentials, secrets, payment-card information, Customer Personal Data, or production records by email or through a general inquiry.