@stardeck-customer-apps/data-store-sdk 0.2.0 → 0.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/SKILL.md +1 -0
- package/package.json +1 -1
package/SKILL.md
CHANGED
|
@@ -307,6 +307,7 @@ try {
|
|
|
307
307
|
|
|
308
308
|
## Important Notes
|
|
309
309
|
|
|
310
|
+
- **App-code access control does NOT restrict AI agents.** Filtering rows or hiding columns in your app code (route handlers, server actions, the Kysely queries above) is the trust boundary for **human end-users in the browser** only. A scoped AI agent reads the data store **directly** through platform tools, bypassing your app code entirely — so internal fields you "hide" in a query, or a `?scope=` flag you check in a handler, do nothing to stop an agent from reading them. To keep internal data (notes, margins, internal status, churn flags) out of a customer-facing agent's reads, configure it on the **store** — a staff-only store, or per-column access tiers (`client`/`internal`) plus a per-table row policy — not in app code. See the **platform-identities** skill for how to model per-customer data and set the internal/customer-facing split.
|
|
310
311
|
- **DEPLOYMENT_SECRET must never be exposed to the client.** All data store operations must happen server-side.
|
|
311
312
|
- **Tables auto-generate** `id` (UUID), `created_at`, and `updated_at` columns. Don't include these in create table definitions.
|
|
312
313
|
- **Column deletes are soft-deletes.** The column is renamed to `_deleted_{name}_{timestamp}` and can be restored.
|