sayan
eeb684b46c
#38 Ipad app production readiness, Colony orchestration, Social posting Co-authored-by: Sayan Datta <sayan@Sayans-MacBook-Air.local> Reviewed-on: #44
86 lines
1.9 KiB
Markdown
86 lines
1.9 KiB
Markdown
# Adapter Detailed Implementation Spec_ Mobile Edge Inventory Admin
|
|
|
|
**Date:** 2026-04-16
|
|
**Status:** Implementation-focused adapter spec
|
|
**Owner:** Sayan
|
|
**Purpose:** Define the first adapter surfaces that need careful treatment.
|
|
|
|
## 1. Mobile Edge Adapter
|
|
|
|
The phone edge apps should adapt backend communication state into mobile-safe views.
|
|
|
|
They should expose:
|
|
|
|
- alerts
|
|
- lead summary
|
|
- note entry
|
|
- transcription status
|
|
- communication memory reminders
|
|
- personal calendar entries and follow-up suggestions
|
|
- business WhatsApp conversation and call surface where supported
|
|
- quick actions
|
|
|
|
They should not assume:
|
|
|
|
- unrestricted audio interception
|
|
- hidden OS access to every message channel
|
|
- unsupported WhatsApp or telephony capture flows
|
|
|
|
They should support three capture modes:
|
|
|
|
- direct supported API ingestion
|
|
- provider-routed server-side ingestion
|
|
- operator-assisted import or note confirmation
|
|
|
|
They should also surface post-capture intelligence:
|
|
|
|
- diarized transcript review
|
|
- reminder suggestions
|
|
- calendar creation or edit suggestions
|
|
- CRM and QD-score recommendation review
|
|
|
|
## 2. Inventory Adapter
|
|
|
|
The inventory adapter should normalize incoming property material into:
|
|
|
|
- canonical property rows
|
|
- media references
|
|
- amenity sets
|
|
- pricing and unit data
|
|
|
|
It must support:
|
|
|
|
- create
|
|
- update
|
|
- validation errors
|
|
- ingest batch status
|
|
|
|
## 3. Oracle Template Adapter
|
|
|
|
The Oracle template adapter should convert:
|
|
|
|
- chapter and subchapter metadata
|
|
- template JSON
|
|
- seed examples
|
|
|
|
into:
|
|
|
|
- catalog query outputs
|
|
- synthesis seeds
|
|
- reviewable template records
|
|
|
|
## 4. Admin Surface Adapter
|
|
|
|
The admin surface should adapt backend system health and operational actions into:
|
|
|
|
- health cards
|
|
- deployment and install state
|
|
- queue visibility
|
|
- debug event timelines
|
|
|
|
## 5. Integration Rules
|
|
|
|
- adapters translate existing domain truth
|
|
- adapters do not become domain owners
|
|
- adapters remain thin where possible
|