--- type: source-summary title: 'Source: oracle-comparison.html' modified: 2026-04-07 tags: - oracle-comparison - competitive - governance - source - preston-test --- # Source: oracle-comparison.html ## What this source is The **Oracle competitive differentiation page** — an HTML-rendered comparison of Oracle NSIP (Oracle's NetSuite Integration Proxy, their AI-powered iPaaS) vs SuiteCentral 2.0. Page-dated February 2026. Referenced in all three [[pages/concepts/three-review-paths|review paths]] as the governance-differentiation artifact and in [[sources/09-claim-proof-matrix]] as the proof for claim #4 ("Oracle differentiation is explicit"). Read directly from the canonical Preston-Test HTML file. Text + matrix extracted; HTML/CSS scaffolding omitted. The page is built around two structural elements: 1. **A side-by-side demo** showing the same mapping ("Revenue" → "revenue_field") through Oracle NSIP vs SuiteCentral 2.0 — concrete, not abstract. 2. **An 8-row feature matrix** comparing AI governance capabilities head-to-head. ## Key claims 1. **Oracle NSIP = Oracle's NetSuite Integration Proxy** — the native AI iPaaS Oracle has launched. First formal naming of Oracle's product in the corpus. → new entity/competitor tracking. 2. **Oracle is a "black box AI"** — the page's framing. Oracle's mapping page shows only "Mapped by AI. No further details available." → [[pages/concepts/suitecentral-2-overview]] competitive thesis 3. **5 things Oracle NSIP lacks (on a specific mapping)**: - No confidence score - No reasoning trace - No hallucination detection - No human approval step - No cost visibility 4. **SuiteCentral 2.0 shows (on the same "Revenue" → "revenue_field" mapping)**: - **95% confidence** broken down as: Semantic 45% + Pattern 30% + Historical 25% → second-source confirmation of the "multi-signal confidence" claim from [[sources/narration-scripts]] - **Reasoning trace** (verbatim): *"Revenue matches revenue_field with high semantic similarity (0.94). Confirmed by 12 historical mappings across 3 prior integrations. Pattern 'direct_name_match' also satisfied. No ambiguity detected."* → concrete example of the Reasoning Trace Engine output - **Hallucination Risk: Low** — a named UI label from the Hallucination Detector - **Cost: $0.003/mapping** — matches Claude 3.5 Sonnet pricing from [[sources/26-canonical-metrics-and-wording]]. Suggests the default mapping provider is Claude. - **Approve / Reject** buttons — the Approve-to-Apply gate surface 5. **The 8-row feature matrix**: | Capability | Oracle NSIP | SuiteCentral 2.0 | |---|---|---| | Reasoning Traces | ❌ | ✅ DB-persisted per mapping | | Confidence Breakdown | ❌ | ✅ Multi-signal (semantic + pattern + historical) | | Hallucination Detection | ❌ | ✅ Built-in detector with risk scoring | | Dual-ERP Support | ⚠ NetSuite only | ✅ NetSuite + Business Central | | Approve-to-Apply | ❌ | ✅ Human-in-the-loop approval gate | | Cost Transparency | ❌ | ✅ Per-provider cost shown at mapping time | | DLP / PII Protection | ❌ | ✅ **8 PII patterns (GDPR / CCPA)** | | Governance Pacer | ❌ | ✅ API rate limit enforcement built-in | → [[pages/concepts/suitecentral-2-overview]] (competitive thesis), [[pages/concepts/claim-proof-matrix]] (claim #4) 6. **EU AI Act August 2, 2026 — CONCRETE DATE**: *"The EU AI Act takes effect August 2, 2026. High-risk AI systems used in financial processes must provide reasoning traces, human oversight, and risk assessments. Black-box AI mappings will not pass audit."* This is first formal mention of the EU AI Act enforcement date in the corpus. → (NEW) `pages/concepts/eu-ai-act-compliance` or fold into overview. 7. **SOC 2 Trust Services Criteria named as the compliance framework**: *"Approve-to-apply workflows, persisted reasoning traces, and confidence scoring provide the audit trail SOC 2 demands."* Third-source confirmation of SOC 2 TSC (now in [[sources/11-role-brief-cto]] + [[sources/read-elevator-pitch]] + [[sources/ai-governance-layer-video]] + this source + [[sources/compliance-dashboard]]). 8. **NetSuite API concurrency limit NAMED**: *"Uncontrolled AI calls can exhaust NetSuite API concurrency limits (**5 concurrent / 10 requests per second**). The Governance Pacer enforces rate limits and queuing to prevent ERP lockouts during bulk operations."* This is the first formally-ingested specific number for NetSuite's governance budget. → [[pages/concepts/suitecentral-2-overview]] (Governance Pacer section), [[pages/entities/reuben-cook]] 9. **Dual-ERP Support matrix entry**: Oracle NSIP is "NetSuite only" (amber warning), SuiteCentral 2.0 is "NetSuite + Business Central" (green). Confirms [[sources/read-talking-points]] and [[sources/ai-governance-layer-video]] dual-ERP equal-citizens claim from a new angle (competitive). 10. **"SuiteCentral 2.0 — Built by Auditors, for Auditability"** — footer tagline. Matches [[sources/compliance-dashboard]] header subtitle. Consistent branding. ## Pages updated by this ingest **Created** (1 new page): - [[pages/concepts/oracle-comparison]] — the 8-row matrix + the concrete Revenue→revenue_field example + governance-first thesis + NetSuite API concurrency limits **Updated** (3 existing pages): - [[pages/concepts/suitecentral-2-overview]] — specific NetSuite API concurrency limits (5 concurrent / 10 RPS) added to Governance Pacer detail; EU AI Act date reference - [[pages/concepts/claim-proof-matrix]] — claim #4 now links to the full 8-row matrix in the new concept page - [[pages/entities/reuben-cook]] — the concrete NetSuite API concurrency limits give Reuben a specific fact to verify ## Notable quotes > "AI without governance is a liability, not a feature." > — Why Governance Matters section header > "Uncontrolled AI calls can exhaust NetSuite API concurrency limits (5 concurrent / 10 requests per second). The Governance Pacer enforces rate limits and queuing to prevent ERP lockouts during bulk operations." > — For Operations card > "The EU AI Act takes effect August 2, 2026. High-risk AI systems used in financial processes must provide reasoning traces, human oversight, and risk assessments. Black-box AI mappings will not pass audit." > — For Auditors card > "SuiteCentral 2.0 — Built by Auditors, for Auditability" > — Footer tagline ## Cross-references / contradictions found - **DLP pattern count — CORRECTED 2026-04-07**: this source was scraped from the live page by NotebookLM and showed "8 PII patterns." The actual repo HTML snapshot says **14 patterns** (the "8" was a pre-Alpine.js scrape artifact). `DLPService.ts` implements 10 regex patterns; GovernanceService.ts adds content-filter patterns; the dashboard JavaScript snapshot lists 14 combined. See [[pages/concepts/production-proof]] for the full reconciliation. - **Resolves the "what is Oracle NSIP" question**: the hook video mentioned Oracle launching "native AI iPaaS" without naming the product. This source names it: **Oracle NSIP = NetSuite Integration Proxy**. - **The 5 concurrent / 10 RPS NetSuite limits** are a concrete, verifiable number — the kind of technical claim the CTO should sanity-check. This is the most precise governance-budget number in the corpus. - **EU AI Act and Colorado AI Act are both on the compliance dashboard** (per [[sources/compliance-dashboard]]) with Aug 2, 2026 and Jun 30, 2026 enforcement dates respectively. Flag for overview page as a regulatory timeline. - **The "Revenue" → "revenue_field" mapping is a concrete demo** — not abstract. A reviewer verifying claim #1 (AI mapping is production-usable) from the claim-proof matrix can walk this specific example and see confidence breakdown, reasoning trace, hallucination risk, cost, and approve/reject buttons all on one page. This is strong async-review design. ## Notes - The page is dated **February 2026**. Three-month refresh cycle implied if we pair this with the March 2026 refresh mentioned in [[sources/26-canonical-metrics-and-wording]]. - The page uses red ❌ / amber ⚠ / green ✅ iconography deliberately: red for "not available," amber for "partial" (NetSuite only vs full dual-ERP), green for "available." The dual-ERP row is the only amber — a subtle acknowledgment that Oracle NSIP does support NetSuite (just not Business Central). - The concrete "Revenue → revenue_field" example is the highest-density content in the page — it shows semantic similarity score (0.94), confirms by 12 historical mappings across 3 prior integrations, names the match pattern ("direct_name_match"), and explicitly states "No ambiguity detected." That's four distinct signals in one reasoning trace. - The page's "Built by Auditors, for Auditability" tagline is shared with [[sources/compliance-dashboard]] — consistent marketing language across the governance proof pages.