Bridge

Bridge is an open-source local connector for AXAL and Tally workflows. The repository contains a Tauri desktop application and the MCPB packaging path for Claude Desktop, with React/TypeScript and Rust components for Tally, digital-signature certificate (DSC), document, sync, and local database operations.

The repository is self-contained: build and development commands resolve files relative to the clone, not to a developer-specific directory.

First useful result

As of 8 September 2026, no installer is published: the public v0.1.0 release has no downloadable assets. Check GitHub Releases for future packages. For source use, the contributor quick start below builds the desktop app; to run the MCP server, follow the source MCP setup. When a release asset is published, use the installation guide for its package-specific steps.

Before requesting financial data through an MCP client, the client may send the selected Tally result to its AI provider, including company identity, party or open-bill details, and amounts. Source installations default to BRIDGE_AGENT_REDACTION=none; set it to mask_parties or drop_narration before launch when that better fits the workflow. These settings mask party names or drop narration; they do not remove amounts. The package installation settings expose the same choices.

For a first result, run tally_status to check that TallyPrime and its Licensed or Education mode are observed, then list the loaded companies. Select a company with exactly one observed INR currency master and request receivables or payables. In Education mode, explicitly supply an as_of date on day 1, 2, or 31; an omitted date defaults to today and may be refused. Bridge rechecks product, mode, dates and currency for the financial read; other or unobserved products/modes, no currency master, non-INR, or multiple currency masters are refused.

The desktop also offers local XML draft preparation through Prepare file. It preserves source observations beside editable proposals and saves a local draft for later review.

For contributors, use the setup and development path below.

Supported development hosts

Bridge is intended to build and run on Windows and macOS 12.4 or later. Run platform checks on a native host for each operating system; a successful build on one operating system does not verify the other.

Shared prerequisites:

• Node.js 22 or 24 and Corepack (.node-version pins the CI baseline)
• the Rust toolchain pinned by rust-toolchain.toml
• Perl 5 with Locale::Maketext::Simple for the bundled SQLCipher/OpenSSL build
• LLVM/libclang for SQLCipher binding generation (LIBCLANG_PATH may be required)
• the operating-system dependencies listed in the Tauri prerequisites

On Windows, install the Microsoft C++ build tools, WebView2 components, and a complete Perl distribution such as Strawberry Perl. If another incomplete perl.exe appears first on PATH, set OPENSSL_SRC_PERL to the complete Perl executable. Install LLVM as well; if libclang.dll is not discoverable, set LIBCLANG_PATH to its directory (commonly C:\Program Files\LLVM\bin). On macOS, install Xcode Command Line Tools. DSC workflows also require a vendor PKCS#11 library compatible with the host operating system; never commit a private key, PIN, certificate dump, or locally installed vendor library. Bridge's macOS bundles require macOS 12.4 or later.

Contributor quick start

Run these commands from the repository root in PowerShell, Command Prompt, or a POSIX-compatible shell:

corepack pnpm install --frozen-lockfile
corepack pnpm exec playwright install chromium webkit
corepack pnpm test
corepack pnpm run build
corepack pnpm run cargo:check
corepack pnpm run tauri:dev

pnpm test includes Chromium and WebKit evidence-drawer focus suites; installing the lock-pinned browsers after dependencies is therefore required once for each developer environment. tauri:dev starts the Vite development server and desktop application. It does not require a fixed checkout location. The first Rust build can take several minutes.

For a release build, run corepack pnpm run tauri:build on each target host. CI-produced bundles are unsigned smoke artifacts only. Do not redistribute a desktop installer until the signing, notarization, provenance, and rollback gates in the release runbook are complete.

Platform verification

Before claiming support for a platform, run the following on that platform:

corepack pnpm install --frozen-lockfile
corepack pnpm run build
corepack pnpm run cargo:check
corepack pnpm run tauri:build

Also manually exercise the affected Tally, DSC, document, and sync workflows. Vendor integrations may require host-specific software even though repository paths and project commands are portable.

Integration trust boundaries

Bridge restricts native network and file access even if the renderer is compromised:

• Tally connections are loopback-only (localhost, 127.0.0.0/8, or ::1). Remote plaintext Tally hosts are intentionally rejected.
• AXAL credentials are sent only to the exact https://complyeaze.com origin by default. Self-hosted deployments must set BRIDGE_AXAL_ALLOWED_ORIGINS before Bridge starts to a comma-separated list of exact HTTPS origins such as https://bridge.example. Entries cannot contain paths, credentials, queries, or fragments.
• Documents must be selected with Bridge's native file or folder picker. Scan IDs are short-lived and native-only paths are never returned to the webview. Presigned uploads are limited to https://complyeaze.com by default; set BRIDGE_DOCUMENT_UPLOAD_ALLOWED_ORIGINS to the exact comma-separated HTTPS storage origins used by your AXAL deployment.
• A custom PKCS#11 module can be selected by the administrator-controlled BRIDGE_DSC_PKCS11_LIBRARY environment variable before launch. Do not point it at an untrusted library.

These environment variables are process configuration, not checkout paths; the same policy applies on Windows and macOS. Restart Bridge after changing them.

Privacy and safe diagnostics

Do not commit or attach real customer, company, tax, certificate, credential, financial, or document data. Before sharing logs, screenshots, fixtures, or reproduction steps, replace personal and customer data with synthetic values and remove local usernames and absolute paths. See SECURITY.md for private reporting and handling requirements.

Repository map

• src/ - React UI and API bindings
• src-tauri/ - Rust core and Tauri configuration
• docs/ - architecture, roadmap, and operational guidance
• .github/ - issue and pull-request templates plus CI configuration

Governance

• Agent responsibilities
• Contributor guide
• Review checklist
• Security policy
• Rectification guidelines
• Roadmap
• Managed Git guidance
• Source and asset provenance
• Release process

License

Bridge is licensed under the Apache License, Version 2.0. Attribution notices are provided in NOTICE. The historical v0.1.0 release remains under the MIT license shipped with that tag; current development source is version 0.2.0 under Apache-2.0.