Skip to content
Merged
Changes from all commits
Commits
Show all changes
50 commits
Select commit Hold shift + click to select a range
4a8c6c4
Add files via upload
JavaDude42 Apr 13, 2026
f688b39
Social Commerce App Init
JavaDude42 Apr 14, 2026
7dc670c
Add files via upload
JavaDude42 Apr 14, 2026
176d3b5
File structure issue
JavaDude42 Apr 14, 2026
1ced24c
Merge branch 'oracle-livelabs:main' into main
JavaDude42 Apr 14, 2026
0b4ad72
Update introduction.md
JavaDude42 Apr 14, 2026
d3a8317
Merge remote-tracking branch 'upstream/main'
JavaDude42 Apr 14, 2026
51f4d93
Update introduction.md
JavaDude42 Apr 14, 2026
b9b6d5d
Update introduction.md
JavaDude42 Apr 14, 2026
5be0034
Final MVP Fixes
JavaDude42 Apr 15, 2026
45ce54c
Merge branch 'main' into main
JavaDude42 Apr 15, 2026
9fadb00
Merge remote-tracking branch 'upstream/main'
JavaDude42 May 11, 2026
acff689
This is for the demo
JavaDude42 May 11, 2026
8e40ed4
Merge branch 'main' into main
JavaDude42 May 11, 2026
8b8fc3f
Bad files removed
JavaDude42 May 11, 2026
e917831
Merge branch 'main' of https://github.com/JavaDude42/database
JavaDude42 May 11, 2026
ff4a448
One file update
JavaDude42 May 11, 2026
c99872d
LiveStack LiveLab - Regail
JavaDude42 May 22, 2026
a332107
Merge branch 'main' into main
JavaDude42 May 22, 2026
b22bc99
LiveStack LIveLab Retail Ready for Review
JavaDude42 May 24, 2026
08edade
Merge branch 'main' into main
JavaDude42 May 24, 2026
afce345
Update Retail LiveStack workshop
JavaDude42 May 26, 2026
a1991bc
Merge branch 'main' into main
JavaDude42 May 26, 2026
ff1b17f
Ready for review and testing
JavaDude42 May 27, 2026
041529b
Merge branch 'main' into main
JavaDude42 May 27, 2026
cd8db65
Merge branch 'main' of https://github.com/JavaDude42/database
JavaDude42 May 27, 2026
0997da7
Removed Back end provisioning
JavaDude42 May 27, 2026
f9b8ae3
Fixed a few things
JavaDude42 May 28, 2026
f1fb5ac
Merge branch 'main' into main
ramonamagadan18 May 28, 2026
5a89265
Final Pre Testing Build
JavaDude42 May 29, 2026
c854a3b
Merge branch 'main' into main
JavaDude42 May 29, 2026
7af8356
Final Production Build
JavaDude42 Jun 1, 2026
20a1881
Merge branch 'main' into main
JavaDude42 Jun 1, 2026
75ae92c
Delete AGENTS.md
JavaDude42 Jun 1, 2026
21253ef
Merge branch 'main' of https://github.com/JavaDude42/database
JavaDude42 Jun 1, 2026
55e2fd5
Improved JSON Lab
JavaDude42 Jun 1, 2026
c6375e8
Merge branch 'main' into main
JavaDude42 Jun 1, 2026
d7ab0ab
Vastly updated Vector Search lab
JavaDude42 Jun 1, 2026
057cc9d
Greatly improved version
JavaDude42 Jun 2, 2026
6b8e670
Merge branch 'main' into main
JavaDude42 Jun 2, 2026
3d310a2
Close to done. only labs 8 and 9 remain
JavaDude42 Jun 2, 2026
538832e
Merge branch 'main' into main
JavaDude42 Jun 2, 2026
23948c8
Business language focus
JavaDude42 Jun 3, 2026
c5fcdcc
Merge branch 'main' into main
JavaDude42 Jun 3, 2026
99436eb
Final push
JavaDude42 Jun 3, 2026
0040574
Merge branch 'main' of https://github.com/JavaDude42/database
JavaDude42 Jun 3, 2026
80fd409
Merge branch 'main' into main
JavaDude42 Jun 3, 2026
5c78597
One more change
JavaDude42 Jun 3, 2026
473d4e4
Merge branch 'main' of https://github.com/JavaDude42/database
JavaDude42 Jun 3, 2026
959ecb0
Merge branch 'main' into main
JavaDude42 Jun 3, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -27,26 +27,11 @@ Estimated Time: **5 minutes**

