Platform Architecture
The Platform
Governed runtime · MCP tools · Skills · Channels · Operations Hub
ForgePort is not a chatbot or a single-purpose automation. It is a five-layer platform: channels capture signals, agents propose actions, the governed runtime gates every write, MCP tools connect to any system, and the Operations Hub gives administrators a way to observe and steer.
How it works
How a typical action flows
Signal arrives
An invoice from a regular supplier lands in thomas@trustfort.net. The inbox channel picks it up within 60 seconds.
Agent proposes
fp:elina-inbox classifies the email, matches the supplier against CRM records, extracts payment details, and proposes a SEPA payment of 4,280.00 EUR to the Commerzbank account on file.
Risk tier assigned
The pending action is classified as high risk — all SEPA payments are high by default, regardless of amount. The action appears in the Operations Hub pending queue.
Human approves
You see the proposal in Teams or the Operations Hub. Full context is visible: the source email, the matched supplier, the proposed amount, the BC cost centre, and the decision trace explaining why the agent proposed what it did. You approve with one click.
Execution and audit
ForgePort submits the SEPA payment to Commerzbank via the Banking tool group, writes a G/L entry to Business Central, and records the full sequence — proposal, approval, execution — in the audit log. The entire trail is exportable as Markdown or CSV for any 30-day window.
Integrations
What it integrates with
Enterprise systems
- Microsoft Dynamics 365 Business Central
- Commerzbank (AIS + PIS via SEPA Pain/Camt XML)
- Microsoft 365 / Graph API (email, Teams, calendar)
- Atlassian (Jira, Confluence, Tempo)
- LinkedIn API
- Microsoft Advertising
- Any REST / OData / SOAP API — 1–3 days per new integration
Channels
- Inbox (email)
- Microsoft Teams
- WhatsApp Business (Phase 1: outbound-only)
- Operations Hub (web)
- Newsletter
- Booking and contact form webhooks
MCP tools across 18 tool groups
specialist agents coordinated by one orchestrator
knowledge chunks with hybrid search + semantic reranking
of write operations pass through the human approval gate