# Technical Architecture

#### 1.1 Conceptual Diagram

Agent → Tools → Physics → PoSml

* **Agent**: goals, policies, and execution plans (task graphs).
* **Tools**: functional modules (planner, scenario builder, evaluator).
* **Physics**: engines and environment configurations (contacts, friction, sensor pipelines).
* **PoSml**: execution-proof mechanisms and artifact integrity.

#### 1.2 Asset Layer & Storage

* **Content-Addressed Storage (CAS)** for large artifacts (meshes, textures, scenarios).
* **On-Chain Pointers** for metadata, versions, licenses, and hashes.
* **Access Control** with granular licensing (commercial/non-commercial, duration, territory).

#### 1.3 Job Orchestration & Execution

* **Spec → Bundle**: job definitions include robots, sensors, scenes, scenarios, and seeds.
* **Scheduling**: node selection by capability and reputation.
* **Execution Sandbox**: pinned-version environments for maximum determinism.
* **Artifacts**: logs, trajectories, sensor dumps, videos, and metrics exported to CAS.

#### 1.4 Proof-of-Simulation (PoSml)

* **Trace Commitments**: per-step hash chains over state, inputs, and outputs.
* **Deterministic Windows**: deterministic segments for spot-checks.
* **Redundant Runs**: selective re-execution on independent nodes for result consensus.
* **Attestation**: node signatures and timestamps; optional TEEs/zk-proofs (roadmap).

#### 1.5 Licensing & Monetization

* **Automatic royalty splits** for asset owners and contributors.
* **Metered compute pricing** by job/time/VRAM.
* **Result licensing** for internal research, commercial use, or redistribution.


---

# Agent Instructions: 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:

```
GET https://deeptics.gitbook.io/deeptics-whitepaper/core-design/technical-architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.