Projects & Collaboration

Organize and share selected Workflow records and preserved source versions while keeping original scientific ownership and provider credentials separate.

Project model

Projects live inside Workflow. They are a grouping and access layer over selected scientific records; adding a record to a project does not change its original author or duplicate the underlying experiment.

A project begins with a Main branch.
Exact inclusions determine which circuits, transpilations, jobs, compiler records, and source files are visible in a branch.
Personal originals remain separate from the shared project view.
Deleting a project removes the shared project container/access while preserving personal scientific records.

Roles and invitations

Role	Current behavior
Owner	Manages project settings, membership, invitations, and project deletion.
Contributor	Can inspect shared work and publish future work to their own writable branch. A default fork is created when the invitation is accepted.
Viewer	Can inspect, compare, and download permitted shared artifacts and create personal working copies, but does not receive a contributor fork.

Invitations can target an existing verified Spinorio account by email or exact username. Invitations are delivered in the recipient’s Workflow dashboard; this source release does not include email-delivery integration.

Branches and checkpoints

A contributor works on their own branch rather than overwriting Main.
New branches can start from the current included records or a recorded checkpoint.
The branch baseline is fixed at creation; later changes to Main are not silently merged into the fork.
Existing jobs retain their original researcher/author.
Experiment merging, source merging, and simultaneous editing are not implemented.

Notebook and source sharing

A notebook can be associated with a writable project branch so future executions publish to that branch. Spinorio captures preserved source snapshots separately from scientific execution records.

Including a notebook shares all code and Markdown cells after explicit consent.
Saved outputs are excluded by default.
Supporting files require explicit inclusion.
Opening an included notebook from a contributor branch creates or reopens an independent working copy; it does not automatically execute code.
Provider connections, live kernel state, and credentials are never transferred with a project copy.

Review source before sharing

Source text can itself contain secrets. Remove API keys, credentials, and unrelated private content before including a notebook or file in a project.

← Jobs & results

Compiler overview →