Clear boundaries.
Accountable automation.

Identity and client access

The linked prototype workspace uses its own sign-in and server-side client membership checks. The WordPress client portal and its connection to n8n are still being implemented. Selecting a client must never grant access by itself.

Approval before execution

Actions awaiting approval remain separate from completed work. Approval is a recorded decision; downstream execution is reported separately after a connected workflow confirms it. Enabling an agent configures availability and does not prove its external systems are connected.

Credentials and integrations

Provider secrets belong in server-side secret storage or the workflow credential store. No API keys belong in chat messages or browser code. Integrations must validate client context and permissions before taking action.

Costs with a source

Actual expenses and estimates are tracked separately. Manual entries are labelled. Multiple currencies are reported independently; no implicit conversion is applied. This operational ledger is not a replacement for your accounting records.

Current deployment

The WordPress marketing website is live. A separate prototype provides workspace configuration and an expense ledger. WordPress client access, external workflow execution, phone bots and automatic provider usage require further implementation and validation. No security certification or independent audit is claimed.