feat: Oracle CRM Page, Synthetic Client Data and Live Snapshot when hitting emotion hotpoint
This commit is contained in:
26
README.md
26
README.md
@@ -170,8 +170,11 @@ http://127.0.0.1:8000/health
|
||||
### Backend capabilities already present
|
||||
|
||||
- authentication and token issuance
|
||||
- authenticated `/api/auth/me` identity resolution with `full_name` and email
|
||||
- Catalyst campaign routes
|
||||
- Sentinel websocket/session ingestion
|
||||
- canonical CRM routes for contacts, client 360, opportunities, tasks, kanban, QD, and imports
|
||||
- Oracle v1 API routes with same-origin frontend fallback
|
||||
- CCTV routes
|
||||
- scenes and videos routes
|
||||
- vault routes
|
||||
@@ -207,14 +210,19 @@ Implemented now:
|
||||
- live ingress and AWS/Linux operational model
|
||||
- Dream Weaver / Qwen / Wan workflow assets
|
||||
- browser-webcam Sentinel path using MediaPipe
|
||||
- canonical CRM schema and synthetic Kolkata client dataset
|
||||
- Oracle CRM-facing route family and Client 360 aggregation service
|
||||
- Sentinel assigned-mode integration with canonical CRM contacts
|
||||
- same-origin Oracle frontend client fallback for production deployments
|
||||
- Linux-origin auto-update scripts and nginx deployment assets under `infrastructure/desineuron_ingress/`
|
||||
|
||||
Still being closed:
|
||||
|
||||
- canonical CRM routes for `leads`, `chat_logs`, and `kanban`
|
||||
- unified CRM database contract
|
||||
- prompt inventory and persona contract map
|
||||
- full end-to-end async orchestration across all media workflows
|
||||
- stronger frontend/backend contract discipline
|
||||
- live operational proving of the import review and commit workflow
|
||||
- richer Sentinel evidence capture at emotion hotpoints
|
||||
- full production rollout validation on the Linux origin after each merge
|
||||
|
||||
## Deployment Model
|
||||
|
||||
@@ -228,6 +236,18 @@ Velocity is being shaped toward:
|
||||
|
||||
The current repo also includes the ingress and ops artifacts used to run this model today.
|
||||
|
||||
### Linux-origin update path
|
||||
|
||||
The repo includes a Linux-side auto-deploy path for `velocity.desineuron.in`:
|
||||
|
||||
- [`deploy_velocity_site.sh`](infrastructure/desineuron_ingress/deploy_velocity_site.sh)
|
||||
- [`install_linux_velocity_site.sh`](infrastructure/desineuron_ingress/install_linux_velocity_site.sh)
|
||||
- [`desineuron-velocity-site-update.service`](infrastructure/desineuron_ingress/desineuron-velocity-site-update.service)
|
||||
- [`desineuron-velocity-site-update.timer`](infrastructure/desineuron_ingress/desineuron-velocity-site-update.timer)
|
||||
- [`velocity.desineuron.in.nginx.conf`](infrastructure/desineuron_ingress/velocity.desineuron.in.nginx.conf)
|
||||
|
||||
That path is designed to pull `main` from Gitea onto the Linux origin, rebuild the frontend, and republish the static site under `/var/www/velocity.desineuron.in/current`.
|
||||
|
||||
## Internal Truth Sources
|
||||
|
||||
Key internal docs live under `.Agent Context/` and `infrastructure/`.
|
||||
|
||||
Reference in New Issue
Block a user