> For the complete documentation index, see [llms.txt](https://solvency.gitbook.io/picoin/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solvency.gitbook.io/picoin/science-compute-layer/science-compute-l2.md).

# Science Compute L2

Science Compute is Picoin’s future decentralized computation infrastructure.

The goal is to create a distributed network capable of supporting:

* scientific workloads;
* AI inference;
* distributed GPU compute;
* mathematical computation;
* open-source AI infrastructure.

The protocol is designed to evolve from Proof of Pi mining into broader useful computation systems.

### Scientific Jobs

Picoin introduces scientific jobs as future compute coordination primitives.

Scientific jobs currently exist as L1 accounting objects.

A scientific job may contain:

* requester;
* metadata hash;
* storage pointer;
* compute limits;
* reward configuration;
* job status.

The current implementation focuses on:

* accounting;
* security;
* coordination;
* future extensibility.

Heavy compute execution is intentionally deferred to future L2 infrastructure.

### Compute Units

Picoin uses abstract Compute Units for future compute accounting.

Compute Units are designed to represent:

* relative compute workload;
* execution complexity;
* compute accounting.

The protocol separates:

* compute execution;
* compute accounting.

Current L1 versions only track accounting structures.

Future L2 systems may later determine:

* compute unit usage;
* workload pricing;
* execution metrics.

#### Future L2 Responsibilities

The future L2 is expected to execute:

* AI inference;
* distributed GPU compute;
* scientific simulations;
* compute scheduling;
* workload execution.

This separation is intended to improve:

* scalability;
* security;
* modularity.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://solvency.gitbook.io/picoin/science-compute-layer/science-compute-l2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.