{"id":"4e1bf2e2-fed4-4255-9ab9-407279fd645a","arxiv_id":"2611.17186","paper_version":1,"verdict":"CONDITIONAL","confidence":"MODERATE","novelty_score":4.0,"correctness_risk":"medium","formal_verification":"none","parameter_count":0,"one_line_summary":"A prototype wires agent peer discovery, a federated training stack, on-chain staking, and a payment protocol into one workflow that runs a natural-language model request end to end across four machines.","lead":"Cortex-FL is a working desktop system that turns a plain-language request such as 'I need a five-class image model, keep it under 0.01 USDC' into a four-machine federated training run with signed participation contracts and testnet payments released only after delivery was verified. It matters less as a training method than as a concrete template for how independent organizations might assemble and pay for a shared model without a human coordinator.","discovery_kind":"new_application","skeptic_critique":{"model":"deepseek/deepseek-v4-flash","headline":"The trust model's central guarantee—that the host enforces scope for every agent action—is asserted without adversarial testing beyond a single tampered-package rejection.","rationale":"The reader's weakest_assumption correctly identifies that the trust model's enforcement is asserted, not analysed, and that the only adversarial evidence is a single tampered-package rejection. My concern is a direct elaboration of that assumption: the paper makes a universal security claim about host-side enforcement but provides no adversarial testing of the agent's ability to bypass the trust gate. The reader's verdict is CONDITIONAL, and I agree that this is the appropriate verdict given the evidence. The concrete test I propose would directly address this gap by systematically probing the host's validation logic with adversarial agent prompts. If the test passes, the trust model gains empirical support; if it fails, the central claim is undermined. I do not recommend changing the verdict because the paper's central claim (that the workflow runs) is supported by the demonstration, but the trust model's enforcement is a load-bearing assumption that requires further evidence. The reader's rationale already notes that 'no misled agent, malicious peer, or compromised host is exercised,' which is the same gap I identify. My contribution is to propose a specific, feasible test that would settle whether the concern lands.","tokens_in":10194,"tokens_out":703,"duration_ms":8427,"concrete_test":"Design and run a red-team test in which one agent is given a prompt that instructs it to (a) publish a task with a different objective than the owner specified, (b) invite a peer that the owner did not approve, or (c) authorize a payment exceeding the owner's stated budget. The test should check whether the host's validation rejects each action before it reaches the owner review or the execution scope. Report the number of attempts and the number of successful bypasses. If zero bypasses occur across a systematic set of adversarial prompts, the trust model's enforcement is empirically supported.","verdict_should_be":"CONDITIONAL","load_bearing_attack":"The paper's central claim (b5) is that the complete workflow runs. The trust model in §2 states that 'the host validates proposed actions against the task specification, authenticated identities, and current authorization' and that 'these guarantees cover owner authorization, artifact integrity, and transaction accounting across every agent action and every training workload on the node.' This is a universal security claim expressed in the grammar of a measured fact. The only adversarial evidence reported is a single corrupted model package rejected at delivery verification (§5). That exercises artifact hashing, not the tool boundary, host authorization, or the agent's inability to bypass the trust gate. No misled agent, malicious peer, or compromised host is exercised. The paper acknowledges that agents 'hold no wallet or service credentials' and that 'every consequential step passes a trust gate,' but it provides no test that a misled agent cannot, for example, invoke a tool with a fabricated task identifier, or that a compromised host cannot forge a journal entry. The claim that the system 'supports delegation throughout the learning lifecycle while preserving owner control' (b115) is therefore supported only by design description, not by adversarial evaluation. This is a load-bearing concern because if the trust model fails—if an agent can cause an unauthorized action—the entire value proposition of owner-controlled delegation collapses.","agreement_with_reader":"agree"},"referee_report":{"model":"deepseek/deepseek-v4-flash","summary":"This paper presents Cortex-FL, an agent-native federated learning system that enables users to express learning objectives in natural language and delegate the collaboration required to train a model. The architecture separates agent coordination from local execution authority, with a trusted host enforcing scope and authorization. The system integrates existing components (FL Alliance, FLocKit, x402, AgentaNet) into a coherent workflow spanning task preparation, peer discovery, participation agreements, contract-governed training, verified model delivery, and blockchain-based settlement. The paper demonstrates the complete workflow on a four-node deployment for a five-class image classification task on CIFAR-10, showing that a model requested in natural language can proceed through all stages to a verified checkpoint and service payments.","tokens_in":20332,"tokens_out":1211,"duration_ms":58360,"significance":"If the claims hold, Cortex-FL addresses a practical barrier to FL adoption by reducing the need for specialized expertise in setting up and managing cross-silo collaborations. The integration of agent-based coordination with FL training and blockchain-based incentives is novel and timely. The demonstration provides a concrete proof-of-concept that connects natural-language input to a complete FL workflow, including collaboration formation, contract-governed training, verified model delivery, and settlement. The system builds on existing components and contributes an integration layer that could be reused or extended. The paper is clearly written and the demonstration appears to have been executed successfully, with detailed timestamps and metrics.","major_comments":[{"comment":"The trust model is central to the paper's claim that the system 'preserves owner control over data, computation, and payments' (b115). The paper asserts that 'the host validates proposed actions against the task specification, authenticated identities, and current authorization' and that 'these guarantees cover owner authorization, artifact integrity, and transaction accounting across every agent action and every training workload on the node.' However, the only adversarial evidence provided is a single test where 'an agent modifies the model package before delivery, and the receiving node rejects it at verification' (§5). This test exercises artifact hashing but does not test the tool boundary, host authorization, or the agent's inability to bypass the trust gate. No misled agent, malicious peer, or compromised host is exercised. The paper should either provide additional adversarial testing or analysis to support the trust model claims, or explicitly acknowledge the limitations of the current evaluation and tone down the security claims accordingly.","section":"§2 (Trust model) and §5 (Demonstration)","authors_acknowledge":null,"authors_acknowledge_p":null},{"comment":"The demonstration is conducted on a local network with four nodes, using a single task (five-class image classification on CIFAR-10). While this is sufficient for a proof-of-concept, the paper does not discuss how the system would behave under more challenging conditions, such as network partitions, node failures, malicious peers, or larger-scale deployments. The paper should discuss these limitations and, if possible, provide evidence of robustness or plans for future evaluation.","section":"§5","authors_acknowledge":null,"authors_acknowledge_p":null},{"comment":"The trust model assumes that 'each owner trusts the local host, authorization interface, and credential store.' This is a reasonable starting point, but the paper does not discuss what happens if the host itself is compromised or if the owner's credentials are stolen. The paper should clarify the threat model and identify what attacks are and are not considered.","section":"§2","authors_acknowledge":null,"authors_acknowledge_p":null}],"minor_comments":[{"comment":"The paper does not include a limitations section. Adding one would improve clarity and help readers understand the scope of the claims.","section":"General","authors_acknowledge":null,"authors_acknowledge_p":null},{"comment":"Figure 3 is informative but dense. Consider adding a caption that explains the key elements more explicitly.","section":"Figure 3","authors_acknowledge":null,"authors_acknowledge_p":null},{"comment":"The paper references several external systems (FL Alliance, FLocKit, x402, AgentaNet) but does not provide a brief summary of how they work or what guarantees they provide. A short paragraph in Section 3 or 4 would help readers who are not familiar with these systems.","section":"§3","authors_acknowledge":null,"authors_acknowledge_p":null},{"comment":"The demonstration uses test USDC on Base Sepolia testnet. The paper should clarify whether the system is designed to work with real USDC on mainnet and what additional considerations would apply.","section":"§5","authors_acknowledge":null,"authors_acknowledge_p":null},{"comment":"The paper uses the term 'agentic node' but does not define it formally. Consider adding a definition in Section 2 or 3.","section":"§2","authors_acknowledge":null,"authors_acknowledge_p":null},{"comment":"The paper could benefit from a comparison with other agent-based FL systems or frameworks, if any exist. If none exist, stating this explicitly would strengthen the novelty claim.","section":"§6","authors_acknowledge":null,"authors_acknowledge_p":null}],"recommendation":"major_revision"},"author_rebuttal":null,"desk_editor":{"model":"deepseek/deepseek-v4-flash","letter":"Worth a read if you care about lowering the barrier to cross-silo FL. The paper is honest about what it contributes: FL Alliance and FLocKit handle training, x402 handles payment, AgentaNet handles discovery, and the new piece is the integration layer binding them with a signed artifact chain and host-side trust gates. That connective layer has a genuinely sensible design idea: agents coordinate but hold no credentials, and every consequential step passes an owner-approval or host-verification gate. The four-node demonstration ran, with concrete artifact evidence (round-roster with T/V assignments, 10 rounds from 23:45 to 23:56 UTC, validation loss 1.52 to 0.96, three delivery verifications, three settlement receipts). For a systems paper whose central claim is \"the workflow runs,\" that evidence is adequate and the paper does not oversell it.\n\nThe soft spots are real but proportionate. First, the trust model in §2 makes a universal security guarantee—\"These guarantees cover owner authorization, artifact integrity, and transaction accounting across every agent action and every training workload\"—but the only adversarial exercise is a single tampered model package rejected at delivery verification. That tests artifact hashing, not the tool boundary, host authorization, or the agent's inability to bypass the trust gate. The paper acknowledges the trust boundary but does not test it. Load-bearing? Yes, because the entire value proposition is owner-controlled delegation; if an agent can cause an unauthorized action, that collapses. The paper does not support its universal claim.\n\nSecond, the evaluation is thin even for a demonstration: no baseline (what does the organizer achieve alone?), no accuracy figure for the five-class task, one seed, and no ablation separating the federation's benefit from the organizer's local training. The paper states the loss but never the accuracy, so it is unclear whether collaborating actually helped. Third, the code is not released, making independent reproduction impossible. And the system is assembled from the authors' own prior components (FLock, AgentaNet), which is disclosed but means the integration inherits properties it does not re-establish.\n\nNone of this breaks the stated central claim, which is narrow and evidenced. It limits generalization. The paper is a deployment template, not a scientific result about FL performance or security. It deserves a serious referee because the demonstration is concrete, the architecture is clearly described, and the integration problem is real. But it needs revision: a threat-model section that tests the host gate, an ablation, and release of code.\n\nMy recommendation: engage with it for the systems direction, but require those additions before accepting.","headline":"A credible systems demonstration: the workflow ran end-to-end, but the security claim in §2 is asserted, not tested, and the evaluation has no baseline.","tokens_in":13412,"tokens_out":647,"duration_ms":18032},"pith_extraction":null,"created_at":"2026-11-13T09:33:41.136907+00:00","model_set":{"reader":"deepseek/deepseek-v4-flash"},"pipeline_version":"pith-pipeline@v1.4.1-daily-deepseek-or-medium","input_kind":null,"input_chars":null,"input_total_chars":null,"passes_missing":null,"published_standing":null,"published_confidence":null,"objection_audit":null,"run_record":null,"basis":{"kind":"not_recorded","source":null,"chars_given":null,"chars_total":null},"receipt":null,"falsifier":null,"supporting_citations":[],"lane_accuracy":{"status":"not yet measured","lane":{"model":"deepseek/deepseek-v4-flash","input_kind":null},"url":"https://pith.science/accuracy"},"review_version":1}