## Task 1: Review the final outcome

Perform the following set of steps to connect each lab back to the same retail decision loop and database foundation.
Connect each lab back to the same retail decision loop and database foundation.

1. Review the workshop flow from the database point of view.

This final query ties every lab back to a retail decision and the database evidence behind it. `UNION ALL` stacks several short result sets into one evidence map. Each row names a signal, the screen where the learner saw it, and the Oracle Database evidence behind the screen. Use the result to explain the workshop as one governed decision loop across the major database features.

```sql
<copy>
SELECT 'Operating picture' AS "Signal", 'Retail Command Center' AS "Scene", 'ORDERS, SOCIAL_POSTS, INVENTORY, RETURN_REQUESTS, and AGENT_ACTIONS' AS "Database Evidence" FROM dual
UNION ALL SELECT 'Viral demand', 'Customer Trend Signals', 'SOCIAL_POSTS, PRODUCT_EMBEDDINGS, and SEMANTIC_MATCHES' FROM dual
UNION ALL SELECT 'Creator propagation', 'Creator Influence Network', 'INFLUENCER_NETWORK property graph' FROM dual
UNION ALL SELECT 'Fulfillment distance', 'Intelligent Fulfillment Network', 'SDO_GEOMETRY locations and SDO_DISTANCE' FROM dual
UNION ALL SELECT 'Order state', 'Unified Order Intelligence', 'ORDERS_DV JSON Relational Duality view' FROM dual
UNION ALL SELECT 'ML prediction', 'Retail OML Analytics', 'DBMS_DATA_MINING models and OML feature views' FROM dual
UNION ALL SELECT 'Plain-English analytics', 'Ask Retail Data', 'Semantic views, comments, and visible SQL' FROM dual
UNION ALL SELECT 'Agent action', 'Retail AI Agent Console', 'PL/SQL tools and AGENT_ACTIONS audit rows' FROM dual;
</copy>
```

Expected output:
This table ties every lab back to a retail decision and the database evidence behind it. Each row names a signal, the screen where you saw it, and the Oracle Database evidence behind the screen. Use it as the final map of the workshop: one governed decision loop across the major database capabilities.

| Signal | Scene | Database Evidence |
| --- | --- | --- |
Expand All @@ -64,15 +49,19 @@ Perform the following set of steps to connect each lab back to the same retail d

## Task 2: Explain the workshop flow

Perform the following set of steps as one connected retail operating pattern, not a set of disconnected database feature demos.
Use this final task to connect the technical work to the business outcome.

1. From retail signal to trusted action

Seer Sporting Goods can now follow a retail signal from first observation to trusted action. A product starts to trend. The business sees it in the command center. Vector search connects customer language to products by meaning. The graph shows how influence spreads. Spatial analysis helps choose practical fulfillment paths. JSON Relational Duality lets applications work with order documents while the database stores relational rows. OML scores likely demand changes in the database. Ask Retail Data shows how a business question can be traced to governed SQL. The agent console shows that an AI action can be routed through approved tools and written to an audit trail.

2. One database foundation

1. Use this concise summary to explain the workshop flow.
The power of the workshop is not any single feature in isolation. The power is that the features work together around the same operational data. Oracle AI Database 26ai keeps documents, vectors, graphs, spatial data, machine learning, SQL, security, and agent evidence close to the source of truth. That means fewer copies, fewer disconnected systems, and a clearer path from business question to database evidence to action.

```text
Seer Sporting Goods connects product demand, customer signals, creator influence, fulfillment routing, order documents, in-database machine learning, natural-language SQL, and auditable agent actions through one Oracle AI Database 26ai foundation.
```
3. The operating pattern

2. Close with the same idea that opened the lab: less data movement, clearer decisions, and a direct path from evidence to action. The workshop is not a set of disconnected feature demos. It is one retail operating pattern where Oracle Database 26ai keeps the data, AI, security, analytics, and agent history together.
The retail team does not just get a dashboard, a model, a graph, or an agent. It gets a governed decision loop: observe demand, understand why it is happening, decide how to respond, act through trusted database-backed tools, and prove what happened afterward.

## Acknowledgements

Expand Down
Loading