TRU Studio · partner pilot · 0.3.6

Your records. Your edge. Start here.

Install the existing Studio app, connect to your organisation’s assigned edge, and follow one record from your computer to its confirmation. Python is included. An AI subscription or model API key is not required.

Installation and first-test guide

Same application for every partner. Separate identity and access for each organisation.
The public installer contains no partner credentials. Your Cotrugli contact supplies the assigned provider/edge configuration, approved network route and private connection files. Until configured, Studio works locally and shows Not connected on its Rail evidence page.

Loading available downloads…

One first test, six clear steps

Choose the package for your computer. On a Mac, check the chip under Apple menu → About This Mac. Verify its SHA-256 and install.
Open Studio. Check version 0.3.6 and the source commit in the footer. Skip optional AI setup.
Follow the guide to add your organisation’s connection files. Reopen Studio and check Rail evidence: the expected provider and “edge reachable”.
Ask Learn Guide learn: agents once, using the deterministic mode. Open Rail evidence and refresh to find the matching edge record.
Allow normal closure on the DLT, which can take up to about an hour in this pilot. Refresh the same record rather than creating another action.
Reopen Studio and confirm the same record remains. Send the version, provider, record references and displayed status to your agreed technical contact.

What the result means

ON_EDGE means the edge book contains the matching record. CONFIRMED means the edge reported FINAL and returned its N8CF1 confirmation. Studio reads that confirmation; independent signature verification is performed separately by the existing dossier verifier with pinned rail keys.

The question, answer and original envelope remain in your local evidence archive. The intake receives audit metadata and a 32-byte action commitment; the binary rail receives the edge’s period commitment. A hash cannot recover a lost original, so retain your local data and backups.

Build and installation checks

See the release manifest for the recorded checks for these exact downloads.

Unsigned pilot release. macOS has an ad-hoc signature but no Apple notarization; Windows has no publisher signature. Your organisation may need to approve the app. Follow your normal per-application approval process. Full interactive use and each partner’s environment still need the first joint test.

Existing local data is preserved on upgrade; close Studio and back up its data folder first. The older Live hackathon handshake is a separate workflow and does not configure this native evidence connector. Hospital applications and service events use their existing agreed edge/Co-Tru interface; Studio does not automatically capture them.

Downloads are hosted on our domain. No GitHub login is required. Release details and full SHA-256 checksums · Troubleshooting.