# Memeroot · Oracle SQL Free

**Start here:** open `GUIDE.html` in a browser.

Sixteen tick-boxes from "extracted the zip" to "AI-assisted SQL session signed, executed on Oracle, captured, bundled." Progress saves automatically.

## What this stream demonstrates

The right architectural separation for canvas integrations with external services:

- **Canvas = workspace.** Holds the question, the AI-proposed SQL, and the captured result. Provides signing, content addressing, hash chains, bundle export.
- **Oracle Live SQL = execution engine.** Real Oracle 23c database, accessed in a separate browser tab. Runs the actual queries.
- **AI endpoint = apprentice.** Reads your plain-English question via `prompt-ref`, proposes Oracle SQL, returns it as a content-addressed response.
- **You = the bridge.** Move SQL out, results back. Sign your work. Decide what's final.

This pattern generalizes to any external service — Jupyter for data, GitHub for code, Figma for design, your IDE for compilation. The canvas captures the artifact of each external operation as a signed addressable region. The bundle ships the whole session.

## What's in this zip

```
memeroot-oracle-sql-free/
├── GUIDE.html               ← open this first
├── README.md                ← you are here
├── canvas/MR-CANVAS-v0.8.html
├── features/                ← ten feature XMLs to drop on the canvas
├── identity/
│   └── identity-tour-author.json   ← public-only identity for name attribution
├── stylesheets/             ← three tone-stylesheets (terse/public/annotated)
└── stream/                  ← the tour itself
    ├── stream-oracle-sql-free.xml
    └── chunk-oracle-1.xml … chunk-oracle-5.xml
```

## What you'll need outside the canvas

A free Oracle Cloud account for [Oracle Live SQL](https://livesql.oracle.com). Email signup, ~2 minutes, no payment info required for the free tier.

## Verification

- Every chunk in the stream is signed by `oracle-sql-tour-author` (ECDSA-P256). Verify in the canvas's signature reader.
- Every chunk's `curr` attribute = SHA-256(prev + canonical content). Verify in the Streams tab.
- Every AI response carries a SHA-256 content hash. Anyone citing the response can verify the text is unchanged.
- Your own signatures attribute the question + result regions to you.

The whole session bundles into one file at the end. The recipient drops it into their own canvas and re-verifies everything — no infrastructure required.