OPS-SAT: registered experiment, package

src/data/nav.ts

@@ -73,7 +73,7 @@ export const NAV: NavGroup[] = [
     title: 'Integrations',
     items: [
       { id: 'fprime', label: 'F´ components', href: '/core/fprime/' },
-      { id: 'opssat', label: 'OPS-SAT launcher', href: '/core/quorum-cli/#opssat' },
+      { id: 'opssat', label: 'OPS-SAT package', href: '/core/quorum-cli/#opssat' },
     ],
   },
   { title: 'Lab', items: [{ id: '2049', label: 'Mru 2049', href: '/lab/2049/' }] },

src/pages/concepts/architecture.astro

@@ -263,8 +263,9 @@ const crumbs = [
       <li>
         <strong>Mru Flight</strong> is Layer 1 for spacecraft. The F&#180; components <code>RedundancyManager</code>,{' '}
         <code>HealthRegistry</code> and <code>ReplicaHost</code> are built and tested: 37 unit tests, and a system test
-        against the demo&#39;s counts on the bench schedules. They have not run on flight hardware. A launcher for a{' '}
-        <a href="/core/quorum-cli/#opssat">proposed experiment on ESA&#39;s OPS-SAT</a> is in the repository.
+        against the demo&#39;s counts on the bench schedules. They have not run on flight hardware. The package for the{' '}
+        <a href="/core/quorum-cli/#opssat">experiment registered with ESA&#39;s OPS-SAT Space Lab</a> (OPS-SAT PRETTY,
+        exp4051) is in the repository.
       </li>
       <li>
         <strong>Mru Field</strong> is the same Layer 1 core for systems on Earth that are hard to reach. See{' '}

src/pages/core/quorum-cli.astro

@@ -242,9 +242,13 @@ limits: memory=128MB/process cpu_time=none cpu_share=none max_run=none reply_tim
 
     <h2 id="opssat">On OPS-SAT</h2>
     <p>
-      For a proposed experiment on ESA&#39;s OPS-SAT. The experiment has not been accepted. <code>opssat/run.sh</code>{' '}
-      starts, checks and stops a run with all limits set. Tagged releases ship each static Linux binary (three ARM, one
-      x86_64) with the launcher, a sample fault schedule and the operations note.
+      For the experiment registered with ESA&#39;s OPS-SAT Space Lab for OPS-SAT PRETTY (exp4051, October 2026). Nothing
+      has run on the satellite yet. <code>opssat/run</code> is the entry point the OPS-SAT runner executes: the
+      shrinking quorum and fixed TMR one after the other, same seed and fault schedule, all output in a folder for
+      downlink, finished inside a five-minute window. <code>opssat/package.sh</code> builds the package from a
+      checksum-verified release binary. <code>opssat/run.sh</code> starts, checks and stops a long run on any Linux
+      system. Tagged releases ship each static Linux binary (three ARM, one x86_64) with both launchers, the fault
+      schedules and the operations note.
     </p>
     <DocsEnd />
   </article>

src/pages/index.astro

@@ -41,8 +41,8 @@ import DocsLayout from '../layouts/DocsLayout.astro';
         <p class="k">Integrations</p>
         <h3 class="h3">F&#180; and OPS-SAT</h3>
         <p class="small soft" style="margin: 10px 0 0">
-          F&#180; components around the Rust core, a C interface for other frameworks, and the operations note for a
-          proposed OPS-SAT experiment.
+          F&#180; components around the Rust core, a C interface for other frameworks, and the operations note and
+          package for the registered OPS-SAT PRETTY experiment.
         </p>
       </a>
       <a class="card" href="/lab/2049/" style="text-decoration: none">

src/styles/shared/mru.css

@@ -557,7 +557,7 @@
   display: grid;
   grid-template-columns: 21fr 34fr;
   gap: 64px;
-  align-items: end;
+  align-items: start;
 }
 
 /* The descent line */