mirror of
https://github.com/Orkas-AI/Orkas.git
synced 2026-11-13 18:55:42 -10:00
wyt
1641c490da
Preserve creation, save, edit, open, preview and local execution for current and legacy app types. Enforce commercial guidance only at Publish, keeping app/draft data on cancellation or external-open failure, and carry artifact revisions and SDK schema/docs with the owning app lifecycle. Prompt confirmation: The requested public app behavior keeps unified local creation, editing, saving, preview and execution for current and legacy types. Already approved SDK query/read semantics remain in the on-demand SDK reference; artifact corrections and factual preview observations remain in their owning tool fields and receipts. The established Publish boundary excludes hosted account/quota/publication authority. Prompt audit: - Keep: Local unified creation/edit/save/preview/run and exact data/reference schemas; publication alone requires explicit commercial guidance/refusal before side effects. Type: Hard constraint. Placement: web-app-sdk references/common.md, generated public SDK references and existing app tool contracts. Actors: Authorized native app author and on-demand SDK consumer. Purpose: The established public app contract owns the already accepted product boundary; execution-layer guards enforce it, and docs describe actual public capability rather than recreate old type heuristics. - Drop: Official cloud publication/account/quota workflow and broad web/local lifecycle gates. Type: Pitfall. Placement: SDK/app mixed sources. Actors: Authorized native app author and on-demand SDK consumer. Purpose: Preserve current/legacy app data and local execution while excluding hosted publication; no new model-facing tool name or route is authored. - Keep: Reserved identity fields and SDK query read/projection semantics are explained with the existing runnable example. Type: Pitfall. Placement: On-demand web-app-sdk common data reference; generated public SDK schema remains authoritative. Actors: Native app author that loads the SDK Skill. Purpose: Host validation cannot select the intended query, so one operand/reference owner explains the accepted data semantics without permission expansion or a delivery gate.