Tentacles Requirements¶

Purpose¶

This document makes the Tentacles v1 requirements explicit so the project can be executed without relying on the private handoff email.

Product Definition¶

Tentacles is the AI systems segment of Souza Hub.

V1 is not a generic AI platform launch. It is a practical internal pilot built to prove one useful business workflow first and then expand in stages.

First Pilot¶

The first pilot is fixed as:

tenant: TV Mount Australia
workflow class: customer service and booking-adjacent handling
primary channels: WhatsApp and email

Current Entry Points¶

Known current v1-facing entrypoint:

shared WhatsApp number: 0480 804 100

Current business publishing:

public business segment page: tentacles.business.souza.au
business docs endpoint: docs.tentacles.business.souza.au

Provisional external domains mentioned in the handoff:

tentacles.com.au
tentatcles.systems

Treat those external domains as optional or provisional project domains until a final public-domain decision is made.

Mandatory V1 Outcomes¶

V1 must be able to:

receive inbound WhatsApp messages
receive inbound email messages
classify and route customer requests
use approved business knowledge for responses
send a holding response when confidence or approval is insufficient
create an internal review queue
notify a human operator when the queue is no longer empty
support human review before sensitive or uncertain replies are sent
support booking-related handling for the TV Mount Australia pilot

Human-In-The-Loop Rule¶

The operator workflow is mandatory.

If the system is not confident or if the action should not be automated yet, it must:

create or update the internal review queue
send a holding response to the customer
notify a human by email or WhatsApp

The operator loop is more important than advanced observability or full product breadth in the first release.

Tenant Model¶

The project owner wants:

2 to 3 internal pilot tenants on a shared core platform

Current intended tenants:

TV Mount Australia
Tentacles
Souza Hub

Telephony remains adjacent and may be folded into this later if needed, but it should not complicate the first pilot.

Channel Rules¶

V1 channels:

WhatsApp
email

Deferred channels:

web chat
voice
broader telephony integration

Data And Knowledge Rules¶

Each active tenant should have:

a bounded knowledge base
clear prompt or instruction ownership
a documented escalation path

Shared platform logic should remain separate from tenant-specific knowledge.

Infrastructure Rules¶

Infrastructure preference from the project owner:

use full machine separation for the shared core stack
prefer LXC over VM
do not duplicate the full stack per tenant

Delivery Rules¶

prototype first
prove one workflow before broadening scope
preserve multi-tenant awareness without overbuilding
keep the stack swappable where practical
prefer hosted model APIs first

Documentation Rule¶

The Tentacles execution baseline should now be readable from:

Current Open Decisions¶

These are still implementation decisions, not requirement gaps:

whether Dify is in the first deployment or deferred until the review loop is stable
whether Langfuse is in the first deployment or deferred
the exact operator notification mechanism for the first release
the exact deployment target host or cluster slice for the first business-scoped pilot stack