forked from sagnik/Project_Velocity
#24 WebOS Completion Co-authored-by: Sayan Datta <sayan@Sayans-MacBook-Air.local> Reviewed-on: sagnik/Project_Velocity#25
1.9 KiB
1.9 KiB
Oracle Schema and Root API Spec_ Multi-Surface Platform
Date: 2026-04-16
Status: Schema extension direction
Owner: Sayan
Reviewers: backend and schema reviewers
Purpose: Define how the current Oracle and root API shape should be extended for this workstream.
1. Current Truth
Existing Oracle schema already includes:
- canvas pages
- revisions
- components
- prompt executions
- component templates
- forks
- merge requests
- lineage
- audit
Reference:
Project_Velocity/backend/oracle/schema_oracle.sql
2. Required Extensions
Recommended additions:
oracle_template_chaptersoracle_template_subchaptersoracle_template_seed_examplesoracle_synthetic_generation_jobsinventory_propertiesinventory_import_batchesinventory_media_assetsedge_communication_eventsedge_communication_memory_factsedge_transcription_jobsedge_transcript_segmentsuser_calendar_eventsinsight_recommendationsadmin_action_events
3. Root API Additions
Recommended route families:
GET /oracle/template-chaptersGET /oracle/template-subchaptersGET /oracle/component-templatesPOST /oracle/component-templates/seedPOST /oracle/component-templates/synthetic-jobsPOST /inventory/import-batchesPATCH /inventory/properties/{propertyId}GET /mobile-edge/eventsGET /mobile-edge/memoryPOST /mobile-edge/importsPOST /mobile-edge/notesGET /mobile-edge/calendarPOST /mobile-edge/calendarPATCH /mobile-edge/calendar/{calendarEventId}GET /mobile-edge/transcripts/{eventId}GET /mobile-edge/insights/{leadId}GET /admin-surface/healthPOST /admin-surface/actions
4. Schema Rules
- do not replace current Oracle tables
- extend cleanly
- keep lifecycle and audit fields
- keep provider provenance for communication records
- keep role and tenancy fields where current Oracle patterns already use them