Visenious

Visenious Super Intelligence. A vendor-agnostic business suite, orchestrated by Genius.

A multi-layered system of independent agents and software connectors. Genius, the central sovereign core of the Visenious ecosystem, interprets the request, plans the work, delegates to the right agent or connector and returns one verified result. Your ERP, CRM and tools keep their authority. First pilot: an order problem resolved end to end.

Seven capabilities. An open catalog.

Independent agents and software connectors, enabled per deployment. New ones join under the same orchestration and the same control.

  • 1.1 Support

    Answers with sources.

    Facts, suggestions and missing evidence kept apart.

  • 1.2 CRM

    Changes you can diff.

    A before and after change set, with provenance.

  • 1.3 Supply chain

    The ERP stays authoritative.

    Proposals are drafted. Orders are never placed alone.

  • 1.4 Attendance

    Grounded in trusted records.

    Corrections are proposals under your policy.

  • 1.5 Vision

    Cameras at the edge, events in the core.

    Visenious Visual SI sends events to Genius, never video.

  • 1.6 Efficiency

    Recommendations with a baseline.

    Guardrail metrics defined before any trial.

  • 1.7 Learning

    Improvement as a governed release.

    Model changes versioned, evaluated and approved.

Every action takes the same path.

  1. 01

    Intent

    What Genius proposes to do, and why.

  2. 02

    Classify

    The effect class sets the authority.

  3. 03

    Govern

    Policy, scope and rate. Pass, steer or block.

  4. 04

    Hold

    Outside policy, a reviewer decides.

  5. 05

    Execute

    Through a qualified adapter.

  6. 06

    Settle

    A receipt lands in the audit chain.

Approval is bound to the exact proposal. A material edit creates a new version.

The ERP stays the operational centre.

Genius understands the lifecycle of business documents and coordinates work across departments. The ERP enforces its native rules and keeps its records.

Business areaGenius contributesThe ERP keeps
Sales and fulfilmentPrepares quotes, investigates delays, coordinates alternatives.Prices, terms, orders, release and fulfilment state.
InventoryExplains shortages, proposes transfers, requests reservations.Availability, locations, reservations and movements.
ProcurementConsolidates demand, compares suppliers, prepares orders.Supplier rules, purchasing documents and commitments.
ProductionIdentifies material gaps, proposes schedule changes.Bills of materials, production orders and capacity.
FinanceCollects evidence, investigates mismatches, prepares actions.Posting, balances, document controls and the ledger.
Document lifecycleDraftApproveReleaseFulfilInvoice
Worked example

Two tasks. Ten units. One authoritative reservation.

A sales order and a production order compete for the same stock. Reading availability does not reserve it. The ERP allocates.

  1. 01 · Sales workflowRequests 7 units. The ERP confirms an atomic reservation for the sales order.
  2. 02 · Production workflowRequests 6 units. Only 3 remain, so the request cannot be fully reserved.
  3. 03 · ResolutionThe rejected request considers an approved transfer, replenishment or escalation while unrelated work continues.

Genius coordinates the resource that is actually shared: an order key protects its edits, a warehouse and product key identifies a stock conflict. Native ERP reservations and conditional updates do the enforcing. Illustrative quantities; allocation follows your policy.

A service issue. Two specialists. One reviewed result.

  • The reviewer sees the draft, the diff, the uncertainty and the policy.
  • A material edit creates a new proposal version.
  • Instructions found in documents or tool results cannot grant new authority.
VSI · orchestrated by Genius · ticket #2 287live
  • $ vsi task --from ticket:2287
  • > Customer says the replacement unit never shipped.
  • ⟶ genius.plan → support.interpret → crm.context (scope: account, orders)
  • ⟶ support: policy 'replacements' v3 · RMA 1182 opened 14 days ago
  • ⟶ crm: shipment field empty · carrier reference missing
  • Proposal: reply with status, set rma.carrier_ref from the warehouse export. Two effects, two receipts.
  • ⟶ govern message:send → hold (customer-facing) · record:update → pass
  • ✓ reviewed 10:04 · message approved · record v7→v8 · receipts #551, #552

A pilot is judged on work saved, not model speed.

The scorecard is agreed with you before the pilot starts. The difficult cases are proven before autonomy is widened.

  • 01

    Time saved

    Active handling time before and after, including review and correction.

  • 02

    Completion quality

    Correct, supported outcomes and the amount of rework.

  • 03

    Operational reliability

    Failures, recovery, duplicate effects and unresolved outcomes.

  • 04

    Human experience

    Review effort, clarity of evidence and operator acceptance.

  • 05

    Practical cost

    Hardware, integration, operation and ongoing support.

The difficult cases, proven before autonomy widens

Parallel independent orders
Unrelated orders progress without global blocking.
Two tasks compete for stock
Confirmed reservations never exceed availability.
An employee changes the ERP
Stale conditions trigger reassessment.
Duplicate request or timeout
No duplicate effect. Unresolved outcomes stay visible.
Restart or worker interruption
Saved results survive. Pending effects reconcile safely.
Approval delayed or revoked
Waits release capacity. Authority is rechecked.
Bulk job or connector overload
Backlogs stay bounded and access stays fair.
Camera outage or repeated event
Degraded coverage is visible. Events are deduplicated.
Company boundary
Forbidden records and actions remain inaccessible.

Release widens in stages: read only, proposals under review, approved writes with confirmed effects, then routine tasks within limits. Each stage needs the evidence of the one before it.

Built to be owned.

Your host. No tenancy, no metered tokens.

Orchestration
Genius, the central sovereign core, coordinates every layer: independent agents, software connectors and the governance gate. Several agent roles share one local model.
Agents
Python. Independent managed roles with schemas, scopes and effect classes, registered in an open catalog.
Durability
PostgreSQL. Interrupted work resumes from recorded results. Uncertain external effects are reconciled before any retry.
Connectors
Vendor-agnostic. Software connectors to any ERP, CRM, support desk or HR system, qualified per product and version. Reads first, writes after their guarantees are proven.
Workspace
My work, approvals, exceptions, evidence, activity. Every wait shows its reason.
Inference
Local models. Cloud is an explicit opt-in.
Deployment
Docker Compose on one host. Air-gapped supported.
Path
Prove the foundation, deliver Support and CRM, connect one ERP, add vision and attendance, improve with evidence, qualify the customer deployment. Progression by acceptance evidence, not by calendar.
Status
Design baseline of 8 October 2026, architecture and roadmap of 21 October. Enterprise identity, durable business execution and ERP connectors are the implementation work ahead.
Runs on
Genius.

Start with Support and CRM.

One email to pick the systems and the pilot cases.