Sentinel Risk Intelligence Labs LLC · AWS Marketplace Master Subscription Agreement

Last updated: November 1, 2026

SENTINEL RISK INTELLIGENCE LABS LLC

Master Subscription Agreement — AWS Marketplace

Provider: Sentinel Risk Intelligence Labs LLC, 191 Maple Avenue, Red Bank, NJ 07701 (“Provider”)

Product: Eyes on Glass™ / SOaaS (Service-Oriented Assurance as a Service) — risk intelligence, heartbeat monitoring, onboarding command bridge, and related governance tooling.

Customer: the legal entity that subscribes to Eyes on Glass™ through AWS Marketplace or executes an Order Form under this Agreement (“Customer”)

Table of Contents

1. [Master Subscription Agreement](#1-master-subscription-agreement)
2. [Exhibit A — Service Description & Subscription SKUs](#exhibit-a--service-description--subscription-skus)

- A.1A Industry platform selection

- A.1B Dual-Vault architecture (design purpose and function)

- A.2 Pronged Purchase Packages (including ninety-day named-user land / A.2.5b.1 and Think-tank / A.2.5c)

1. [Exhibit B — Client Operating Platform Requirements](#exhibit-b--client-operating-platform-requirements)
2. [Exhibit C — Performance & Scalability](#exhibit-c--performance--scalability)
3. [Exhibit D — Security, Privacy & Data Processing](#exhibit-d--security-privacy--data-processing)
4. [Exhibit E — Support & Service Levels](#exhibit-e--support--service-levels)
5. [Exhibit F — Professional Services (Optional)](#exhibit-f--professional-services-optional)
6. [Exhibit G — Order Form Template](#exhibit-g--order-form-template)
7. [Exhibit H — Acknowledgment of Material Technical Modifications (Redlines)](#exhibit-h--acknowledgment-of-material-technical-modifications-redlines)
8. [Exhibit I — Sovereign Posture Rebate & Global Sovereign Defense Fund](#exhibit-i--sovereign-posture-rebate--global-sovereign-defense-fund)

1. Master Subscription Agreement

This Master Subscription Agreement (“Agreement”) is entered into as of the date Customer first subscribes through AWS Marketplace or executes an Order Form (the “Effective Date”) by and between Provider and Customer. Each Order Form executed under this Agreement incorporates these terms.

1.1 Definitions

1.2 Grant of Access

Subject to this Agreement and the fees stated on the Order Form (the platform fee is USD 0.00; isolation is the industry plane selected under A.1A, not a SKU), Provider grants Customer a non-exclusive, non-transferable right during the Subscription Term for Authorized Users to access and use the Services solely for Customer’s internal business purposes, in accordance with the Documentation and applicable Exhibits. Every new subscriber starts on the ninety-day named-user model, procured through AWS Marketplace Checkout; handshake and entitlement then fail closed on day ninety (90) unless converted under A.2.5b. A Think-tank license (A.2.5c) is not the ninety-day land and is not a paying subscriber SKU; licensed use is research / lab / design-partner operators as stated on the Order Form.

1.3 Restrictions

Customer will not (and will not permit others to): (a) reverse engineer or attempt to derive source code except as permitted by law; (b) sublicense, resell, or provide the Services to third parties except as expressly allowed; (c) use the Services to build a competing product; (d) probe or scan systems without authorization; (e) remove proprietary notices; or (f) exceed documented API or usage limits without a written amendment.

1.4 Client Operating Platform

Customer is responsible for provisioning, securing, and operating the Client Operating Platform as described in Exhibit B. Provider does not warrant outcomes that depend on Customer’s failure to meet those requirements.

1.5 Performance and service levels

Environmental performance (throughput, latency, ingest volume, refresh cadence, infrastructure cost) follows the Client Operating Platform as set forth in Exhibit C and Provider’s Performance & Operating Environment Statement (incorporated by reference).

Platform integrity (governance-engine correctness) is measured under the Platform Integrity SLA in Exhibit E.3. Eyes on Glass is customer-deployed software: Customer hosts and operates the runtime, and Provider does not warrant infrastructure uptime.

1.6 Customer Obligations

Customer will: (a) maintain accurate account and billing information; (b) safeguard credentials and API keys; (c) ensure Authorized Users comply with this Agreement; (d) obtain necessary rights and consents for Client Data; (e) configure identity, network, and data-plane components per Exhibit B; and (f) not submit unlawful or infringing content.

1.7 Provider Obligations

Provider will: (a) make the Services available per Exhibit E; (b) implement reasonable administrative, technical, and organizational safeguards for Client Data per Exhibit D; (c) provide support per Exhibit E; and (d) process Client Data only as instructed in this Agreement and Exhibit D.

1.8 Fees and Payment

Fees are stated on the Order Form. Unless otherwise stated: (a) paying Subscription Fees are collected through AWS Marketplace Checkout when Customer buys through Provider’s AWS Marketplace listing — default listing cadence is the 12-month monthly payment term (Exhibit A.2.8); (b) payment timing follows the AWS Marketplace invoice on Customer’s AWS account; (c) if an AWS Marketplace charge fails or remains unpaid, Customer’s license is switched off (entitlement and handshake fail closed) until the charge is paid; (d) refunds are available only as stated under “Cancellation and refunds” in this Section 1.8, Exhibit I (Sovereign Posture Rebate as subscription credit), or as required by law.

Named-user fees. Everyone starts on the ninety-day named-user model, procured through AWS Marketplace Checkout. Full Platform plus one (1) named user license is USD 0.00 for ninety (90) days and covers the licensed scope selected on the Order Form (Package 1, 2, or 3): Mandatory Bundle, Dual-Vault STD (Exhibit A.1B), and POL-GOV-STD. When Healthcare is selected, the Healthcare PHI Vault (Dual-Vault PHI) is a separate Healthcare line under Exhibit A.1A and is not included in named-user seats. Additional named user licenses are charged through AWS Marketplace Checkout for the 90-day term at the A.2.5b volume-band rate (all seats in the band at that rate) and may be added at any time at remaining days ÷ 90. Seat rates are the same on Full Swarm, Custom Stack, and Single Pillar. Seats and bands are billed per selected industry plane; headcount is not pooled across planes. USD 0.00 on the first named user is trial-only; conversion bills every named user on that plane at that band × 4 per year (2–5 publishes USD 1,000 / year; other bands keep their cliffs). Mid-term adds on a yearly term are charged through AWS Marketplace Checkout at remaining days ÷ 365; the next yearly subscription is the full band. Paid terms default to twelve (12) monthly AWS Marketplace charges of that annual amount / 12 for every paying subscriber, including renewals; annual in advance is available only through an AWS Marketplace private offer. No APR applies.

Partnerships are not AWS Checkout. Partner, Reseller, Think-tank, and Contributor do not sign up via AWS. Enrollment is at https://eyes-on-glass.io/Partners.

Infrastructure and hosting (all packages). Customer is solely responsible for maintaining their systems, programs, and networks, and for all Client Operating Platform, infrastructure, hosting, Dual-Vault storage backends, licensing and subscriptions for systems they use for business services, paper or electronic statements they deliver to customers, reports to customers or regulatory agencies, and related third-party charges under Exhibit B (including B.0.1). Those costs are never Provider Subscription Fees and are never included in named-user fees or the day-90 posture credit.

AWS Marketplace Checkout. AWS Marketplace Checkout is leveraged when Customer buys through Provider’s AWS Marketplace listing. Default listing cadence is the 12-month monthly payment term (Exhibit A.2.8): AWS issues twelve (12) monthly charges of the named-user annual band / 12 — no APR. Annual in advance on AWS is a private offer, not the listing default. This Agreement is the end-user license agreement for Provider’s AWS Marketplace listing. AWS seller / Marketplace fees are a Provider payout cost and do not reduce Order Form fees, the Defense Fund 12% base, or the rebate base. Customer’s own cloud hosting under Exhibit B remains Customer’s infrastructure cost and is not the Marketplace charge.

Order Form fees are gross. AWS Marketplace fees are a Provider payout cost and do not reduce Subscription Fees, the Defense Fund 12% base, or the rebate base. Advisor fees under Exhibit F are paid by Customer directly to the Advisor and are not part of Subscription Fees, the Defense Fund 12% base, or the rebate base.

Global Sovereign Defense Fund allocation. Customer acknowledges that 12% of Subscription Fees under each Order Form is allocated to the Global Sovereign Defense Fund per Exhibit I to capitalize the reserve that funds Sovereign Posture Rebates and global financial-crime / cyber-breach defense initiatives. The allocation may be shown as a separate quote line or embedded in Subscription Fees per Provider’s standard quote format.

Sovereign Posture Rebate. Eligible Customers may earn a 10% rebate of that selected plane’s Subscription Fees after maintaining Strong Risk Posture on that plane for twelve (12) consecutive months. Every new subscriber is a trial organization: that Qualification Period starts during the ninety-day term and continues without restart on paid licenses. There is no direct Package 1 skip of that clock. The rebate is not earned against unselected industry platforms and does not require PASS on all six platforms. The same percentages apply to a community bank, a federal buyer, and a Fortune 500 name. Rebate direction (donation, split, or subscription credit) is elected on the Order Form per Exhibit I.5.

Cancellation and refunds. Subscription Fees are billed monthly through AWS Marketplace. Customer may cancel at any time; cancellation is effective at the end of the then-current billing month. Customer may request a refund by emailing Partner@eyes-on-glass.io within thirty (30) days of the charge. If Provider approves the refund, the license is deactivated and protection stops immediately. Customer then has seven (7) days of read-only access to export its evidence; after that period, all 4-Box entries, remediated risks, blocked data, wallet transactions, and shutdown attempts are permanently deleted, because they may contain confidential information. Customer is solely responsible for archiving its evidence. Approved refunds are issued through AWS Marketplace.

1.9 Intellectual Property

Provider retains all rights in the Services, Documentation, algorithms, models, and improvements. Customer retains all rights in Client Data. Customer grants Provider a limited license to use Client Data solely to provide the Services, comply with law, and as described in Exhibit D. That license does not include training, fine-tuning, or distilling models.

Patents. Provider’s pending and issued patents cover the SOaaS methods Customer is licensed to use, not to own or copy. The intent of this clause is:

1. Customer receives only the license needed to operate the subscribed Services.
2. No broader patent license, assignment, or covenant to sue third parties on Provider’s background patents is granted.
3. Contributor value-add (same methodology as Think-tank). Instead of a no-challenge bar, paying Customers under this Agreement receive the same overlay-patent economics as Think-tank contributors (A.2.5c / Partner rider). If Customer originates patentable improvement material (concept, Control ID overlay, isolation-safe functional note, or patent disclosure — implementation is not required), Customer (or Customer’s institution) may file. Customer grants Provider an exclusive license-back to ship that improvement in Eyes on Glass / SOaaS. Customer is guaranteed seventy-five percent (75%) of third-party patent royalties on that overlay — not 75% of named-user Subscription Fees, and never a reduction of the 12% Defense Fund or 10% Sovereign Posture Rebate. Background IP (including Ω, K13 Master Orchestrator / Master Agent, the MRM Governance Quad, Dual Vault, halt, and the twenty-five numbered agents) remains Provider’s. Customer is not a sub-licensor of those methods. If Provider recognizes that overlay as a subsystem at the caliber of Dual Vault or the Governance Quad, Customer may have a sub-licensor opportunity for that overlay only. The contribution rider is elected at https://eyes-on-glass.io/Partners (not AWS Checkout). Customer may still contest Provider’s background patents in response to a claim initiated by Provider.

Provider may identify certain functionality as covered by pending or issued patents.

Data-use commitment: no AI / LLM training. Neither Party, nor any Partner, Reseller, Think-tank, or Contributor under this program, may train, fine-tune, or distill models on Dual Vault contents, examiner packs, PHI, handshake telemetry, or customer operating data obtained through this program. Provider may request non-classified usage summaries only (operator count, and whether handshake is pointed at production rails) — not Dual Vault, PHI, or classified examiner packs. Healthcare PHI remains on the Healthcare plane; catalogs never mix.

1.10 Confidentiality

Each party will protect the other’s Confidential Information using reasonable care and use it only for purposes of this Agreement. Exclusions: information that is public, already known, independently developed, or rightfully received from a third party without restriction.

1.11 Warranties and Disclaimers

Provider warranty (limited). Provider warrants that during the Subscription Term it will provide the Services substantially in accordance with the Documentation and Exhibit A.

Customer warranty. Customer warrants it has rights to provide Client Data and that its use complies with applicable law.

DISCLAIMER. EXCEPT AS EXPRESSLY STATED, THE SERVICES AND DOCUMENTATION ARE PROVIDED “AS IS.” PROVIDER DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. PROVIDER DOES NOT WARRANT UNINTERRUPTED OR ERROR-FREE OPERATION, SPECIFIC RISK OUTCOMES, REGULATORY APPROVAL, OR AI-GENERATED CONTENT ACCURACY.

1.12 AI-Assisted Features

Certain features invoke large language models (e.g., Vertex AI / Gemini) for assistive analysis, summarization, or export formatting. AI outputs are not deterministic and must not be relied upon as sole basis for legal, compliance, or safety-critical decisions. Customer remains responsible for human review and final judgments.

1.13 Indemnification

By Customer. Customer will defend and indemnify Provider against third-party claims arising from Client Data, Customer’s use in violation of this Agreement, or Customer’s Client Operating Platform.

By Provider. Provider will defend and indemnify Customer against third-party claims that the Services, when used as authorized, infringe a U.S. patent, copyright, or trademark, subject to customary exclusions (combinations, modifications, non-Provider components, continued use after workaround).

Process. The indemnified party must promptly notify, allow control of defense, and cooperate reasonably.

1.14 Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW: (a) NEITHER PARTY IS LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR LOST PROFITS/REVENUE; (b) EACH PARTY’S AGGREGATE LIABILITY ARISING FROM THIS AGREEMENT IS LIMITED TO FEES PAID OR PAYABLE BY CUSTOMER IN THE 12 MONTHS PRECEDING THE CLAIM. These limits do not apply to breaches of confidentiality, indemnification obligations, or liability that cannot be limited by law.

1.15 Term and Termination

Term. This Agreement begins on the Effective Date and continues until all Order Forms expire or are terminated.

Termination for cause. Either party may terminate for material breach not cured within 30 days of written notice.

Effect of termination. Upon termination or expiry, or on cancellation effective at the end of the billing month, Customer’s license ends. If a refund is approved, the license is deactivated and protection stops immediately. In either case Customer has seven (7) days of read-only access to export its evidence; after that period, all 4-Box entries, remediated risks, blocked data, wallet transactions, and shutdown attempts are permanently deleted from the platform, because they may contain confidential information, unless law requires retention. Customer is solely responsible for archiving its evidence. Sections that by nature should survive (fees owed, confidentiality, IP, disclaimers, liability limits, dispute resolution) survive.

1.16 Export and Sanctions

Customer represents it is not subject to applicable trade sanctions and will not use the Services in prohibited jurisdictions or for prohibited end uses.

1.17 Governing Law and Disputes

This Agreement is governed by the laws of the State of New Jersey, without regard to conflict-of-law rules. Exclusive venue: the courts of Monmouth County, New Jersey. The parties waive jury trial to the extent permitted.

1.18 General

Neither party may assign without consent, except to an affiliate or in connection with a merger or sale of substantially all assets. This Agreement, Exhibits, and Order Forms are the entire agreement. Amendments must be in writing. If an Order Form conflicts with an Exhibit, the Order Form controls only for that order. Force majeure applies for events beyond reasonable control.

1.19 Order of Precedence

1. Order Form (commercial terms, SKU, term, fees)
2. Applicable Exhibit(s) referenced on the Order Form
3. This MSA
4. Documentation

Exception: If Customer executes Exhibit H (Acknowledgment of Material Technical Modifications), the acknowledged Material Technical Modifications apply as stated in Exhibit H and Section 1.20; Provider’s baseline warranties, performance commitments, and support obligations apply only to the unmodified standard configuration unless the parties expressly agree otherwise in a Provider-signed Impact Assessment.

1.20 Contract Modifications and Redline Acknowledgment

The parties acknowledge that enterprise procurement often involves redlines and other Contract Modifications to Provider’s standard Agreement and Exhibits.

Scope — what this Section covers. This Section and Exhibit H apply to Material Technical Modifications only. They do not apply to customary commercial or legal negotiations—such as fees, payment terms, term length, renewal, governing law, venue, insurance, confidentiality, or liability caps—that do not alter technical Exhibits, operating requirements, security minimums, performance assumptions, or SLA measurement methodology. Those commercial terms may be negotiated without triggering Exhibit H unless they introduce new technical or performance commitments (for example, an uptime percentage not paired with agreed measurement endpoints and exclusions).

Customer understanding. Customer understands and agrees that any Material Technical Modification may alter, impair, or degrade the functionality, performance, security posture, auditability, or operational reliability of the Services as designed, tested, and documented by Provider. Examples include, without limitation: relaxing encryption or key-management minimums; reducing Dual-Vault separation; removing aggregation or ingest constraints; expanding implied uptime or throughput commitments without corresponding platform investment; or shifting Provider custody obligations to configurations Provider has not validated.

Provider position. Provider does not represent or warrant that the Services will achieve the outcomes described in the Documentation or Exhibits when operated under a materially modified technical baseline unless Provider expressly confirms such outcomes in a written Impact Assessment signed by Provider engineering or authorized technical leadership. Absent that confirmation:

• the limited warranty in Section 1.11 applies only to the extent the Services are used in accordance with the unmodified standard Exhibits or Provider-approved substitutes documented on the Order Form;
• performance follows the Client Operating Platform (Section 1.5, Exhibit C) and may be further reduced by Material Technical Modifications;
• support and SLA remedies in Exhibit E may be limited or unavailable for issues traceable to Material Technical Modifications.

Process. Customer will provide redlines in writing. Provider may accept, reject, or counter with an Impact Assessment describing expected functional or performance effects. Execution of Exhibit H (or equivalent acknowledgment on the Order Form) is required when Customer insists on any Material Technical Modification to Exhibits B, C, or D, or to requirements incorporated by reference (including the Dual-Vault Security Manual and Performance & Operating Environment Statement).

No waiver of negotiation. This Section does not prohibit good-faith negotiation of commercial, legal, or technical terms; it documents Customer’s informed acknowledgment of technical and operational consequences when standard technical requirements are changed.

Exhibit A — Service Description & Subscription SKUs

A.1 Product Overview

Eyes on Glass / SOaaS is a risk intelligence and operational assurance platform. The architecture is language-agnostic and hardware-agnostic. Logic remains deterministic across:

• Virtual Machines (VMs) — cloud-native execution
• Bare metal — Physical Mainframe, Midrange, Mini, Standalone Server, Client Server, P.C., Mobile Devices
• Edge-deployment for high-frequency internal reconciliation

Handshake Protocol: Model Context Protocol (MCP) bridge for virtual-to-physical data integrity. GCP / Firebase in Provider runbooks is a reference footprint, not the product boundary and not a production prerequisite.

Architecture reference: Dual-Vault Security Manual, Performance & Operating Environment Statement, and Provider’s platform-versus-client responsibilities matrix (Provider Documentation made available to Customer).

A.1A Industry platform selection and deploy isolation

Customer purchases one (1) or more industry platforms together with one (1) licensed scope under A.2 (Full Swarm, Custom Stack, or Single Pillar) on a single Order Form. A single operating company typically selects one plane. A conglomerate may select every plane the parent (group-level) board oversees. Everyone starts on the ninety-day named-user model, procured through AWS Marketplace Checkout. They do not mix. Isolation is the industry plane, not a SKU. Named-user seats and volume bands are billed per selected plane. Headcount is not pooled across planes. Provider’s internal parent environment is not a group dashboard and is not a client deploy target.

Deploy isolation. After AWS Marketplace subscription confirmation, Provider dispatches (i) the parent kit workflow for the selected scope and (ii) the client deployment package for each selected industry platform. Provider’s internal parent environment is not a customer industry deploy target and is not a conglomerate oversight console. A purchase of one pack does not entitle Customer to another pack’s catalog, Control IDs, or deployment package unless that pack is also selected on the Order Form. Each business unit’s leadership operates on its own plane. The parent (group-level) board oversees risk management, compliance, and internal controls across those isolated installs without merging catalogs, Dual Vault stores, or PHI.

Healthcare only — Healthcare PHI Vault (Dual-Vault PHI). When Customer selects the Healthcare & Pharmaceutical platform, the Healthcare PHI Vault is a separate Healthcare line and is not included in named-user seats: USD 0.00 during the ninety-day term; after conversion, USD 9,000 per year, or USD 750 per month on the 12-month monthly payment term. The overlay covers PHI vault isolation, encryption, Standing Gate PHI-zeroed-on-stale, and the extra HIPAA security controls that do not load on the other five platforms. It is not Dual-Vault STD. The other five platforms never receive this plane.

A.1B Dual-Vault architecture (`EOG-DUAL-VAULT-STD`) — sole design section

This A.1B is the single statement of Dual Vault purpose, function, and inclusion. Later Exhibits point here; they do not restate this architecture.

Included on every license. Dual-Vault evidence infrastructure (EOG-DUAL-VAULT-STD) — Operational Vault + Immutable Archive Vault, freeze pin, handshake, live halt, and examiner seal — is included (not a separately sold optional SKU, and not withheld until conversion). Governance (K13 Master Orchestrator / Master Agent + the MRM Governance Quad) is embedded in the license, never waived, and cannot be removed from the kit. Dual Vault is included in full at the USD 0.00 platform fee on 90-day named-user land. Customer remains solely responsible for Dual-Vault backends (the two stores and HSM/keys) per Exhibit B.4 and §1.8. Technical minimums: Dual-Vault Security Manual (Deployment Packet), incorporated by Exhibit B.4.

A.1B.1 Why Sentinel Risk Intelligence Labs designed it

Sentinel Risk Intelligence Labs designed Dual Vault expecting that data in the Operational Vault is encrypted at rest (AES-256-GCM) and in transit (TLS 1.3 with mTLS), but it MAY be updated, overwritten, rotated, or deleted as operational state changes — because a preventative halt that cannot be proved is not examiner-grade, and a live operations store that can be rewritten is not an audit trail.

Labs’ mandated operating standard is:

• Prevention first
• Containment second
• Evidence always

Dual Vault is the persistence and integrity backbone that makes that standard executable: Operational Vault runs the live path; Immutable Archive Vault commits the sealed truth. Perfect prevention is not an acceptable dependency. If a material custody, financial-crime, or governance event occurs, the evidence package must still be evidentiary-complete, replayable, disclosure-ready, and tamper-evident.

Institutions already had dashboards, tickets, and after-the-fact reconstructions. Those artifacts fail when:

• the system that scored the event is the same system that can edit the record of the event;
• an internal auditor, external auditor, or examiner asks what fired, who confirmed, when, on which Control ID, and what was blocked;
• an auditor asks for timestamped, attributable, tamper-evident evidence that maps to inherited Google Cloud / Microsoft / GitHub / Cursor SOC 2 reports and to Customer’s Privacy Policy, IT Security Policy, and Acceptable Use Policy;
• counsel, insurance, or a regulator needs a disclosure package that does not have to be rebuilt from logs that have rotated.

A.1B.2 What Dual Vault is (two paths, one way)

One-way promotion. Data is created in Operational Vault. A governance checkpoint identifies a promotion candidate. The candidate is sealed, SHA-256 hashed, and Sovereign Clock timestamped. MRM Quad quorum is validated where the product workflow requires it. The candidate is committed to Immutable Archive Vault. End-to-end promotion evidence is logged. Back-propagation from Archive to Operational is prohibited. Watch instruments never handshake-pass even if sealed.

##### A.1B.2.1 Operating rules (required for designed operation)

For the platform to operate as designed, Customer SHALL apply the following rules. Failure to apply them is a Material Technical Modification (Exhibit H) and Dual Vault is not examiner-grade on that footprint.

Provider vs Customer. Provider implements Dual Vault write paths, promotion semantics, freeze pin, handshake validation, and halt evidence. Customer provisions two separated backends and independent key hierarchies under these A.1B.2.1 rules (Exhibit B.4). Provider does not host Customer vault keys unless the Order Form states a Provider-managed tenant.

A.1B.3 Evidence

Dual Vault is the examiner seal, not a browser download. Minimum evidence package for a material event:

• event narrative and decision rationale;
• Control ID execution proof (CTRL-…), including block/allow path and policy-gate context;
• actor / system attribution (who confirmed; LlamaRisk cannot substitute for AGENT_02 ∧ AGENT_17);
• Sovereign Clock timestamp and SHA-256 commitment (hash chaining for archive continuity);
• approver trail for release, override, or break-glass;
• immutable archive object reference and evidence ID (EOG-CTRL-*);
• Four-Box Box 2 BIA Financial (F) saved / prevented exposure only from a sealed counterfactual — agency civil-penalty dollars are not invented.

Uses: internal reconstruction, external audit sampling, regulatory disclosure, insurance substantiation, litigation hold, law-enforcement support. A material event missing required components is control insufficiency and cannot be closed without remediation.

A.1B.4 Internal auditing

Internal audit (Customer’s first, second, and third lines) can retrieve from Dual Vault, without rewriting Operational state:

• Control ID bind / unbind and POL-SYNC-01 fail-safe blocks when mappings are incomplete;
• handshake pass / fail-closed history and freeze-pin presence;
• compensating-control drafts vs sealed promotions;
• break-glass activation, extension, deactivation, and post-incident review (Dual-Vault BG-ACT / BG-EXT / BG-DEC / BG-PIR);
• Dual-Vault DR cadence and RPO/RTO attestation (DR-READINESS-01);
• notification dispatch (sent / failed / duplicate) with timestamp.

The SPA does not store PII; seals land in Customer’s vault backends.

A.1B.5 External auditor, inherited SOC 2, and Customer policies

Software provider role. Provider is a development / software provider. Provider ships Dual Vault write paths, promotion semantics, freeze pin, handshake, and halt evidence. Provider does not operate Customer’s control environment. Physical hosting, identity, CI/CD, and development-tooling controls sit with the platform vendors Customer and Provider use; day-to-day access, IAM, Dual-Vault backends, and workforce conduct sit with Customer. Dual Vault is less control-oriented than a managed SOC operator: it records and enforces Bound Control IDs on Customer’s cloud; Customer and the vendors below hold the operational control surface.

Dual Vault is designed so Customer can produce auditor-consumable artifacts: timestamped Control ID execution, access and promotion journals, hash-chained archive objects, and a freeze pin an external auditor can verify against SHA-256.

Inherited SOC 2 (platform vendors). The SOC 2 Type II reports that apply to hosting, identity, and software delivery are the vendors’ reports, obtained from each vendor under that vendor’s process:

Dual Vault does not replace those vendor reports. It maps freeze pin, halt, promotion, and access evidence to the criteria in those reports as they apply to Customer’s footprint.

Customer policies Provider drafted for Clients to enforce. Use of the Services is also governed by:

• Provider’s Privacy Policy (https://eyes-on-glass.io/privacy);
• the IT Security Policy Provider drafted for Clients (https://eyes-on-glass.io/security-policy);
• the Acceptable Use Policy (AUP) Provider drafted for Clients (https://eyes-on-glass.io/acceptable-use).

Customer shall adopt and enforce those policies (or Customer-equivalent policies no less protective, attached to the Order Form) for Authorized Users and the Client Operating Platform. Dual Vault seals freeze pin, halt, promotion, break-glass, and POL-SYNC-01 events so Customer can demonstrate enforcement of those policies to internal audit, external auditors, and examiners.

A.1B.6 Regulatory examinations

For in-scope industry platforms, Dual Vault holds the exam pack: Control ID map, regulatory references, compensating controls, freeze object, Dual Vault pin. Retrieval is for Customer’s examiner (for example OCC, FDIC, Federal Reserve, SEC, state DOI, or the pack’s other supervisors) — not a substitute for Customer’s filing duties.

GENIUS, CLARITY, and other Watch instruments never handshake-pass. Sealing a Watch row does not green-light a book. Preventative halt does not freeze a customer’s self-custody wallet or another firm’s chain address; HTTP 423 is friction on this institution’s onboarded payout, sweep, or Dual Vault collect.

A.1B.7 Timestamp

Sovereign Clock (K13) is the authoritative governance time source for audit-grade timestamps. Operational Vault timestamps reflect current state. Archive commits carry an immutable evidentiary timestamp at seal. Drift beyond defined tolerance is a monitored incident. Evidence IDs embed UTC date (EOG-CTRL-…-YYYYMMDD-nnn). Hash chaining makes later clock argument visible as a break in continuity, not a silent edit.

A.1B.8 Preventative measures (block, freeze, halt)

Dual Vault is not only a filing cabinet. It is how the preventative path is armed, proved, and held:

Break-glass (activation, extension, deactivation, post-incident review) is Dual-Vault-controlled: the moment governance is bypassed is the moment it is most thoroughly recorded.

A.1B.9 Ninety-day named-user land

Every new subscriber includes A.1B.1 through A.1B.8 in full for ninety (90) days. Conversion does not “turn Dual Vault on”; it extends the license term on the same backends and freeze chain.

A.2 Pronged Purchase Packages (commercial offerings)

Provider sells Eyes on Glass / SOaaS through one named-user model. Customer selects one or more industry platforms (A.1A), then licensed scope on the Order Form (Full Swarm, Custom Stack, or Single Pillar) for each selected plane. A single operating company typically selects one plane. A conglomerate may select every plane the parent board oversees; catalogs never mix. Everyone starts on the ninety-day named-user model, procured through AWS Marketplace Checkout for each selected plane. Packages 1–3 are scope — how many Risk Domain/Pillars those seats may bind — and do not change seat rates. For Package 2 and Package 3, the Order Form states the applicable Risk Domain/Pillars; only functionality tied to those named pillars is deployed. Unnamed pillars are not licensed and are not deployed. Named-user seats and volume bands are billed per selected plane. Dual-Vault STD is included (Exhibit A.1B). The 12-month monthly payment term is a billing cadence (annual / 12, no APR) for every paying subscriber, including renewals, not a kit. There is no Package 4. Paying Subscription Fees on this Agreement are collected through AWS Marketplace Checkout. The ninety-day named-user term, including one-seat USD 0.00 land, is procured through AWS Marketplace Checkout. Partner, Reseller, Think-tank, and Contributor enroll at https://eyes-on-glass.io/Partners, not via AWS. Gold-input platform lists and per-agent list prices are not sold. There is no platform fee. The Exhibit I rebate is attested per selected plane, not across all six industry platforms.

A.2.1 Mandatory in every package (locked)

The following components are required in Packages 1–3 and on ninety-day named-user land and are not substitutable or removable:

Customer may not subscribe to individual field agents without the Mandatory Bundle. Package 3 licenses one (1) Risk Domain/Pillar (not a lone field agent) plus the Mandatory Bundle; only functionality tied to that named pillar is deployed.

A.2.2 Universal platform lines (every quote)

Regardless of package, production quotes include these separate line items (not absorbed into field-agent fees or implementation):

Optional upgrades (POL-GOV-ENT, Dual-Vault GEO-PLUS/PQ, detection bundles) are stated on the Order Form.

A.2.3 Package 1 — Full Risk Domain/Pillar Swarm Sovereign

Package 1 is the complete SOaaS swarm scope. Named-user seat rates are the same as Packages 2 and 3. Customer receives the Full Swarm roster on the selected plane unless the Order Form states exclusions (which may trigger Exhibit H if material). Gold-input Full Swarm list prices and a separate “strategic premium” line are not the invoice.

A.2.4 Package 2 — Custom Pillar Stack Sovereign

Customer selects Risk Domain/Pillars on Order Form Schedule A-2; the Schedule restates the mapped field-agent roster per selected pillar. Pillars not listed are not licensed and are not deployed. Live connector authorization per enabled system remains Customer responsibility (Exhibit A.6).

A.2.5 Package 3 — Single Pillar Sentinel

Additional Risk Domain/Pillars require migration to Package 2 or an Order Form amendment. Until then, functionality tied to unnamed pillars is not deployed.

A.2.5b Ninety-day named-user land (default cadence — not a fourth package)

Everyone starts here. Ninety-day named-user land is the default billing cadence for Packages 1, 2, and 3, procured through AWS Marketplace Checkout. It is not Package 4, not a separate price book, and not Full Swarm-only. Licensed scope on the Order Form (how many Risk Domain/Pillars those seats may bind) rides this cadence. Commercial terms: (1) Full Platform plus one (1) named user license is USD 0.00 for ninety (90) days on each selected plane; (2) additional named user licenses are charged through AWS Marketplace Checkout for the 90-day term at the volume-band rate, all seats in the selected band at that rate, and may be added at any time at remaining days ÷ 90; (3) the entitlement expires on day ninety (90) and then fail-closes unless converted. Dual Vault is in. Customer pays all infrastructure and hosting.

The 90-day named-user term is not eligible for the 12-month monthly payment term during the ninety-day term. Every new subscriber is a trial organization: the Exhibit I Sovereign Posture Rebate still requires twelve consecutive PASS months on that selected plane, and that Qualification Period starts during the ninety-day term. At day 90, a Customer that has achieved desired risk posture on that plane and continues receives a full credit of 90-day named-user fees as stated above, and PASS months earned on that plane carry forward (the clock does not restart). The rebate does not require PASS on all six industry platforms. Provider does not publish a target percentage of package-price “saves”; Four-Box Box 2 prints sealed BIA Financial (F) saved / prevented exposure only when a sealed counterfactual exists. Agency civil-penalty dollars are not invented.

A.2.5b.1 Dual-Vault architecture on the ninety-day license

Ninety-day named-user land includes Exhibit A.1B in full — design purpose (A.1B.1), two-path architecture and operating rules (A.1B.2 / A.1B.2.1), evidence (A.1B.3), internal audit (A.1B.4), external auditor plus inherited Google Cloud / Microsoft / GitHub / Cursor SOC 2 and Customer Privacy / IT Security / AUP policies (A.1B.5), regulatory examinations (A.1B.6), Sovereign Clock timestamps (A.1B.7), and preventative block / freeze / HTTP 423 halt (A.1B.8).

Customer receives Dual Vault as operational safeguarding and examiner-grade evidence, not as a delayed conversion feature. Freeze pin, handshake fail-closed, CTRL-K13-PREEMPT-01 dual-signal halt, quarantine/release, POL-SYNC-01 fail-safe, cyan successful halt, and SHA-256 archive seals operate during the ninety-day term on Customer’s backends. Day 90 fail-closes the license, not Dual Vault as a product capability. Conversion extends the same freeze chain.

A.2.5c Think-tank license SKU (Gated Institution-Community)

Think-tank is not a paying subscriber SKU and not ninety-day named-user land. Partner, Reseller, Think-tank, and Contributor do not sign up via AWS. Enrollment is at https://eyes-on-glass.io/Partners. Customer is a Design Partner or Academic / Research Institution admitted after the same due diligence as every partner, holding a Partner ID (EOG-P-########), SKU EOG-*-THINK-TANK at USD 0.00 for that institution’s own operators. Not annual, not 12-month monthly, not stock. Isolation remains the industry plane selected under A.1A. Partner’s clients still pay named-user bands. Infrastructure is never credited. Named-user cohort is capped on the Order Form. Partner shall not gift, resell, or white-label those seats.

Think-tank terms in the Partner / Reseller Agreement §7 (Think-tank rider) control contribution share. This Order Form controls licensed use, cohort cap, the 180-day clock, production conversion, and usage-summary rights.

A.2.6 Agent catalog reference (summary)

Full ω weights and BIA tier multipliers: Provider Documentation made available to Customer.

A.2.7 Deployment scale and feed registry

A.2.8 12-month monthly payment term (billing cadence)

The 12-month monthly payment term is not a Pronged Purchase Package and does not produce a distinct kit. It is a payment cadence for Package 1, 2, or 3, available to every paying subscriber, including renewals. On this Agreement, AWS Marketplace Checkout issues those twelve monthly charges.

The 12-month monthly payment term is the default for paying subscriptions under this Agreement. Annual in advance is available only through an AWS Marketplace private offer.

A.3 What Is Included in the Subscription

• Access to subscribed agents, controls, and modules per selected Pronged Purchase Package (Exhibit A.2)
• Mandatory Bundle (K13 + Quad), Dual-Vault STD, and POL-GOV-STD when on Order Form
• Eligibility for Sovereign Posture Rebate and Global Sovereign Defense Fund participation (Exhibit I), per selected industry plane. Every new subscriber is a trial organization: the twelve-month Qualification Period starts during the ninety-day term on that plane and continues on paid licenses. There is no direct Package 1 skip of that clock. Named-user fees may be fully credited at day 90 per A.2.5b if desired risk posture is achieved on that plane and Customer continues. Unselected platforms are not in the Qualification Period
• Product updates and security patches during the Subscription Term
• Support per Exhibit E.1 (Provider code, onboarding roster / integration catalog, Control IDs, and KPIs), 9:00 AM to 5:00 PM Eastern Time, business days; break-fix matters are routed to Customer’s own Production Support team
• Documentation and release notes

A.4 What Is Not Included (unless on Order Form or SOW)

• Agents, detection modules, or controls not listed on the Order Form
• All Customer infrastructure, hosting, and cloud spend (GCP, Firebase, AWS, Azure, colo, on-premises), HSM, bandwidth, Dual-Vault storage backends, and related third-party charges — Customer sole cost on every license
• Identity provider (Okta, Entra ID, Google Workspace) licensing
• Per-source-system connector implementation beyond catalog wiring
• 24×7 or extended-hours support (Provider support hours are 9:00 AM to 5:00 PM Eastern Time, business days)
• Support for Customer infrastructure, hosting, network, cloud, colocation, or MSP environments (Customer contacts its internal help desk or its service provider’s help desk)
• Regulatory or legal advice (Customer contacts its own regulatory/compliance team, general counsel, or the applicable regulatory agency)
• Break-fix support, including code-related break-fix in Customer’s deployment (Customer contacts Customer’s own Production Support team)
• Legal or compliance certification audits (SOC 2 Type II, etc.) unless separately contracted
• Custom ML model training on Customer data

A.5 Sandbox vs Production

Sandbox and Production run the same deterministic kernel. Neither mode is Firebase-bound. Both follow the language-agnostic and hardware-agnostic principle in A.1.

Sandbox (sandboxMode / demo catalog / CLI dry-run) runs without live Dual Vault persistence. It is suitable for demos and dry-runs on any listed environment (VM, bare metal, mainframe, midrange, mini, standalone server, client-server, P.C., mobile, or edge). Sandbox is not examiner-grade evidence and is not Strong Risk Posture.

Production is that same kernel armed on the Client Operating Platform Customer elects. Production requires: (1) production authentication (Customer IdP or equivalent — not a Firebase-only prerequisite); (2) Dual-Vault backends per Exhibit A.1B (including A.1B.2.1 operating rules) and Exhibit B.4; (3) Exhibit B platform readiness on that footprint. Co-locating both vaults on one logical storage instance, or omitting unidirectional Archive isolation, is not Production.

Ninety-day named-user land is production (including Dual Vault) on the Client Operating Platform — it is not sandbox. Think-tank (A.2.5c) is a production-grade kernel in licensed research / lab / design-partner scope — it is not sandbox and is not a license to operate Customer’s live book as Governance and Loss Prevention. Order Form must state environment(s) (VM / bare metal / edge / other) and, for Think-tank, licensed use.

A.6 Integration Catalog

The platform ships a catalog of systems (e.g., HR, ERP, IAM pillars) for onboarding UX and handshake templates. Live OAuth, API credentials, and data extraction for each source system are Customer responsibilities unless a Professional Services SOW states otherwise.

A.7 Order Form schedules

Each Order Form must attach or incorporate:

Exhibit B — Client Operating Platform Requirements

B.0 Hosting model and scope

The Client Operating Platform is Customer-owned and Customer-operated. Provider delivers the governance engine, APIs, and reference install patterns; Customer (or Customer’s integrator) provisions the environment that hosts application components, stores Client Data, connects source systems, and enforces Customer security policy.

Language-agnostic / hardware-agnostic. Exhibit B applies the A.1 principle: deterministic logic on VMs (cloud-native), bare metal (Physical Mainframe, Midrange, Mini, Standalone Server, Client Server, P.C., Mobile Devices), and edge-deployment for high-frequency internal reconciliation. GCP / Firebase in Provider runbooks is one reference path Provider tests first — not a requirement to go live.

Likely Customer deployments: Amazon Web Services (AWS), Microsoft Azure, GCP, a shared hybrid model, colocation, managed hosting, on-premises, mainframe / midrange / LPAR, client-server, P.C. / mobile, or edge. This Agreement and Exhibit B apply to all of the above. Customer selects the hosting model on the Order Form (see Exhibit G).

Hybrid note: Even when Customer’s data plane and source systems reside in AWS, Azure, colocation, or on-prem, Customer may place components across two or more environments. Provider does not host the Services runtime. Customer is responsible for secure connectivity, identity federation, and data-residency compliance across all segments.

Functional equivalence: Customer must supply capabilities equivalent to those in the tables below. If Customer’s stack does not offer a listed equivalent, the parties document the substitute in a deployment addendum or Professional Services SOW before go-live.

Reference: Provider’s platform-versus-client responsibilities matrix, Provider Documentation made available to Customer (Bucket A = Provider product; Bucket B = deployer environment; Bucket C = Customer onboarding per tenant).

B.0.1 Customer organizational, systems, and data-control obligations

Customer remains solely responsible for maintaining their systems, programs, and networks, ensuring organizational roles and responsibilities, security settings, general-ledger and transmission controls, and infrastructure and hosting costs of each selected project, including:

Roles. Customer shall maintain Organizational roles and responsibilities consisting of:

• [Board / Executive] — risk acceptance.
• [CISO / Head of Information Security] — advises on risk, and reports on IT Security Control effectiveness.
• [CIO / Head of IT] — implements technical controls and operational procedures.
• [People / HR] — joiner, mover, and leaver processes; disciplinary process for violations.
• [Line managers] — ensure their teams understand and follow corporate policies.
• Users — protect credentials, report incidents, and use systems only as authorized.

Endpoints, access, and change. Organization-issued devices run supported operating systems, current security updates, [endpoint protection], disk encryption where required by classification, and automatic lock [after X minutes]. Users shall not disable security software or attach unauthorized equipment to the network. Remote access SHALL use [VPN / zero-trust / approved method] with MFA. Wireless and guest networks shall be segregated from production networks as [described in the network standard]. Changes to production systems follow [change-management procedure]. Emergency changes SHALL be documented and reviewed after the fact. Backups meet [RPO/RTO] defined by [BCP/DR policy]. Restore tests occur at least [annually]. Critical services shall have documented recovery objectives [RTO/RPO] and tested plans. Tests and results shall be recorded at least [annually].

Data classification. Data in the organization is classified by [Data owners], who classify information they own and approve access. Information is classified and handled according to the Data Classification Policy for:

• Public — approved for public release.
• Internal — for staff and authorized parties; not for public release.
• Confidential — limited need-to-know; harm if disclosed.
• Restricted / Secret — highest sensitivity (e.g. authentication secrets, large personal-data sets, material non-public information).

Users label, store, share, retain, and dispose of information according to its classification. Production data shall not be copied to non-production without approval and masking where required.

Secure development and configuration. Customer is responsible for internal configuration settings, versions of systems and programs they use for business services, and introducing new or revised code into their environments. Secure development SHALL include [code review, dependency scanning, secrets scanning, separate environments, least-privilege service accounts]. Customer is responsible for the licensing and subscriptions for any and all systems and programs, internally developed or purchased, used for business services.

Logical access. Access to systems and information is granted based on least privilege and need-to-know.

• Users have unique IDs. Shared privileged accounts are prohibited except where technically unavoidable, in which case use is logged and dual-controlled.
• Authentication meets [password standard / MFA requirement]. Multi-factor authentication is required for [remote access, privileged access, email, cloud consoles].
• Access is granted via onboarding, reviewed on a predetermined period and on mover events, and revoked on leaving, promptly.
• Privileged access is time-bound where practicable, separately logged, and reviewed at least quarterly.
• Periodic access reviews are completed by [data owners / managers] at least annually.

Physical access. Premises, server rooms, and sensitive areas use access control appropriate to risk. Visitors are signed in / escorted. Clear-desk and clear-screen practices apply in offices / all sites.

General ledger, transmission, and encryption. Customer maintains their general-ledger systems and the transmission of data on internal systems and to external parties. Data in transit over untrusted networks shall be encrypted using current, supported protocols (e.g. TLS 1.2+; prefer TLS 1.3). Data at rest shall also be encrypted where required by classification or law (e.g. laptops, portable media, selected cloud stores).

Cryptographic keys and secrets are stored in approved vaults or key-management services, rotated on [schedule], and never committed to source code, tickets, or chat. Use of deprecated algorithms is inventoried and remediated on a plan approved by the CISO.

Monitoring and incidents. The organization monitors systems to detect misuse, attack, and operational failure. Logs are maintained, protected against tampering, and retained for [period], subject to law. Monitoring does not replace the requirement to report incidents. Personal data in logs should be masked / minimized. Users report suspected security incidents, lost devices, or unauthorized disclosure immediately to [IT Service Desk / security contact]. An Incident Response Plan governs investigation, containment, notification, and lessons learned. Legal/regulatory notification is decided by [Legal / DPO] according to applicable law.

Statements, reports, and hosting. Customer remains solely responsible for paper or electronic statements they deliver to customers, reports to customers or regulatory agencies, and infrastructure and hosting costs of each selected project.

B.1 Identity & access

B.2 Infrastructure, network & runtime

B.3 Data plane & persistence

B.4 Security, operations & resilience

B.4.1 Dual-Vault subsystem (required)

Purpose and function of Dual Vault, and the operating rules required for designed operation (logical separation, network segmentation, independent key hierarchies, geographic redundancy), are described in Exhibit A.1B (including A.1B.2.1). This B.4.1 states Customer’s obligation to provision the backends so those rules are met. B.4 does not restate the Dual Vault architecture.

For any production deployment (non-sandbox), including ninety-day named-user land, Customer must provision, operate, and maintain a Dual-Vault subsystem consisting of two logically and cryptographically separated stores:

Customer responsibilities (all hosting models):

1. Provision both vaults in Customer-controlled infrastructure (or Customer-contracted colo/hosting). Provider reference env vars: VAULT_BUCKET (Operational), ONBOARDING_IMMUTABLE_ARCHIVE_BUCKET / IMMUTABLE_ARCHIVE_BUCKET (Archive) on GCP; Customer maps equivalents on AWS, Azure, or on-prem.
2. Maintain separation of duties: no single identity with simultaneous write authority to both vaults; one-way promotion from Operational → Archive only (no back-propagation).
3. Enforce access controls: RBAC minimum roles, ABAC attributes where applicable, MFA for human access, mTLS for machine access, break-glass only per documented workflow with dual approval and time bounds.
4. Operate key management: independent KEK/DEK hierarchy per vault (Tier 1 root KEK, Tier 2 partition/pillar KEK, Tier 3 DEK per record/batch policy); KEKs in HSM or FIPS 140-2 Level 3 (target 140-3) boundary; DEKs wrapped at rest; rotation, revocation, and destruction per NIST SP 800-57 / 800-88 aligned practices.
5. Meet encryption minimums: all vault data at rest AES-256-GCM (or stronger Provider-approved AEAD equivalent); TLS 1.3 minimum in transit; mTLS for service-to-machine vault APIs where supported.
6. Preserve archive integrity: SHA-256 (minimum) commitment hashing, tamper-evident hash chaining for archive commitments, retention lock aligned to Customer policy and applicable law.
7. Audit and monitor: append-only audit of vault access, promotion events, key lifecycle events, authz decisions, and break-glass activations; integrate with Customer SIEM.

Provider role: The Services implement dual-vault write paths, promotion semantics, and validation when Customer vault backends are correctly configured. Provider does not host Customer vault keys or substitute for Customer custody obligations unless explicitly stated on an Order Form (e.g., Provider-managed tenant).

Incorporated by reference: the Dual-Vault Security Manual (Deployment Packet), Provider Documentation made available to Customer. Where this Exhibit summarizes the Manual, the Manual governs technical minimums for production authorization. Deviations require written deployment addendum and, for material gaps, Provider written acceptance before go-live.

B.4.2 Cryptographic and access-control minimums (summary)

B.4.3 General security, operations & resilience

B.5 Deployment footprint selection (Order Form)

Customer marks one primary model; hybrid combinations are described in free text.

Provider support boundary: Provider support covers only Provider code, the onboarding roster (integration catalog), Control IDs, and KPIs, per Exhibit E.1. Provider does not support Customer infrastructure. Any break-fix matter, including code-related break-fix in Customer’s deployment, goes to Customer’s own Production Support team. Customer or its SOW integrator is responsible for provisioning and operating the Client Operating Platform, and Customer directs infrastructure, hosting, network, cloud, colocation, or MSP issues to its internal help desk or its service provider’s help desk, unless Exhibit F Professional Services explicitly includes infrastructure implementation for Customer’s chosen footprint.

B.6 Acceptance criteria (illustrative)

Before production go-live, Customer (or integrator) should satisfy environment-specific checks analogous to Provider’s readyz scripts: authenticated health on gateway and bridge, correct auth mode, reachable UI URL, Dual-Vault subsystem operational (Operational Vault and Immutable Archive Vault provisioned, encrypted, access-controlled, and writable per B.4), and smoke test of at least one handshake or ingest path in non-sandbox mode.

Exhibit C — Performance & Scalability

C.1 Governing Principle

Functionality is fixed by product version and subscribed SKU. Performance, throughput, latency, and infrastructure cost follow the Client Operating Platform.

Incorporated by reference: Provider’s Performance & Operating Environment Statement (Provider Documentation made available to Customer).

C.2 Technical Bounds (current product generation)

C.3 Enterprise Scale

For deployments referencing hundreds of source systems or high event rates:

1. Customer (or SOW integrator) deploys an aggregation plane before /ingest.
2. Partitioning, backpressure, and retry are shared responsibilities per Provider’s enterprise ingest topology guidance (Provider Documentation made available to Customer).
3. Performance acceptance tests use Customer’s staging/production platform, not Provider’s demo sandbox.

C.4 Excluded Performance Claims

Unless explicitly stated on an Order Form with attached test protocol:

• Specific uptime percentage (see Exhibit E)
• Maximum events per second globally
• End-to-end latency SLAs for ingest → dashboard
• Cost caps on Customer’s cloud or hosting bill

Exhibit D — Security, Privacy & Data Processing

D.1 Data Roles

A separate Data Processing Agreement (DPA) is required if GDPR, UK GDPR, or similar laws apply. Attach as Exhibit D-1 or standalone agreement.

D.2 Security Measures (Provider)

Provider is a software / development provider. Measures below apply to Provider-controlled application code and delivery, not to operation of Customer’s Client Operating Platform or Dual-Vault backends (Exhibit B.4).

Provider will maintain commercially reasonable measures including:

• Encryption in transit (TLS)
• Encryption at rest for Provider-managed stores where supported
• Access controls and least-privilege IAM for Provider personnel
• Vulnerability management for Provider-controlled application code
• Incident notification to Customer within 72 hours of confirmed breach affecting Customer Client Data

D.3 Security Measures (Customer)

Customer is responsible for: API key rotation, identity and access management (IAM) and security configuration of Customer’s chosen cloud or hosting platform, network segmentation, aggregator hardening, and workforce access policies, and for adopting and enforcing Provider’s Privacy Policy, IT Security Policy, and Acceptable Use Policy (AUP) (or Order Form equivalents no less protective) as stated in Exhibit A.1B.5.

D.4 Subprocessors

Provider may use Google Cloud (GCP / Firebase), Microsoft (Azure and related Microsoft services where in the footprint), GitHub (Actions, GHCR, private artifacts), Cursor (Anysphere — development tooling), and other subprocessors listed at https://eyes-on-glass.io/subprocessors. Customer may rely on those vendors’ SOC 2 Type II reports obtained from each vendor’s trust center, as described in Exhibit A.1B.5. Provider will notify Customer of material subprocessor changes.

D.5 Data Location

Client Data is stored and processed in the region(s) Customer selects for its Client Operating Platform. Customer must not configure cross-border transfers inconsistent with applicable law without appropriate safeguards.

D.6 Retention and Deletion

Retention defaults per Documentation. Upon termination, or when a refund is approved, Customer has seven (7) days of read-only access to export its evidence; after that period, all 4-Box entries, remediated risks, blocked data, wallet transactions, and shutdown attempts are permanently deleted from the platform and from any Provider systems, because they may contain confidential information, except where law or a legal hold requires retention. Customer is solely responsible for archiving its evidence (Sections 1.8 and 1.15).

D.7 Audit Rights and Shared Responsibility

(a) Provider development practices. Provider is a software provider. The Services are developed and deployed under Secure by Design controls and OWASP principles. Core components are written in Rust, whose compiler enforces memory-safety and shared-state safeguards and whose low runtime overhead can reduce CPU and memory requirements for suitable workloads. Tested implementations sit behind defined interfaces, and other components consume only their outputs. Source code is held in a third-party private repository, with each of the six (6) industry platforms logically separated and system logs maintained. Before deployment, each release undergoes performance, security, and user acceptance testing, and management reviews every release before it is committed and deployed to the applicable industry platform package. Provider regularly scans its code for vulnerabilities and remediates findings according to CVSS severity.

(b) Customer environment. Provider has no control over, or input into, Customer’s control environment or the risk posture of any colocation provider, cloud hosting provider, or MSP Customer uses. Customers in regulated industries, or that use regulated businesses or third-party providers, are responsible for their own due-diligence assessments and for managing vulnerabilities and threats according to their risk tolerance and classification level.

(c) Audit requests. Provider applies no minimum or maximum number of policy retrieval attempts against the state of the Dual Vault. No minimum or maximum number of times is placed on Customer's retrieval of logs and metrics of the entire platform. This policy is another example of the eyes-on-glass First Principle, its bedrock doctrine, and it is why any Customer can look at any screen and know its live date. eyes-on-glass takes disclosure seriously, in real time. Two layers share one reporting surface. (1) Vault Metrics Posture is live status, available 24×7 with no view quota; it shows that the vault is healthy, what was promoted, and that the chain is intact. (2) The applicable Exam Pack is the sealed proof for a given examination or audit: the Control ID map, freeze object, Dual Vault pin, and the metric rows captured and promoted for that event. Exam Packs are released through grant → collect → revoke, not by opening Posture. Anyone who needs the sealed proof, evidence or metrics receives the Exam Pack through that same door, including examiners, Customer, internal audit, counsel, external auditors, law enforcement, and Customer's Third-Party Providers; the Exam Pack is released to each of them through the grant → collect → revoke process. It is Customer's data; it remains in Customer's own deployment, and Provider does not hold it. It is therefore available to Customer through both the Vault Metrics Posture (live, 24×7, with no view quota) and the Regulatory Exam Pack. Customer may also request at any time (i) Dual Vault evidence of policy and halt/freeze execution, (ii) a summary of Provider's application-layer security controls described in (a), and (iii) direction to the Google Cloud, Microsoft, GitHub, and Cursor SOC 2 Type II reports from those vendors. Provider operates no data centers or physical facilities that host Customer Data; the platform is customer-deployed and its supporting infrastructure is outsourced, so infrastructure assurance comes through those vendors' SOC 2 Type II reports in (iii) rather than onsite audits of Provider.

Exhibit E — Support & Service Levels

Provider SLAs are structured in two tiers:

E.1 Support Channels

Support scope. Provider support covers only Provider code, the onboarding roster (integration catalog), Control IDs, and KPIs. Break-fix matters go to Customer’s own Production Support team. Support hours are 9:00 AM to 5:00 PM Eastern Time, business days. Provider does not offer 24×7 or extended-hours support.

Break-fix matters. For any break-fix matter, including code-related break-fix in Customer’s deployment, Customer contacts Customer’s own Production Support team. The only escalation Provider supports is at the sole written direction of a regulatory agency stating that Sentinel Risk Intelligence Labs LLC owns the matter; no other escalation path exists.

Infrastructure issues. For infrastructure, hosting, network, cloud, colocation, or MSP issues, Customer contacts its internal help desk or its service provider’s help desk. Provider does not support Customer infrastructure.

Regulatory inquiries. For regulatory inquiries, Customer contacts its own regulatory or compliance team, general counsel, or the applicable regulatory agency. Provider does not provide regulatory or legal advice.

E.2 Severity Definitions

Response target. All severities carry a single initial-response target of 4 business hours, measured within E.1 support hours (9:00 AM to 5:00 PM Eastern Time, business days). This is an initial-response target for Provider-scope matters (Provider code, the onboarding roster, Control IDs, and KPIs). It is not a production-support SLA or a resolution or fix-time commitment, because Provider does not provide production support. Break-fix matters stay with Customer’s own Production Support team per Exhibit E.1.

E.3 Platform Integrity SLA (Provider commitment)

Provider commits that the governance engine — for the Customer’s subscribed Pronged Purchase Package, agents, and controls on the Order Form — will operate in accordance with the Documentation and release version in effect during the Subscription Term, measured against the metrics below.

Measurement philosophy. These metrics attest to correctness and fidelity of Provider-delivered logic, catalog wiring, and control enforcement — not to infrastructure uptime, ingest throughput, or live third-party connector success (which depend on the Client Operating Platform and Bucket C onboarding per Provider’s platform-versus-client responsibilities matrix).

E.3.1 Platform Integrity Metrics

Provider commits that the governance engine produces deterministic, machine-evaluated signals for the six metrics below. These metrics are measured by the K13 Orchestrator and Governance Quad validation logs — no subjective scoring, no human override.

Strong Risk Posture is not scored on these six metrics. PI-1–PI-6 measure Provider governance-engine correctness and support service credits (E.3.2). Rebate eligibility is licensed Risk Domain/Pillar PASS under Exhibit I.4, attested by SHA-256 Sovereign Hash. K13’s sealed monthly Sovereign Posture Attestation is final and conclusive for rebate eligibility, per Exhibit I.4.3.

Supplementary catalog metrics (control-ID wiring, onboarding wizard paths, Model ID Card schema, Four-Box grammar) remain in Documentation and release regression suites; they support PI-1–PI-6 for Provider SLA purposes. They are not Sovereign Posture Rebate eligibility gates.

Platform Governance — annual reference-layer refresh. Provider maintains the onboarding wizard roster (integrationCatalog.json), marketplace and reputational-AI monitor cross-refs, and related catalog wiring on the annual cycle defined in Provider Documentation (plus ad-hoc critical gaps). This is Provider Platform Governance under Exhibit E.3 — not a Customer-purchasable SKU, add-on, or Bucket C onboarding obligation. Command Bridge search, pillar assignment, and handshake wiring for catalog systems are included in the licensed Services; live production connector enablement per vendor remains Customer responsibility per Exhibit A.6 and Exhibit F.

Functional behavior is fixed by product version; Customer must run a supported release. Customer must supply production telemetry per Exhibit B for K13 to evaluate licensed Risk Domain/Pillars (Exhibit I.4) and, separately, PI-1–PI-6 for Provider SLA.

E.3.2 Attestation and remedies

AI-assisted features (invokeLlm, summarization, export formatting) are excluded from PI-2 and PI-3 except where they affect Evidence Engine hash inputs (PI-5).

E.4 Exclusions from Platform Integrity SLA

The following are excluded from Platform Integrity metrics and remedies (E.3):

E.5 No Scheduled Maintenance

Provider does not operate scheduled maintenance windows. Regulatory enforcements, Control IDs, KPIs, and the introduction of new vendor business applications through the onboarding wizard are applied automatically within the Services, without a maintenance process or downtime notice. Product updates and security patches are delivered as releases; Customer must run a supported release (Exhibit E.3).

Exhibit F — Professional Services (Optional)

Applicable when Customer engages an Advisory Committee member as listed on the Order Form, or when an SOW references this Exhibit.

Rates: Advisory Committee members (“Advisors”) are independent advisors, not employees or agents of Sentinel Risk Intelligence Labs LLC. Each Advisor contracts directly with Customer under the Advisor’s own engagement agreement. The rates below are the Advisors’ own hourly rates, listed for Customer’s reference.

Billing: Each Advisor invoices Customer directly at that Advisor’s own hourly rate, under the Advisor’s own engagement agreement, and Customer pays the Advisor directly.

Minimum engagement: A minimum of ten (10) hours per advisor engagement is the standard requirement.

Scheduling: Scheduling is based on each advisor’s availability.

Advisory only: Advisor services are advisory only. They do not constitute legal advice from Provider or a Provider production-support obligation (consistent with Exhibit E.1). The General Counsel Advisor does not create an attorney-client relationship with Customer unless separately engaged in writing.

Provider not a party: Provider is not a party to, does not bill, and is not liable for Advisor engagements or advice. Advisor fees are not Provider fees and are excluded from Subscription Fees, the Defense Fund 12% base, and the rebate base.

Acceptance: Advisor engagements: hours and billing are governed by the Advisor’s own engagement agreement with Customer, not by Provider’s records; custom integration work under an SOW: written sign-off on agreed test protocol.

Change control: Material scope changes require written change order.

Exhibit G — Order Form Template

ORDER FORM NO: [____]

Effective Date: [____]

Subscription Term: 90 days named-user land (default; no auto-renew) then 12 months paid (Packages 1–3; auto-renew: Yes — renews for successive 12-month terms through AWS Marketplace on twelve monthly charges; Customer may turn off auto-renewal before the end of the then-current 12-month term, effective at the end of that term)

Customer: [Legal name, address]

Provider: Sentinel Risk Intelligence Labs LLC, 191 Maple Avenue, Red Bank, NJ 07701

Industry platform (Exhibit A.1A) — select one or more (seats bill per plane; catalogs never mix):

[ ] Financial Institutions

[ ] Healthcare & Pharmaceutical

[ ] On-Chain / Digital Asset

[ ] Transportation & Logistics

[ ] Telecommunications & Data

[ ] Energy & Utility

Pronged Purchase Package (Exhibit A.2) — select one licensed scope **per selected plane** (not a fourth package):

[ ] Package 1 — Full Risk Domain/Pillar Swarm Sovereign

[ ] Package 2 — Custom Pillar Stack Sovereign

[ ] Package 3 — Single Pillar Sentinel

[ ] Ninety-day named-user land is the default cadence for the elected Package(s) — Full Platform + 1 named user USD 0.00 per selected plane; additional named users by volume band; expires day 90

[ ] Think-tank license SKU (A.2.5c) — Gated Institution-Community; Partner ID required; USD 0.00 named-user seats for admitted operators

AWS Marketplace SKU / private-offer ID (platform × named-user band × cadence; Order Form fees control): ______________________________

Think-tank license (A.2.5c) — complete when that SKU is selected:

Partner ID: EOG-P-____________

Track: [ ] Design Partner [ ] Academic / Research Institution

Licensed use: [ ] Research / lab [ ] Internal design-partner operators

(Not production Governance and Loss Prevention of a live book, live wallets, live HOS/ELD, or live PHI.)

Named-user cohort cap: ________ operators (own operators only; no gift, resale, or white-label)

Contribution clock: significant improvement material every 180 days from Partner ID issuance (implementation not required)

[ ] Customer acknowledges that production use of a live book converts Think-tank seats to paying named-user bands on this same industry platform; the contribution rider may continue

[ ] Provider may request non-classified usage summaries (operator count; whether handshake is pointed at production rails). Dual Vault, PHI, and classified examiner packs are not ingested

Full kernel remains armed (halt, HTTP 423, CIP, Dual Vault, handshake, Healthcare PHI DLP on the Healthcare plane only)

Payment cadence:

[ ] Annual in advance — AWS Marketplace private offer only (not the listing default)

[ ] 12-month monthly payment term (Exhibit A.2.8) — Packages 1–3, including renewals; **AWS Marketplace Checkout** (listing default)

Applicable Risk Domain/Pillar (Package 3 — exactly one; only functionality tied to that named pillar is deployed): __________ (P1–P12)

Applicable Risk Domain/Pillars (Package 2 — list each; only functionality tied to those named pillars is deployed):

_________________________________________________________________

Schedule A-2 — Mapped field-agent roster for the named pillars above (Provider completes from the Agent Roster in Provider Documentation; attach sheet if needed):

_________________________________________________________________

ω coverage % (Package 2 required; Package 3 advisory): _________ %

Mandatory & universal lines (all packages):

[ ] K13 + MRM Quad (Mandatory Bundle) $________ / yr [ ] 90-day land: USD 0.00 for 90 days

[ ] EOG-DUAL-VAULT-STD $________ / yr [ ] 90-day land: USD 0.00 for 90 days (included)

[ ] EOG-POL-GOV-STD (Control Objective #1) $________ / yr [ ] 90-day land: USD 0.00 for 90 days

[ ] Customer acknowledges sole responsibility for all infrastructure, hosting, cloud, HSM, Dual-Vault backends, and related third-party costs (Exhibit B) — never included in Subscription Fees or the USD 0.00 platform license

Deployment tier (operational footprint, not a seat rate): [ ] D1 [ ] D2 [ ] D3

Platform Integrity SLA (Exhibit E.3):

Jurisdictions / regulatory scope: ___________________________________

PI metric targets: [ ] Standard (per Exhibit E.3.1) [ ] Custom: _______

Optional PS SOW #: ____

Environments:

[ ] Production URL: ____________________

[ ] Staging URL: _______________________

Client Operating Platform (Exhibit B.5):

[ ] B-GCP (reference only) [ ] B-AWS [ ] B-AZURE [ ] B-HYBRID [ ] B-COLO [ ] B-ONPREM [ ] B-BAREMETAL [ ] B-EDGE

Hybrid / notes: _________________________________________________

Dual-Vault (Exhibit B.4 — required for Packages 1–3 and ninety-day named-user land):

Operational Vault backend: _______________________________________

Immutable Archive Vault backend: _________________________________

[ ] Dual-Vault Security Manual minimums accepted (no material deviation)

[ ] Deviation addendum attached: __________________________________

Feed registry size: 96 logical governance feeds per gateway instance (default). Count is configurable. Enterprise scale uses additional gateway instances and a Customer aggregation plane. Not a warranty of 96 live source systems or ingest throughput.

Enterprise aggregator: [ ] Customer [ ] Provider SOW [ ] N/A

Fees:

Named-user Subscription Fees (same rates on Packages 1–3): $________

12-month monthly payment term amount (if elected): $________ (annual / 12 — no APR)

Healthcare PHI Vault (Healthcare only; separate line, not in named-user seats): USD 0.00 during the 90-day term; USD 9,000 / yr after conversion (or USD 750 / month on the 12-month monthly payment term)

90-day named-user fees: **USD ________** (1 named user = USD 0.00; otherwise quantity × band rate)

Day-90 posture credit: **full credit of 90-day named-user fees** if desired risk posture is achieved and Customer continues (Customer infrastructure never credited)

Rebate clock: **every new subscriber is a trial organization** — clock starts during the 90-day term and continues on paid licenses (no direct Package 1 skip)

Customer infrastructure / hosting / cloud / HSM / Dual-Vault backends: **Customer sole cost — not included**

Defense Fund allocation (12% of named-user Subscription Fees — Exhibit I.2): $________ [ ] embedded in subscription [ ] N/A (USD 0.00 land = 12% of USD 0.00)

One-time implementation: N/A (installation and training are streamlined)

Advisory Committee engagements (Exhibit F, if any): contracted directly with the Advisor under the Advisor’s own engagement agreement; not a Provider fee

Payment terms: per AWS Marketplace invoice; the license is switched off if an AWS Marketplace charge fails or is unpaid

Payment processor: [x] AWS Marketplace Checkout

Partner / Reseller / Think-tank / Contributor signup (not AWS): https://eyes-on-glass.io/Partners

[ ] Overlay-patent value-add (§1.9(3)) — same Think-tank methodology: Customer may file originated improvements; exclusive license-back; 75% of third-party royalties on that overlay; background IP stays Provider

Install kit delivery: parent kit workflow for selected scope, then the client deployment package for each selected industry platform, after AWS Marketplace subscription confirmation

Sovereign Posture Rebate (Exhibit I) — direction of 10% rebate if earned:

[ ] (1) 100% donate to Global Sovereign Defense Fund

[ ] (2) Split: _____% donate / _____% subscription credit

[ ] (3) 100% credit against next year's Subscription Fees

Exhibits incorporated: A, B, C, D, E, I [F if SOW] [H if redlines]

Contract Modifications (Section 1.20 / Exhibit H):

[ ] None — standard form executed without Material Technical Modifications

[ ] Material technical redlines attached; Exhibit H executed: [ ] Yes [ ] N/A

[ ] Commercial/legal redlines only (no Exhibit H required): [ ] Yes

Authorized signatories:

Customer: ___________________ Date: _______

Provider: ___________________ Date: _______

Exhibit H — Acknowledgment of Material Technical Modifications (Redlines)

When to use: Execute this Exhibit only when Customer (or Customer’s procurement, legal, or technical representatives) proposes or insists upon Material Technical Modifications—redlines that materially depart from Provider’s standard technical Exhibits, operating requirements, security minimums, performance assumptions, incorporated technical manuals, or SLA measurement methodology.

When not required: Customary commercial and legal redlines (fees, payment terms, term, governing law, venue, insurance, confidentiality, liability caps) that do not change technical Exhibits or introduce new technical/performance commitments do not require Exhibit H.

H.1 Acknowledgment

By signing below, Customer acknowledges and agrees:

1. Redlines are anticipated. Customer understands that negotiation and redlining of enterprise agreements is common. This Exhibit applies only where Customer requests changes to technical or performance-related terms—not routine commercial or legal terms.
2. Functional impact. Customer understands that Material Technical Modifications may degrade, impair, or eliminate functionality of the Eyes on Glass / SOaaS platform as designed, including governance workflows, Dual-Vault promotion paths, ingest and aggregation behavior, handshake and onboarding flows, assessment/KPI outputs, AI-assisted features, audit trails, and integration with Customer’s chosen Client Operating Platform footprint.
3. Performance impact. Customer understands that Material Technical Modifications may degrade performance, including throughput, latency, availability, scalability, and cost efficiency, particularly where modifications relax Exhibit B or B.4 requirements, Exhibit C performance assumptions, enterprise ingest topology constraints, or Customer’s obligation to maintain an adequate Client Operating Platform and aggregation plane.
4. Security and compliance impact. Customer understands that Material Technical Modifications to security, encryption (including AES-256-GCM minimums), key management, access control, Dual-Vault separation of duties, or archive immutability may weaken Customer’s security posture and may invalidate assumptions in Provider’s Documentation and deployment packet.
5. Provider reliance. Provider has designed, tested, and documented the Services against its standard Agreement and Exhibits. Customer accepts that Provider does not warrant the same functionality, performance, security, or SLA outcomes for technically modified configurations unless Provider issues a written Impact Assessment expressly accepting specified deviations and any adjusted commitments.
6. Customer assumption of risk. To the extent a Material Technical Modification contributes to reduced functionality, performance, security, or compliance outcomes, Customer assumes that risk and will not assert that Provider failed to meet Documentation or Exhibit requirements that were modified, waived, or replaced by Customer’s redlines, except as expressly restated in a Provider-signed Impact Assessment.
7. Support scope. Support and remedies under Exhibit E may exclude or be limited for incidents caused by or attributable to Material Technical Modifications, unless otherwise agreed in writing.

H.2 Description of Material Technical Modifications (attach redline)

Redline attachment: [ ] Attached as Redline Schedule H-2 (required if any material technical or performance term is modified)

Provider Impact Assessment issued: [ ] Yes — ID/date: ______________ [ ] No — Customer proceeds without Provider technical sign-off

H.3 Signatures

Customer acknowledges Sections H.1–H.2.

Customer legal name: _______________________________________________

By: _________________________________ Title: _______________________

Date: _______________

Provider acknowledgment (optional; does not expand warranty absent Impact Assessment):

By: _________________________________ Title: _______________________

Date: _______________

Exhibit I — Sovereign Posture Rebate & Global Sovereign Defense Fund

I.1 Purpose — performance bond, not a discount

The Sovereign Posture Rebate is a performance bond: Provider commits to return a portion of Subscription Fees when Customer demonstrates sustained Strong Risk Posture using the Eyes on Glass governance engine in production. It is not an automatic discount, volume rebate, or refund for infrastructure outages (environmental performance remains Customer’s responsibility per Exhibit C).

The rebate rewards governance discipline measured deterministically by K13 as licensed Risk Domain/Pillar PASS (Exhibit I.4). Platform Integrity Metrics (PI-1–PI-6, Exhibit E.3) remain Provider SLA measures and service-credit gates. Eligibility is not subject to subjective scoring or human override. K13’s sealed monthly Sovereign Posture Attestation is final and conclusive for rebate eligibility (Exhibit I.4.3).

I.1.1 Commercial rationale *(explanatory — not a warranty)*

The following describes why Provider offers the Sovereign Posture Rebate and Defense Fund structure. Only Sections I.2–I.8 (and cross-referenced Exhibits) create binding obligations. Metrics below (e.g., net revenue retention) are commercial objectives, not guarantees.

I.2 Global Sovereign Defense Fund

The Global Sovereign Defense Fund (“Defense Fund”) capitalizes the Sovereign Posture Rebate and supports public-good initiatives against financial crime and cyber breach. Governance mechanics below are binding on Provider.

I.2.1 Fund governance framework

I.2.2 Administration summary

I.3 Sovereign Posture Rebate amount

I.4 Strong Risk Posture — deterministic measurement

I.4.1 Computation authority (K13 + Sovereign Hash)

I.4.2 Licensed Risk Domain/Pillar PASS (all required, every month)

A Customer is in Strong Risk Posture for a calendar month on a selected industry plane when K13 determines that every licensed Risk Domain/Pillar on that plane PASSes for that month (production, non-sandbox). Licensed scope is the Pronged Purchase Package for that plane on the Order Form (Schedule A-2), not the six Platform Integrity Metrics in Exhibit E.3.1, and not unselected industry platforms. Catalogs never mix, so K13 does not attest a single hash across planes:

The 90-day named-user term does not pay the Sovereign Posture Rebate at day 90. Every new subscriber is a trial organization: the twelve-month Qualification Period starts during the ninety-day term on that selected plane. At day 90, if Customer is in Strong Risk Posture on that plane and continues on that same industry platform, 90-day named-user fees for that plane are fully credited against the conversion Order Form per A.2.5b, and PASS months earned on that plane carry forward (the clock does not restart). There is no direct Package 1 skip of that clock. Customer infrastructure is never credited. Unused industry platforms are not scored.

Prerequisites (not PI metrics): (a) production non-sandbox deployment on that plane; (b) minimum telemetry for K13 to evaluate each licensed Risk Domain/Pillar on that plane; (c) no active break-glass window in the month (I.4.1).

Twelve-month rule. Customer earns rebate eligibility for a selected plane only if every licensed Risk Domain/Pillar on that plane PASSes in each of twelve (12) consecutive calendar months. One FAIL on any licensed Risk Domain/Pillar on that plane in any month resets that plane’s Qualification Period. A FAIL on plane A does not reset plane B.

Payment prerequisite (not a posture condition). Subscription Fees for the Qualification Period must be current per Section 1.8 before rebate issuance.

I.4.3 Attestation (final and conclusive)

I.5 Rebate direction — Customer election (Order Form)

After earning a Sovereign Posture Rebate, Customer directs payment as elected on the Order Form (may change annually on renewal notice):

Provider issues rebate within 60 days after Qualification Period completion and posture attestation. Donation portions are acknowledged in writing for Customer’s records.

I.6 Relationship to other remedies

I.7 Exclusions

Rebate is not earned for months affected by: sandbox/demo; unsubscribed agents; Customer platform failures preventing posture measurement; Material Technical Modifications without Impact Assessment; force majeure; or Customer’s failure to maintain Exhibit B minimums.

I.8 Tax and regulatory

10. Insurance (SCMP Section 11.2)

Provider maintains commercially insured Professional Liability (Errors and Omissions) coverage, issued through biBerk (a Berkshire Hathaway company) under policy N8PL996825, with limits of $2,000,000 per occurrence and $2,000,000 in the aggregate, for the policy term November 4, 2026 through November 4, 2027, and will renew or replace that coverage with comparable limits for so long as the Agreement is in effect. Under SCMP Section 11.2, Provider satisfies any other insurance obligation under SCMP Section 11.1 that is not commercially insured through a self-insured retention program. On Buyer's request, Provider will deliver a certificate of insurance for its commercially insured coverage and, for any self-insured coverage, a declaration on Provider letterhead signed by an authorized officer of Provider. A copy of the certificate of insurance for that policy is Exhibit A (Certificate of Insurance). Insurance, whether commercial or self-insured, does not limit Provider's liability under the Agreement.

Exhibit A — Certificate of Insurance (biBerk Professional Liability, Policy N8PL996825)

ACORD 25 Certificate of Liability Insurance dated 11/03/2026. Insurer: National Liability & Fire Insurance Company (NAIC 20052). Professional Liability (Errors & Omissions), claims-made, policy N8PL996825, $2,000,000 per occurrence / $2,000,000 aggregate, $1,000 deductible, policy period 11/04/2026–11/04/2027.

Download the certificate of insurance (PDF)

Sentinel Risk Intelligence Labs LLC · eyes-on-glass AWS Marketplace EULA