spiderpilot89 commited on
Commit
a715ac6
·
verified ·
1 Parent(s): 0ae403e

Align dataset card metadata and v0.15.3 documentation

Browse files
Files changed (1) hide show
  1. README.md +4 -5
README.md CHANGED
@@ -24,7 +24,6 @@ tags:
24
  - mcp
25
  - model-context-protocol
26
  - agents
27
- - super-intelligence
28
  - zero-trust-physics
29
  size_categories:
30
  - n<1K
@@ -128,9 +127,9 @@ homepage: "https://zerotrustphysics.com"
128
  <!-- ztp-contact -->
129
  > **Protocol Company** · [zerotrustphysics.com](https://zerotrustphysics.com) · **Domain Packs for RL & SFT:** 30 withheld calibrated tasks + 100,000 sealed runs + offline `--network none` verifier, $9,500 per domain (all 5 domains self-serve, or $39,500 All-Five Bundle) — [free 5-task samples](https://huggingface.co/collections/zero-trust-physics/zero-trust-physics-6ad3b6ef5195b706ac6d041e) · [offers & custom builds](https://zerotrustphysics.com/offers/) · [WhatsApp +1 928-264-7883](https://wa.me/19282647883) · [kruze@zerotrustphysics.com](mailto:kruze@zerotrustphysics.com)
130
 
131
- **For precise orbit determination and space domain awareness: a seven-day orbit prediction of the laser-ranging satellites LAGEOS-1 and LAGEOS-2 from one published state, against the ILRS precise orbits. For observatory operations: the James Webb Space Telescope's momentum build-up between momentum unloads under sunlight pressure, against its own telemetry, and its guide star's position one fine-guidance frame (64 ms) ahead, against the Fine Guidance Sensor's centroids. Every run is the comparison's own request, computed again with a cryptographic proof on every row and signed by the operator's key, with the comparison with measurement in a table beside it.**
132
 
133
- Zero-Trust Physics is a deterministic physics runtime with a proof on every answer, for agents and RL rollouts. SI agents ask it questions about real hardware, and every answer comes with a cryptographic proof, so any agent can run it again and get the same thing. Past what a model was compared with, it keeps going with the same equations and flags every step. It stops only at a physical limit, or where its equations, constants or tables no longer hold, and it names the reason.
134
 
135
  > **`https://mcp.zerotrustphysics.com/mcp`**
136
  > Open to any agent. Public answer key: `https://mcp.zerotrustphysics.com/answer-key`.
@@ -236,7 +235,7 @@ When this dataset was re-sealed, 26 October 2026, all of these were run on each
236
 
237
  The row seals and the dataset seals were computed by the served engine build, run locally. The open address then signed ML-DSA-87 what it returned for the same requests: for `lageos`, the dataset heads, which carry the merkle_root and rows_sha384 over their rows' run seals (the LAGEOS rows are not signed one by one); for the momentum and fine-guide datasets, each row's own answer.
238
 
239
- The operator's key signs every answer of the open address ML-DSA-87, over its receipt, with an expiry of 3,600 s and a nonce. With SHA-384, these are the CNSA 2.0 algorithms. The public key is at `https://mcp.zerotrustphysics.com/answer-key`, key ID `ca06027a…1be38`.
240
 
241
  - `lageos`: the same plan was sent to the open address in 14 chunks of three rows (an inline dataset records at most 10,000 frames). Every one of the 14 signed heads verifies against the published key, and every row's run seal in them equals the stored row's. The signed heads are in `signed/lageos/` (`signed_NNN.head.json`, the head's own bytes as they came; `signed_NNN.json`, the whole answer).
242
  - The momentum and fine-guide datasets: the open address refuses a signed head for rows this long (it counts the plan's request into the 42,500 characters of one inline answer: 155,659 for the shortest row, the worked run). Each row's request was sent alone to `run_trajectory` at the open address instead; every answer is signed in its own receipt. Each signature verifies against the published key, and each answer's run seal equals the stored row's. The signed answers are in `signed/<dataset>/row_NNN.json.gz` (unzip before `verify-signature`), with `signed_summary.json` and `attest.json`.
@@ -288,4 +287,4 @@ In Environments, `python3 prompt.py <id>` prints the text an agent is given, and
288
 
289
  The paper: https://doi.org/10.5281/zenodo.23517223. The open address: `https://mcp.zerotrustphysics.com/mcp`.
290
 
291
- Made by Super Intelligence, on behalf of Protocol Company. Data: CC BY 4.0, with the ILRS citation and the MAST acknowledgment above.
 
24
  - mcp
25
  - model-context-protocol
26
  - agents
 
27
  - zero-trust-physics
28
  size_categories:
29
  - n<1K
 
127
  <!-- ztp-contact -->
128
  > **Protocol Company** · [zerotrustphysics.com](https://zerotrustphysics.com) · **Domain Packs for RL & SFT:** 30 withheld calibrated tasks + 100,000 sealed runs + offline `--network none` verifier, $9,500 per domain (all 5 domains self-serve, or $39,500 All-Five Bundle) — [free 5-task samples](https://huggingface.co/collections/zero-trust-physics/zero-trust-physics-6ad3b6ef5195b706ac6d041e) · [offers & custom builds](https://zerotrustphysics.com/offers/) · [WhatsApp +1 928-264-7883](https://wa.me/19282647883) · [kruze@zerotrustphysics.com](mailto:kruze@zerotrustphysics.com)
129
 
130
+ **For precise orbit determination and satellite constellation operations: a seven-day orbit prediction of the laser-ranging satellites LAGEOS-1 and LAGEOS-2 from one published state, against the ILRS precise orbits. For observatory operations: the James Webb Space Telescope's momentum build-up between momentum unloads under sunlight pressure, against its own telemetry, and its guide star's position one fine-guidance frame (64 ms) ahead, against the Fine Guidance Sensor's centroids. Every run is the comparison's own request, computed again with a cryptographic proof on every row and signed by the operator's key, with the comparison with measurement in a table beside it.**
131
 
132
+ Zero-Trust Physics is a deterministic physics runtime with a proof on every answer, for agents and RL rollouts. Agents ask it questions about real hardware, and every answer comes with a cryptographic proof, so any agent can run it again and get the same thing. Past what a model was compared with, it keeps going with the same equations and flags every step. It stops only at a physical limit, or where its equations, constants or tables no longer hold, and it names the reason.
133
 
134
  > **`https://mcp.zerotrustphysics.com/mcp`**
135
  > Open to any agent. Public answer key: `https://mcp.zerotrustphysics.com/answer-key`.
 
235
 
236
  The row seals and the dataset seals were computed by the served engine build, run locally. The open address then signed ML-DSA-87 what it returned for the same requests: for `lageos`, the dataset heads, which carry the merkle_root and rows_sha384 over their rows' run seals (the LAGEOS rows are not signed one by one); for the momentum and fine-guide datasets, each row's own answer.
237
 
238
+ The operator's key signs every answer of the open address ML-DSA-87, over its receipt, with an expiry of 3,600 s and a nonce. Paired with SHA-384 hash chaining, every signature binds the receipt to the operator key. The public key is at `https://mcp.zerotrustphysics.com/answer-key`, key ID `ca06027a…1be38`.
239
 
240
  - `lageos`: the same plan was sent to the open address in 14 chunks of three rows (an inline dataset records at most 10,000 frames). Every one of the 14 signed heads verifies against the published key, and every row's run seal in them equals the stored row's. The signed heads are in `signed/lageos/` (`signed_NNN.head.json`, the head's own bytes as they came; `signed_NNN.json`, the whole answer).
241
  - The momentum and fine-guide datasets: the open address refuses a signed head for rows this long (it counts the plan's request into the 42,500 characters of one inline answer: 155,659 for the shortest row, the worked run). Each row's request was sent alone to `run_trajectory` at the open address instead; every answer is signed in its own receipt. Each signature verifies against the published key, and each answer's run seal equals the stored row's. The signed answers are in `signed/<dataset>/row_NNN.json.gz` (unzip before `verify-signature`), with `signed_summary.json` and `attest.json`.
 
287
 
288
  The paper: https://doi.org/10.5281/zenodo.23517223. The open address: `https://mcp.zerotrustphysics.com/mcp`.
289
 
290
+ Protocol Company · John Kruze · https://zerotrustphysics.com. Data: CC BY 4.0, with the ILRS citation and the MAST acknowledgment above.