Program case study

ScienzaOS

Research infrastructure for open science and collaboration.

How one academic foundation — sources, review, rights, and provenance — is meant to carry research, teaching, and university–industry collaboration, at a pre-launch stage.

Pre-launch — access by request

  • Intelligent Systems
  • Knowledge Systems
A university research commons with scholarly books and shared data resources
Program artwork, not a screenshot of the software.

Research context

ScienzaOS sits at the intersection of Intelligent Systems and Knowledge Systems. It asks what academic work looks like when agents can prepare material while responsibility stays with people.

The program is pre-launch: access is by request, and the program site describes browser-local previews rather than connected institutional systems.

Approach

  1. Keep sources, claims, citations, and access context attached to the work they support.
  2. Route work through review and approval, so the person responsible decides what is issued.
  3. Carry rights and provenance forward, so reviewed knowledge can be reused rather than rebuilt.

System architecture

Diagram — the ScienzaOS foundation. Read top to bottom: three surfaces sit on one shared foundation of sources, review, rights, and reuse. The foundation is what the surfaces have in common, not a separate product.
  1. Surfaces

    Research Agent, Teaching Studio, Business Collaboration

    Three connected surfaces for papers and proposals, teaching material, and university–industry work.

    • Research Agent
    • Teaching Studio
    • Business Collaboration
  2. Shared foundation

    Sources and evidence

    Selected sources stay connected to the work they support, with their access context.

    • Evidence lineage
  3. Workflow

    Review and approval workflows

    Plans, drafts, review issues, and revisions pass an approval gate before anything is issued.

    • Approval workflows
  4. Rights

    Roles, rights, and provenance

    Authorship, versions, sharing conditions, and source context travel with the record.

  5. Reuse

    Responsible reuse

    Reviewed knowledge moves into teaching and collaboration without being rebuilt from scratch.

Current implementation

Published status
Pre-launch — access by request

The status above is the published one. Research Agent is the first offer; the program site presents Teaching Studio and Business Collaboration as browser-local previews.

What this does not claim

  • No live student, publisher, or partner-system records are connected today.
  • The program site says sign-ups open at the public launch and that nothing is saved or sent before then; this case study does not treat the surfaces as shipped.

Evidence

What the record establishes

The evidence is the program site's documented surfaces, its evidence-lineage model, and its access-by-request status.

What it does not establish

Pre-launch means there is no public usage record yet, so none is claimed here.

Roadmap

Every item below is planned, proposed, or under investigation. None of it is shipped, and this list is not a release schedule.

  1. Planned

    Public launch

    Planned: access moves from request to public launch. The program site says sign-ups open at that point.

  2. Under investigation

    Connecting the teaching and collaboration surfaces

    Under investigation: both are browser-local previews today, and connecting them to institutional systems is future work.

Collaboration

ScienzaOS grows through universities and publishers: research offices, graduate programs, and industry partners scoping joint work around evidence, roles, and rights.

Work on a program with us.

Each program takes on partners where the research question meets real practice — clinical review for AIMed, agent runtime governance for ActantOS and Agent Platform, academic workflows for ScienzaOS, and document-heavy collections for AgenticOCR.

Discuss a collaboration
  • Clinical pilots
  • Research collaborations
  • Dataset partnerships
  • Student theses
  • Open-source contributions