F´ page: replicas as processes; 45 unit tests; v0.7.0

src/data/claims.json

@@ -4,7 +4,7 @@
   "sources": {
     "flight": {
       "repo": "mruspace/flight",
-      "commit": "215547b",
+      "commit": "bbdad54",
       "bench": ["2026-10-11-darwin-arm64.json", "2026-10-11-linux-aarch64.json", "2026-10-11-linux-x86_64.json"],
       "bench_commits": { "darwin-arm64": "7c1a629", "linux-aarch64": "d79b345", "linux-x86_64": "d79b345" },
       "kat": "2026-10-11-darwin-arm64-kat.json",
@@ -805,13 +805,13 @@
       "text": "5"
     },
     "flight.fprime.unit_tests": {
-      "value": 44,
+      "value": 45,
       "format": "int",
       "unit": "F´ unit tests",
       "scope": "fprime/Mru components, fprime-util check in CI",
-      "conditions": "HealthRegistry 5, ReplicaHost 5, FaultInjector 8, RedundancyManager 23, RunRecorder 3",
+      "conditions": "HealthRegistry 5, ReplicaHost 5, FaultInjector 8, RedundancyManager 23, RunRecorder 4",
       "source": { "repo": "flight", "kind": "manual", "ref": "docs/fprime-design-fpp.md" },
-      "text": "44"
+      "text": "45"
     },
     "flight.kani.core": {
       "value": 4,

src/pages/concepts/architecture.astro

@@ -105,7 +105,7 @@ const crumbs = [
             </td>
             <td class="m">Deployed, partial</td>
             <td>
-              Nine Kani proofs, the scenario checks and 44 F&#180; unit tests in CI, a known-answer test coverage
+              Nine Kani proofs, the scenario checks and 45 F&#180; unit tests in CI, a known-answer test coverage
               campaign, an F&#180; system test against the demo, the first F&#180; deployment (<code>MruOpsSat</code>)
               run full length in ESA&#39;s OPS-SAT experiment environment under emulation,{' '}
               <a href="/core/bench/">bench</a> on general-purpose processors, Dusk, and the quorum demo on the SEPP
@@ -271,7 +271,7 @@ const crumbs = [
     <ul class="sig-list">
       <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: 44 unit tests with the two
+        <code>HealthRegistry</code> and <code>ReplicaHost</code> are built and tested: 45 unit tests with the two
         test-only components, a system test against the demo&#39;s counts on the bench schedules, and a first F&#180;
         deployment. They have not run on flight hardware. The quorum demo, without F&#180;,{' '}
         <a href="/core/quorum-cli/#opssat">ran in orbit on ESA&#39;s OPS-SAT PRETTY satellite</a> on 18 Oct 2026

src/pages/concepts/qualification.astro

@@ -121,7 +121,7 @@ const crumbs = [
           <tr>
             <td>F&#180; unit tests and system test</td>
             <td>
-              44 unit tests of the F&#180; components, a 60-case system test against the demo&#39;s counts, and the
+              45 unit tests of the F&#180; components, a 60-case system test against the demo&#39;s counts, and the
               first deployment against the demo in CI. Not run on flight hardware. See{' '}
               <a href="/core/fprime/#tests">F&#180; components</a>.
             </td>
@@ -212,7 +212,7 @@ const crumbs = [
       </table>
     </div>
     <p class="tiny">
-      Status as of 22 Oct 2026, flight v0.6.0. The F&#180; components, the deployment and the C interface have numbered
+      Status as of 22 Oct 2026, flight v0.7.0. The F&#180; components, the deployment and the C interface have numbered
       requirements, each with a verification method, but no trace to mission or standard requirements.
     </p>
 

src/pages/core/fprime.astro

@@ -8,7 +8,7 @@ const crumbs = [
   { label: 'Core runtime', href: '/core/quorum-crate/' },
   { label: 'F´ components' },
 ];
-const repo = 'https://github.com/mruspace/flight/blob/v0.6.0';
+const repo = 'https://github.com/mruspace/flight/blob/v0.7.0';
 ---
 
 <DocsLayout
@@ -47,9 +47,9 @@ const repo = 'https://github.com/mruspace/flight/blob/v0.6.0';
       <span class="pill">F&#180; v4.4.1</span>
       <span class="pill">C++14</span>
       <span class="pill sig">
-        <span class="dot"></span>44 unit tests
+        <span class="dot"></span>45 unit tests
       </span>
-      <span class="pill">v0.6.0</span>
+      <span class="pill">v0.7.0</span>
     </div>
     <p>
       The source is in <a href={`${repo}/fprime`}>fprime/</a> of mruspace/flight. The requirements and the design were
@@ -229,6 +229,13 @@ const repo = 'https://github.com/mruspace/flight/blob/v0.6.0';
       from the state file after a kill, and 1.2% to 1.5% CPU in the timed run. It has not run on the SEPP. See{' '}
       <a href={`${repo}/docs/opssat.md`}>the operations note</a>.
     </p>
+    <p>
+      A second deployment puts each replica in a process of its own: <code>MruQuorum</code>, the manager process, starts
+      three <code>MruReplica</code> processes, linked through F&#180;&#39;s GenericHub over Unix socket pairs (no
+      network), and pins them to the SEPP&#39;s two cores. The kill is real: the manager sends SIGKILL to a replica
+      process at the start of a cycle. In ESA&#39;s environment under emulation it gave the same counts and events as
+      the first deployment, with the three processes pinned in every segment. It has not run on the SEPP.
+    </p>
     <p>
       On one processor the manager and the replicas share the processor. A manager that falls behind used to close
       cycles before their answers were dispatched, so healthy replicas looked silent and were retired as lost. Since
@@ -301,7 +308,7 @@ void quorum_health_clear(quorum_health *health, uint32_t replica);</pre>
           <tr>
             <td>F&#180; unit tests</td>
             <td>
-              44, by requirement: HealthRegistry 5, ReplicaHost 5, FaultInjector 8, RedundancyManager 23, RunRecorder 3.
+              44, by requirement: HealthRegistry 5, ReplicaHost 5, FaultInjector 8, RedundancyManager 23, RunRecorder 4.
               Built with address and undefined-behavior sanitizers.
             </td>
           </tr>