Skip to content

Business Current State

Documentation Platform

  • business docs source tree exists at /root/business-docs
  • published guest name: cbr-sh-docs01
  • guest tag: business
  • guest IP: 10.0.0.52
  • business hub is published at business.souza.au
  • public segment pattern is segment.business.souza.au
  • docs pattern is docs.segment.business.souza.au
  • docs hub is also available at docs.business.souza.au
  • container has been created and provisioned with nginx and MkDocs
  • reverse proxy publishing is using the existing cbr-sf-proxy01
  • business docs hosts are restricted at nginx to 10.0.0.0/16 and loopback

Current Business Segments

  • Souza Hub
  • TV Mount Australia
  • Tentacles
  • Owl Vision
  • telephony placeholder

AI Platform Planning State

  • private handoff copied to /root/.codex/memories/ai-souza-handoff-2026-04-07.md
  • sanitized business planning docs created from that handoff
  • user email replies have now fixed the v1 direction materially
  • current planning direction favors:
  • Dify
  • n8n
  • Langfuse
  • PostgreSQL
  • Qdrant or equivalent retrieval layer
  • current planning bias is prototype-first, multi-tenant-aware, and business-scoped
  • first pilot tenant is TV Mount Australia
  • current shared WhatsApp entrypoint is 0480 804 100
  • WhatsApp and email are both in v1
  • operator fallback is an internal review queue with holding response plus human notification
  • infrastructure preference is separated LXC services on Proxmox

Tentacles Core Infrastructure

Created shared-core Tentacles service containers:

  • cbr-sh-postgres01 on 10.0.0.53
  • cbr-sh-qdrant01 on 10.0.0.54
  • cbr-sh-n8n01 on 10.0.0.55
  • cbr-sh-dify01 on 10.0.0.56
  • cbr-sh-langfuse01 on 10.0.0.57

These are business-tagged shared-core service containers, not one full stack per tenant.

Build script:

  • /root/docs/builds/build-cbr-sh-tentacles-core.sh
  • provisioning scripts:
  • /root/docs/builds/provision-cbr-sh-postgres01.sh
  • /root/docs/builds/provision-cbr-sh-qdrant01.sh
  • /root/docs/builds/provision-cbr-sh-n8n01.sh
  • explicit Tentacles reference docs now exist for:
  • requirements
  • software stack
  • infrastructure
  • v1 workflow

Tentacles Live Software State

Core services now running:

  • cbr-sh-postgres01:
  • Dockerized PostgreSQL
  • reachable on 10.0.0.53:5432
  • cbr-sh-qdrant01:
  • Dockerized Qdrant
  • reachable on 10.0.0.54:6333
  • cbr-sh-n8n01:
  • Dockerized n8n
  • reachable on 10.0.0.55:5678
  • health endpoint returns {"status":"ok"}
  • production webhook path for Tentacles intake: POST /webhook/tentacles/waha-inbound
  • local queue API now running on 10.0.0.55:8081
  • cbr-sh-waha01:
  • Dockerized WAHA as the temporary QR-based WhatsApp adapter
  • reachable on 10.0.0.58:3000
  • intended to be replaced later by WhatsApp Cloud API
  • paired and authenticated against the current shared WhatsApp entrypoint
  • live session now posts message and session.status events to cbr-sh-n8n01

Tentacles Stage 2 Prototype State

Working now:

  • WAHA is paired and in WORKING state
  • n8n accepts production webhook traffic on:
  • http://10.0.0.55:5678/webhook/tentacles/waha-inbound
  • operator review items are being queued through the local queue API on:
  • http://10.0.0.55:8081
  • synthetic inbound WhatsApp webhook tests succeeded end to end:
  • webhook accepted
  • review item queued
  • holding reply call accepted by WAHA

Current implementation note:

  • the first review queue is currently persisted by the local queue API on cbr-sh-n8n01
  • PostgreSQL remains live on the shared core, but the Stage 2 intake path has not yet been moved onto it

Tentacles Dashboards And Endpoints

  • n8n web UI:
  • http://10.0.0.55:5678
  • WAHA Swagger/API UI:
  • http://10.0.0.58:3000
  • local queue API:
  • http://10.0.0.55:8081/health
  • http://10.0.0.55:8081/queue
  • Qdrant API:
  • http://10.0.0.54:6333
  • PostgreSQL service:
  • 10.0.0.53:5432

No current UI yet for:

  • Dify
  • Langfuse

Still deferred at software level:

  • cbr-sh-dify01
  • cbr-sh-langfuse01

These containers exist, but software has not been deployed into them yet because the first useful workflow is being prioritized.

Separation Rule

  • family-only Proxmox guests are out of scope for business integration
  • only guests tagged business should be treated as valid business infrastructure