MEMBER GUIDE / 17 OCTOBER 2026
One organisation.
One record.
One checked proof.
Start with the existing Studio package. Your first session checks your own connection and evidence path; it does not require a customer or an AI subscription.
Connection is coordinated individually. Installing Studio does not automatically enrol your organisation, grant a mandate or provide a shared public edge.
1. Prepare your first session
Give your existing Cotrugli contact your organisation name, technical contact, operating system and CPU architecture, approved network route, and one process you want to record. Start with a synthetic contribution, without patient or customer data.
We coordinate an assigned organisation/provider identity, an authorised edge endpoint and private connection settings. Keep credentials and private network details out of public issues.
2. Install the current package
The current release checked for this proposal is Studio 0.3.6: Windows x64, macOS Apple Silicon or Intel, and Linux x64. Use the download page and its manifest as the release authority. Verify the published SHA-256 and follow your organisation’s approval process for unsigned software; do not disable system protection globally.
Skip AI setup for this evidence test. An OpenAI or other AI key is not required.
3. Apply your private connection
Close Studio. Follow the maintained installation and Rail evidence guide. Your operator supplies rail-edge.json, the authentication file and any required CA separately. Use the assigned endpoint and identity; do not copy another member’s credentials.
- Windows:
%APPDATA%\tech.cotrugli.tru-studio - macOS:
~/Library/Application Support/tech.cotrugli.tru-studio - Linux:
~/.local/share/tech.cotrugli.tru-studioor the configured XDG data home.
Preserve existing configuration, books and wallet files. Authentication and CA paths must point to the supplied local files. Reopen Studio and check the expected provider and endpoint in Rail evidence.
4. Record one synthetic action
Use the maintained guide’s Learn example, such as learn: agents. Keep the local original and its identifier. In Rail evidence, Refresh may send eligible unsent actions; it is not a purely read-only command. If an earlier submission is uncertain, follow the hold/recovery procedure instead of recreating the action.
5. Wait for the normal confirmation
Final DLT confirmation can take up to about an hour in the current process. Record the local/book time separately from later finality. Do not resend an action merely because its final proof is pending.
| Status | What it tells you |
|---|---|
| RECORDED | The action is recorded locally. |
| SENT | The submission reached the intake stage. |
| ON_EDGE | A matching edge book record is found. |
| CONFIRMED | The edge reports FINAL and Studio reads the N8CF1 structure. This alone is not independent cryptographic verification. |
| VERIFIED_STRICT | A separate operator verification result using independently pinned trust. Do not infer this from the Studio label. |
6. Complete the first check together
- Identify the organisation, actor and original for one action.
- Match the original commitment to the same book entry.
- Fetch and independently verify the returned proof.
- Reopen Studio and read the same record without submitting it again.
- Record the tested release, time and result, including any pending step.
Keep originals and local evidence files backed up under your organisation’s policy. A rail commitment does not preserve the original for you.
After the connection works
Choose one contribution, its authorised acceptance and its period. Rehearse a common account with Result, Villanova AI and other willing members. Adopt the accounting basis together before treating an illustrative allocation as an obligation. Existing server-edge or Co-Tru users should use their established route with the operator rather than create a second sender.
If something fails
Record the Studio version, OS, time, non-secret status and error. Check the approved DNS/network route, TLS trust and assigned identity with your operator. Keep uncertain submissions on hold. Never post keys, authentication files, patient material or private originals in the repository. Use the maintained guide for recovery.