<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: pawel jankes</title>
    <description>The latest articles on DEV Community by pawel jankes (@jankes72).</description>
    <link>https://dev.to/jankes72</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4134261%2F9a25ba8c-662f-4c44-b830-242231326db0.png</url>
      <title>DEV Community: pawel jankes</title>
      <link>https://dev.to/jankes72</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jankes72"/>
    <language>en</language>
    <item>
      <title>Building an evidence-first multi-agent system: 720 paired missions, rollback, and strict claim boundaries</title>
      <dc:creator>pawel jankes</dc:creator>
      <pubDate>Sun, 20 Sep 2026 15:21:54 +0000</pubDate>
      <link>https://dev.to/jankes72/building-an-evidence-first-multi-agent-system-720-paired-missions-rollback-and-strict-claim-3n5h</link>
      <guid>https://dev.to/jankes72/building-an-evidence-first-multi-agent-system-720-paired-missions-rollback-and-strict-claim-3n5h</guid>
      <description>&lt;p&gt;I am an independent R&amp;amp;D developer building &lt;strong&gt;SSI V5&lt;/strong&gt;, an experimental multi-agent architecture focused on evidence, provenance, consolidation, and rollback.&lt;/p&gt;

&lt;p&gt;The implementation itself is proprietary. The public GitHub repository is an &lt;strong&gt;evidence and review mirror&lt;/strong&gt;: it contains sanitized reports, run summaries, test artifacts, and reviewer guidance rather than the private source code.&lt;/p&gt;

&lt;p&gt;Repository: &lt;a href="https://github.com/jankes72/SSI_V5" rel="noopener noreferrer"&gt;https://github.com/jankes72/SSI_V5&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I built it
&lt;/h2&gt;

&lt;p&gt;A multi-agent system can produce impressive-looking output while still making it difficult to answer basic engineering questions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Which component made a decision?&lt;/li&gt;
&lt;li&gt;What evidence supported it?&lt;/li&gt;
&lt;li&gt;Did a transferred skill actually improve the result?&lt;/li&gt;
&lt;li&gt;Can the system return to a known-good state?&lt;/li&gt;
&lt;li&gt;Are reported timings physical response times or only software-flow measurements?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;SSI V5 is my attempt to make those questions part of the architecture instead of adding them after the experiment.&lt;/p&gt;

&lt;h2&gt;
  
  
  Architecture in brief
&lt;/h2&gt;

&lt;p&gt;The project separates two main cores:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;BODY_FROZEN&lt;/strong&gt; — an execution-oriented core with its own runtime, memory, and lifecycle.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DIRECTOR&lt;/strong&gt; — a separate orchestration and resource-management core, also with its own runtime, memory, and lifecycle.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;They are not copies of each other. Validated knowledge can move through cross-consolidation, but their identities and responsibilities remain separate.&lt;/p&gt;

&lt;p&gt;The laboratory also uses six experimental agents called &lt;strong&gt;ISKRA1–6&lt;/strong&gt;. The system records consultations, consolidation decisions, provenance, and rollback events. Candidate capabilities are evaluated through a Champion/Challenger process before promotion.&lt;/p&gt;

&lt;h2&gt;
  
  
  Current public evidence
&lt;/h2&gt;

&lt;p&gt;The public evidence mirror currently records:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;S1–S10 training sequence: &lt;strong&gt;COMPLETE / PASS&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Seven BODY runtimes discovered: &lt;strong&gt;7/7 PASS&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Promoted BODY_FROZEN reload verification: &lt;strong&gt;144/144&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Post-S10 drone scenarios: &lt;strong&gt;6/6&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Post-S10 humanoid scenarios: &lt;strong&gt;15/15&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Drone Mother paired families: &lt;strong&gt;12/12&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Rescue Robot Mother paired families: &lt;strong&gt;12/12&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The dual-mother cross-domain laboratory executed:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;60 deterministic repetitions per paired family&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;720 paired missions&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;1,440 domain result rows&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;720 cross-consultations&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;360 consolidations&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;360 rollbacks&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Reported mean software-flow timings were:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;consultation: &lt;strong&gt;2.4896 ms&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;consolidation: &lt;strong&gt;0.0369 ms&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;rollback: &lt;strong&gt;0.1170 ms&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;total software flow: &lt;strong&gt;5.2559 ms&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These measurements describe the software laboratory only. They are &lt;strong&gt;not physical robot or drone response times&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I am not claiming
&lt;/h2&gt;

&lt;p&gt;Clear boundaries matter more than impressive wording. This project does &lt;strong&gt;not&lt;/strong&gt; currently claim:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;physical-world validation,&lt;/li&gt;
&lt;li&gt;safety certification,&lt;/li&gt;
&lt;li&gt;production readiness,&lt;/li&gt;
&lt;li&gt;independent replication,&lt;/li&gt;
&lt;li&gt;universal superiority over other architectures,&lt;/li&gt;
&lt;li&gt;AGI, consciousness, or sentience.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The repository is intended to make the evidence reviewable without exposing the proprietary implementation.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I want to test next
&lt;/h2&gt;

&lt;p&gt;I am looking for universities, robotics teams, AI researchers, and R&amp;amp;D companies willing to define an external validation problem.&lt;/p&gt;

&lt;p&gt;A useful pilot would work like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The partner supplies a previously unseen problem or scenario.&lt;/li&gt;
&lt;li&gt;We freeze the acceptance criteria in advance: PASS, FAIL, or INCONCLUSIVE.&lt;/li&gt;
&lt;li&gt;SSI V5 runs the experiment with evidence and provenance enabled.&lt;/li&gt;
&lt;li&gt;Failures remain visible instead of being removed from the report.&lt;/li&gt;
&lt;li&gt;The partner receives the results, limitations, timings, and rollback/consolidation history.&lt;/li&gt;
&lt;li&gt;Nothing is published without the partner's approval.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The strongest next step is not another internal claim. It is an externally defined test with frozen criteria.&lt;/p&gt;

&lt;p&gt;If you work in multi-agent systems, robotics, autonomous systems, AI assurance, or research validation, I would value a technical review of the evidence mirror or a proposal for a hard external test.&lt;/p&gt;

&lt;p&gt;I am especially interested in:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;paid R&amp;amp;D pilots and proof-of-concept projects,&lt;/li&gt;
&lt;li&gt;research partnerships,&lt;/li&gt;
&lt;li&gt;grant consortia in Poland or Europe,&lt;/li&gt;
&lt;li&gt;independent replication or red-team review.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Feedback is welcome, especially criticism of the experimental design or claim boundaries.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: AI assistance was used to edit and translate this article. The project claims and numerical results were restricted to evidence available in the public repository.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>machinelearning</category>
      <category>architecture</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
