labs: reconcile modules 02+03 on main — transactional search index moves to subject

The documented merge-time collision (article 3 header MERGE NOTE): a SEARCH
index and the HVI's text component are the same indextype and cannot share the
body column (ORA-29879), and the HVI's text component does NOT sync on commit
(verified empirically 2026-07-24 — a committed probe row was not
CONTAINS-findable through the HVI). So on main:

- 05-text-vector: ticket_text_idx (SYNC ON COMMIT) now indexes SUBJECT
- 09-hybrid-index: drop of ticket_text_idx removed — HVI owns body, no collision
- module 02 proof 3: marker token moves to the subject; CONTAINS(subject, ...)
  (the article/02 branch keeps the published body-marker form)
- READMEs: index table + module map updated (module 03 on main, 23 assertions)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: rhoulihan

labs/converged-database-lab/README.md

@@ -80,8 +80,10 @@ All modules run against one deterministically seeded domain. Seeds use an LCG (s
 | `idx_orders_customer` | B-tree | Customer order range scans |
 | `idx_items_product` | B-tree | Product-level aggregations |
 | `idx_tickets_customer` | B-tree | Per-customer ticket lookups |
-| `ticket_text_idx` | Oracle Text (SEARCH INDEX) | Full-text keyword search on ticket bodies |
-| `ticket_vec_idx` | Vector IVF (NEIGHBOR PARTITIONS, COSINE) | Approximate nearest-neighbor on embeddings |
+| `ticket_text_idx` | Oracle Text (SEARCH INDEX, SYNC ON COMMIT) | Transactional keyword search on ticket subjects (module 02's read-after-write proof; body text search belongs to the HVI) |
+| `ticket_vec_idx` | Vector IVF (NEIGHBOR PARTITIONS, COSINE) | Approximate nearest-neighbor on 8-dim demo embeddings |
+| `tickets_bodyvec_ivf` | Vector IVF (NEIGHBOR PARTITIONS, COSINE) | ANN on the real 384-dim `body_vec` embeddings (module 03) |
+| `tickets_hvi` | Hybrid Vector Index (Text + vector, one domain index) | Fused keyword + semantic search on ticket bodies (module 03) |
 
 **Note on embeddings:** The 8-dim vectors are deterministic demo values generated by the LCG seed. All engine behaviors demonstrated (distance functions, vector indexes, transactions, cross-model joins) are dimension-independent. Module 03 documents the optional real-model flow using `DBMS_VECTOR.LOAD_ONNX_MODEL` with all-MiniLM-L12-v2.
 
@@ -95,7 +97,7 @@ All modules run against one deterministically seeded domain. Seeds use an LCG (s
 |---|------|--------|--------|------------|-------|
 | 01 | `what-is-a-converged-database` | Live | 5 | 20 | [README](modules/01-what-is-a-converged-database/README.md) · [article](https://blogs.oracle.com/developers/what-is-a-converged-database-definition-five-tests-and-ai-use-cases) |
 | 02 | `converged-vs-multi-model` | Live | 3 | 18 | [README](modules/02-converged-vs-multi-model/README.md) · [article](https://blogs.oracle.com/developers/converged-database-vs-multi-model-database-whats-the-difference) |
-| 03 | `vector-vs-converged` | On branch, CI-green — article in draft | 4 | 19 | [README](https://github.com/oracle-devrel/oracle-umt-developer-hub/blob/article/03-vector-vs-converged/labs/converged-database-lab/modules/03-vector-vs-converged/README.md) · [branch](https://github.com/oracle-devrel/oracle-umt-developer-hub/tree/article/03-vector-vs-converged) · article at publish |
+| 03 | `vector-vs-converged` | On main, validated — article in draft | 4 | 23 | [README](modules/03-vector-vs-converged/README.md) · [branch](https://github.com/oracle-devrel/oracle-umt-developer-hub/tree/article/03-vector-vs-converged) · article at publish |
 | 04 | `ai-agents-enterprise-data` | On branch, CI-green — article in draft | 3 | 16 | [README](https://github.com/oracle-devrel/oracle-umt-developer-hub/blob/article/04-ai-agents-enterprise-data/labs/converged-database-lab/modules/04-ai-agents-enterprise-data/README.md) · [branch](https://github.com/oracle-devrel/oracle-umt-developer-hub/tree/article/04-ai-agents-enterprise-data) · article at publish |
 | 05 | `json-graph-vector-relational` | On branch, CI-green — article in draft | 4 | 26 | [README](https://github.com/oracle-devrel/oracle-umt-developer-hub/blob/article/05-json-graph-vector-relational/labs/converged-database-lab/modules/05-json-graph-vector-relational/README.md) · [branch](https://github.com/oracle-devrel/oracle-umt-developer-hub/tree/article/05-json-graph-vector-relational) · article at publish |
 | 06 | `secure-agent-access` | On branch, CI-green — article in draft | 4 | 7 | [README](https://github.com/oracle-devrel/oracle-umt-developer-hub/blob/article/06-secure-agent-access/labs/converged-database-lab/modules/06-secure-agent-access/README.md) · [branch](https://github.com/oracle-devrel/oracle-umt-developer-hub/tree/article/06-secure-agent-access) · article at publish |

labs/converged-database-lab/docker/init/05-text-vector.sql

@@ -1,14 +1,23 @@
 ALTER SESSION SET CONTAINER = FREEPDB1;
 ALTER SESSION SET CURRENT_SCHEMA = lab_user;
 
--- Oracle Text index on ticket bodies: keyword search in the same engine/transaction.
--- SYNC (ON COMMIT): the index syncs inside the committing transaction, so a
--- committed row is immediately findable via CONTAINS — transactional
--- read-after-write search (module 02 proves this). The 26ai Free default for
--- CREATE SEARCH INDEX is MAINTENANCE AUTO with deferred background sync
--- (ctx_user_indexes showed IDX_SYNC_TYPE = MANUAL), under which a probe row was
--- NOT visible to CONTAINS immediately after COMMIT.
-CREATE SEARCH INDEX ticket_text_idx ON support_tickets (body)
+-- Oracle Text index on ticket SUBJECTS: keyword search in the same
+-- engine/transaction. SYNC (ON COMMIT): the index syncs inside the committing
+-- transaction, so a committed row is immediately findable via CONTAINS —
+-- transactional read-after-write search (module 02 proves this). The 26ai Free
+-- default for CREATE SEARCH INDEX is MAINTENANCE AUTO with deferred background
+-- sync (ctx_user_indexes showed IDX_SYNC_TYPE = MANUAL), under which a probe
+-- row was NOT visible to CONTAINS immediately after COMMIT.
+--
+-- MERGE RECONCILIATION (modules 02 + 03 together on main): this index lives on
+-- SUBJECT here, not BODY. Module 03's Hybrid Vector Index owns body text search
+-- (an HVI's text component is the same indextype as a SEARCH index — two cannot
+-- share a column, ORA-29879), and the HVI's text component does NOT sync on
+-- commit (verified empirically 2026-07-24: a committed probe row was not
+-- CONTAINS-findable through the HVI). Module 02's read-after-write proof
+-- therefore probes the subject column on main; the article/02 BRANCH keeps the
+-- body form that the published article's snippets byte-match.
+CREATE SEARCH INDEX ticket_text_idx ON support_tickets (subject)
   PARAMETERS ('SYNC (ON COMMIT)');
 
 -- Vector index. IVF (NEIGHBOR PARTITIONS) — works within Free-tier memory without

labs/converged-database-lab/docker/init/09-hybrid-index.sql

@@ -7,30 +7,23 @@ ALTER SESSION SET CURRENT_SCHEMA = lab_user;
 -- Leaf-3-specific: the foundational model + body_vec + IVF live in 08 (on main);
 -- this HVI is the article-3 hybrid-search showcase and stays on this branch.
 --
--- COLLISION NOTE: a CONTEXT/SEARCH text index and the HVI's internal text
--- component are the SAME indextype, so two cannot sit on the same column
--- (ORA-29879). The shared 05-text-vector.sql creates ticket_text_idx (a SEARCH
--- index) on body; this module needs the richer body text for a meaningful hybrid
--- proof, so we DROP ticket_text_idx here and let the HVI own body's text search.
--- The HVI exposes the same CONTAINS(body, ...) capability, so keyword-only search
--- still works. (On the eventual merge with the module-02 branch, whose
--- read-after-write SEARCH proof uses ticket_text_idx, that proof moves to the HVI
--- or to the subject column — a merge-time decision.)
+-- COLLISION NOTE — RESOLVED ON MAIN: a CONTEXT/SEARCH text index and the HVI's
+-- internal text component are the SAME indextype, so two cannot sit on the same
+-- column (ORA-29879). On main, 05-text-vector.sql creates ticket_text_idx on
+-- SUBJECT (SYNC ON COMMIT, for module 02's transactional read-after-write
+-- proof) and this HVI owns BODY text search (module 03's hybrid proof) —
+-- different columns, no collision, so the branch-era ticket_text_idx drop is
+-- gone. The HVI's text component does NOT sync on commit (verified 2026-07-24),
+-- which is why module 02's proof cannot ride on the HVI.
 --
 -- VECTOR_IDXTYPE IVF keeps the HVI's vector component off the Vector Pool
 -- (Free-safe); MEMORY 256M caps the Oracle Text build memory modestly. Builds in
--- ~6s on the Free container.
+-- a few minutes over the 10,000-ticket corpus on the Free container.
 DECLARE
 BEGIN
   EXECUTE IMMEDIATE 'DROP INDEX tickets_hvi';
 EXCEPTION WHEN OTHERS THEN NULL; /* absent — first run */
 END;
 /
-DECLARE
-BEGIN
-  EXECUTE IMMEDIATE 'DROP INDEX ticket_text_idx';
-EXCEPTION WHEN OTHERS THEN NULL; /* HVI takes over body text search */
-END;
-/
 CREATE HYBRID VECTOR INDEX tickets_hvi ON support_tickets(body)
   PARAMETERS('MODEL MINILM_L12 VECTOR_IDXTYPE IVF MEMORY 256M');

labs/converged-database-lab/modules/02-converged-vs-multi-model/README.md

@@ -92,7 +92,12 @@ immediately does not. Search visibility arrives with the commit, in the same
 engine, with no separate search process, change stream, or refresh interval.
 The lab's `ticket_text_idx` is created with `PARAMETERS ('SYNC (ON COMMIT)')`
 (`docker/init/05-text-vector.sql`), so the text index syncs inside the
-committing transaction.
+committing transaction. On main, this index lives on the ticket **subject**
+(the marker token travels in the subject accordingly): module 03's Hybrid
+Vector Index owns body text search, and an HVI's text component does not sync
+on commit — the transactional read-after-write property this proof
+demonstrates needs the dedicated SYNC(ON COMMIT) index. The article/02 branch
+keeps the body-marker form that the published article's snippets byte-match.
 
 **Commit exception:** this script intentionally COMMITs (read-after-write can
 only be shown across a real commit boundary), so the harness rollback does not

labs/converged-database-lab/modules/02-converged-vs-multi-model/scripts/03-read-after-write-search.sql

@@ -7,6 +7,14 @@ DELETE /* Module 02 proof 3: transactional read-after-write text search.
    syncs inside the committing transaction, so search visibility arrives WITH
    the commit, not eventually after it.
 
+   MAIN-BRANCH RECONCILIATION: on main the SYNC(ON COMMIT) search index lives
+   on SUBJECT (module 03's Hybrid Vector Index owns body text search, and the
+   HVI's text component does not sync on commit — verified 2026-07-24), so
+   this proof carries its marker token in the subject and probes
+   CONTAINS(subject, ...). The article/02 branch keeps the body-marker form
+   that the published article's snippets byte-match; the property proven —
+   search visibility inside the committing transaction — is identical.
+
    COMMIT WARNING: this script intentionally COMMITs — a documented exception
    to the rollback contract (see the module README). Read-after-write through
    a text index can only be demonstrated across a real commit boundary.
@@ -17,32 +25,32 @@ DELETE /* Module 02 proof 3: transactional read-after-write text search.
 
    This first statement is an idempotence guard: remove any probe rows left by
    a previously interrupted run (committed together with the INSERT below). */
-FROM support_tickets WHERE subject = 'm02 rw-search probe';
+FROM support_tickets WHERE subject LIKE 'm02 rw-search probe%';
 
 INSERT INTO support_tickets (customer_id, subject, body, status)
-VALUES (1, 'm02 rw-search probe',
-        'read-after-write search probe, marker token zzqxw9347', 'open');
+VALUES (1, 'm02 rw-search probe zzqxw9347',
+        'read-after-write search probe (marker token in subject)', 'open');
 
 COMMIT;
 
 SELECT /* the committed row is findable by CONTAINS immediately — same call
           stack, same second, no sync window */
        'ASSERT:contains-finds-committed-write:' ||
        CASE WHEN COUNT(*) = 1 THEN 'PASS' ELSE 'FAIL' END
-FROM support_tickets WHERE CONTAINS(body, 'zzqxw9347') > 0;
+FROM support_tickets WHERE CONTAINS(subject, 'zzqxw9347') > 0;
 
 DELETE /* explicit cleanup: remove the probe ticket */
-FROM support_tickets WHERE subject = 'm02 rw-search probe';
+FROM support_tickets WHERE subject LIKE 'm02 rw-search probe%';
 
 COMMIT;
 
 SELECT /* and the committed delete is just as immediately invisible to
           search — read-after-write holds in both directions */
        'ASSERT:contains-after-cleanup:' ||
        CASE WHEN COUNT(*) = 0 THEN 'PASS' ELSE 'FAIL' END
-FROM support_tickets WHERE CONTAINS(body, 'zzqxw9347') > 0;
+FROM support_tickets WHERE CONTAINS(subject, 'zzqxw9347') > 0;
 
 SELECT /* domain restored: no probe rows survive in the base table either */
        'ASSERT:probe-rows-gone:' ||
        CASE WHEN COUNT(*) = 0 THEN 'PASS' ELSE 'FAIL' END
-FROM support_tickets WHERE subject = 'm02 rw-search probe';
+FROM support_tickets WHERE subject LIKE 'm02 rw-search probe%';