Add a concrete 0-100 swarmness/compliance score, local large-scale stress, and 3000 TPM budget acceptance so the repo can say when it is a swarm by measured criteria instead of prose alone.
Constraint: user required Chinese docs, explicit scenarios, parameters, formulas, pass/fail lines, and git upload.
Rejected: prose-only PASS reports | they did not answer whether the system is a swarm with a concrete score.
Confidence: high
Scope-risk: moderate
Directive: keep production runtime claims separate from local minimal swarm acceptance scores.
Tested: py_compile swarm_minimal examples tests; unittest discover -s tests 45 tests; run_swarm_compliance_score.py; run_tpm_budget_acceptance.py; run_academic_standard_evaluation.py; git diff --check; docs/script secret-pattern scan.
Not-tested: live S07 and production Kubernetes/NewAPI provider-rate-limit stress were not rerun in this upload step.
Co-authored-by: OmX <omx@oh-my-codex.dev>
Make the user's six swarm characteristics first-class acceptance gates by adding S10/A07 tests, a standard document, and synchronized reports.
Constraint: The user asked to set acceptance indicators and test standard details around decentralization, self-organization, emergence, robustness, scalability, and implicit collaboration.
Rejected: Treating the six traits as prose-only documentation | they now run as deterministic tests and scenario matrix gates.
Confidence: high
Scope-risk: moderate
Directive: Future swarm-readiness claims must report F01-F06 explicitly and distinguish local Agent-layer proof from production no-coordinator runtime.
Tested: py_compile; unittest discover ran 41 tests; run_swarm_characteristics_acceptance PASS; run_academic_standard_evaluation A01-A07 PASS; run_standard_scenario_acceptance S01-S10 PASS with S07 run_id 9c7ccc6087c1435694a52efb12c32301; docs/README secret-pattern scan clean; git diff --cached --check clean.
Not-tested: Production no-coordinator distributed runtime and Kubernetes-scale worker telemetry remain outside this minimal local acceptance gate.
Co-authored-by: OmX <omx@oh-my-codex.dev>
Turn the remaining minimal-boundary items into executable behavior: locked autonomous claim scaling for 3/5/7 agents, multi-candidate fusion, and challenge-revise-revote consensus.
Constraint: The user asked to implement code directly, complete testing and acceptance, and explain the test standards rather than only updating the comparison document.
Rejected: Leaving SW-AQS-16, candidate fusion, and questioning consensus as documentation-only future work | each now has deterministic code paths and S09 acceptance evidence.
Confidence: high
Scope-risk: moderate
Directive: Future claims about full production readiness must still distinguish this local deterministic S09 acceptance from real runtime/Kubernetes scaling and Manager/Agnet platform integration.
Tested: .venv/bin/python -B -m py_compile swarm_minimal/*.py examples/*.py tests/*.py; .venv/bin/python -B -m unittest tests.test_standard_scenarios; .venv/bin/python -B -m unittest discover -s tests; .venv/bin/python -u -B examples/run_next_boundary_acceptance.py; .venv/bin/python -u -B examples/run_academic_standard_evaluation.py; .venv/bin/python -u -B examples/run_standard_scenario_acceptance.py; .venv/bin/python -B examples/export_model_agnet_io_report.py; .venv/bin/python -B -m unittest tests.test_model_io_report_audit; docs secret pattern scan; git diff --check.
Not-tested: Real Kubernetes/worker runtime 3/5/7 scaling, Redis Stream consumer-driven replanning, and Manager/Agnet approval integration remain outside this local minimal acceptance.
Co-authored-by: OmX <omx@oh-my-codex.dev>
Promote the S07 external FastAPI chain from score-only acceptance to a minimal quality-gated flow with refusal detection, retry/fallback recovery, handoff quality checks, and a multi-round consensus gate before final convergence.
Constraint: The user asked to fix the documented shortcomings around score-only convergence, weak refusal scoring, and unqualified handoff evidence while continuing the minimal version.
Rejected: Replacing the whole coordinator with a production consensus runtime | the minimal fix keeps the existing task pool/convergence shape and adds scenario-level quality gates plus consensus evidence.
Confidence: high
Scope-risk: moderate
Directive: Future S07 runs must keep all_outputs_pass_quality_gate and multi_round_quality_consensus_accepts_chain as required checks before claiming PASS.
Tested: .venv/bin/python -B -m unittest tests.test_standard_scenarios; .venv/bin/python -u -B examples/run_continuous_reasoning_acceptance.py; .venv/bin/python -B examples/export_model_agnet_io_report.py; .venv/bin/python -B -m unittest discover -s tests; .venv/bin/python -B -m py_compile swarm_minimal/*.py examples/*.py tests/*.py; .venv/bin/python -u -B examples/run_academic_standard_evaluation.py; .venv/bin/python -B -m unittest tests.test_model_io_report_audit; git diff --check; docs secret pattern scan.
Not-tested: The combined run_standard_scenario_acceptance wrapper was not rerun after report export to avoid creating a newer live run that would make the exported latest-run report stale.
Co-authored-by: OmX <omx@oh-my-codex.dev>
Define Agent and swarm-specific acceptance evidence, move the reports under docs, and make the homepage point to the current standard, live run, model I/O, and handoff evidence.
Constraint: Agent quality standards are configured from industry AI and agent risk references because there is no single accepted swarm-Agent certification standard.
Rejected: Treating py_compile or unittest as the primary quality standard | they are evidence collection tools, not the Agent quality standard itself.
Confidence: high
Scope-risk: moderate
Directive: Keep future standard reports under docs/ and keep secrets in ignored local .env files only.
Tested: git diff --cached --check; python -B -m py_compile swarm_minimal/*.py examples/*.py tests/*.py; python -B -m unittest discover -s tests; python -u -B examples/run_academic_standard_evaluation.py
Not-tested: Did not rerun the full live Azure/NewAPI S07 scenario after moving docs; previous live run 3e8e58ae4e084bc8b90cf5c46f8992f3 passed before the docs relocation.
Co-authored-by: OmX <omx@oh-my-codex.dev>
The standalone prototype should be the root-level project shape for fengqun while preserving the existing planning documents already at the root. This keeps README, examples, tests, and the Python package directly discoverable without deleting the prior docs.
Constraint: User clarified that swarm-minimal is the repository root, but other existing root files must remain.
Rejected: Deleting existing root docs | They are part of the fengqun repository context and were explicitly protected.
Confidence: high
Scope-risk: narrow
Directive: Keep secrets in ignored .env only; do not commit live credentials.
Tested: python3 -B -m unittest discover -s tests; git diff --check; secret-pattern scan showed only placeholders/test values/task-id false positives.
Not-tested: Remote web UI rendering after push.
