{ "schema_version": "v1", "title": "MSG Chain Development History", "generated_at": "2026-09", "public_boundary": "The public development history is a build narrative, not an evidence ledger: it explains in time order what engineering work was done, and every event states its own evidence state in its detail block. An event without public raw evidence cannot be independently checked, and it does not represent mainnet production verification.", "mainnet_status": "No-Go", "events": [ { "event_code": "E001", "display_title": "project initiation, conception, and early design drafting", "id": "msg-origin-2025-09-06", "date": "2025-09", "date_precision": "month", "event_type": "origin", "title_zh": "MSG 公链项目立项并开始构思", "title_en": "MSG Chain Project Initiation and Early Concept Design", "summary_zh": "项目开始围绕自主公链、节点、钱包和相关基础能力进行构思，并起草早期设计资料。", "summary_en": "The project began exploring an independent blockchain, node, wallet, and related foundational capabilities, with early design materials drafted.", "limitations_zh": "该日期是项目历史起点，不是主网上线日期，也不是任何功能完成日期；早期设计资料尚未逐项公开核验。", "limitations_en": "This date is the project's historical starting point. It is not a mainnet launch date and not the completion date of any feature; the early design materials have not been cross-checked item by item in public.", "implementation_status": "RegisteredUnstarted", "production_status": "not_production_verified", "evidence_status": "owner_confirmed_pending_archive_cross_check", "public_evidence_available": false, "evidence_level": "O", "affected_modules": [ "project", "architecture", "node", "wallet" ], "supersedes": [], "public_visibility": "candidate_public_event", "last_reviewed_at": "2026-08", "review_note": "the public version must state that the date is the project's historical starting point, not the mainnet launch date, nor a feature completion date.", "historical_context_zh": "项目负责人确认的项目发展史起点。早期具体实现路线、语言、平台和架构后来经历多次修订。", "historical_context_en": "the project history starting point confirmed by the project lead. The early specific implementation roadmap, language, platform, and architecture later underwent multiple revisions.", "public_status_labels": { "implementation_status": { "zh": "已登记，尚未开始", "en": "Registered, not started" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "项目负责人确认，待归档交叉核验", "en": "Owner-confirmed; archival cross-check pending" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E002", "display_title": "early Windows / Multi-platform engineering prototype formed", "id": "msg-early-engineering-2025-09-14", "date": "2025-09", "date_precision": "month", "event_type": "implementation", "title_zh": "形成早期公链工程和多平台打包材料", "title_en": "Early Chain Engineering and Multi-Platform Packaging Materials Formed", "summary_zh": "项目资料已包含源码、配置、钱包、创世数据、Go 模块以及 Windows、Linux、macOS 相关启动或部署材料。", "summary_en": "Project materials included source code, configuration, wallets, genesis data, Go modules, and Windows, Linux, and macOS startup or deployment materials.", "limitations_zh": "材料存在不等于所有平台均已运行或通过生产验收；公开版不展示本地路径与内部报告名称。", "limitations_en": "The existence of these materials does not mean every platform was running or had passed production acceptance; the public version omits local paths and internal report names.", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "documented_archival_record", "public_evidence_available": false, "evidence_level": "B", "affected_modules": [ "node", "wallet", "build", "deployment" ], "supersedes": [], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "review_note": "the public version does not show local paths, internal report names or archive scale; it retains only engineering stages and capability boundaries.", "historical_context_zh": "这是目前可核验的早期工程活动节点，不等于所有平台均已运行或生产验收。", "historical_context_en": "this is a currently verifiable early engineering activity node, and does not mean all platforms are running or have passed production acceptance.", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "文档归档记录", "en": "Documented archival record" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E003", "display_title": "Windows Electron wallet startup verification", "id": "msg-wallet-windows-validation-2025-09-18", "date": "2025-09", "date_precision": "month", "event_type": "test", "title_zh": "Windows 钱包完成早期启动验证", "title_en": "Early Windows Wallet Startup Validation", "summary_zh": "Windows Electron 钱包可以启动并进入验证，但当时多个节点连接和 RPC 联调仍不稳定。", "summary_en": "The Windows Electron wallet started successfully for early validation, while connections to multiple nodes and RPC integration remained unstable.", "limitations_zh": "该验证限于钱包启动与早期联调窗口，多节点连接与 RPC 稳定性当时仍存在已知缺口。", "limitations_en": "This validation is limited to the wallet startup and early integration window; multi-node connectivity and RPC stability still had known gaps at the time.", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "documented_validation_with_known_gaps", "public_evidence_available": false, "evidence_level": "B", "affected_modules": [ "wallet", "rpc", "node" ], "supersedes": [], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "review_note": "must not be written as the wallet having completed production-grade end-to-end access.", "historical_context_zh": "体现钱包界面与节点网络仍处于早期联调阶段。", "historical_context_en": "reflecting that the wallet interface and node network are still in an early joint-debugging stage.", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "存在已知缺口的文档验证", "en": "Documented validation with known gaps" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E004", "display_title": "Windows node, multi-node and multi-platform engineering organization", "id": "msg-chain-engineering-reorganization-2025-09-30", "date": "2025-09", "date_precision": "month", "event_type": "refactor", "title_zh": "完成早期公链工程目录整理", "title_en": "Early Chain Engineering Directory Reorganization", "summary_zh": "项目完成一次早期工程目录整理，形成 Windows 节点、多节点启动材料、Go 源码、钱包、配置和多平台部署目录。", "summary_en": "An early engineering reorganization brought together Windows nodes, multi-node startup materials, Go source code, wallets, configuration, and multi-platform deployment directories.", "limitations_zh": "这是工程目录整理事件，不代表相关平台已完成生产级部署或验收。", "limitations_en": "This is an engineering directory reorganisation event; it does not mean the related platforms had reached production deployment or acceptance.", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "archival_reorganization_report", "public_evidence_available": false, "evidence_level": "B", "affected_modules": [ "node", "wallet", "build", "deployment", "network" ], "supersedes": [], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "review_note": "cannot thereby claim all multi-platform production versions are available.", "historical_context_zh": "说明项目已从概念和单点工具逐步进入多节点工程化阶段。", "historical_context_en": "This shows the project has gradually moved from concepts and single-point tools into a multi-node engineering stage.", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "归档重组记录", "en": "Archival reorganization report" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E005", "display_title": "early multi-node round-robin block production verification", "id": "msg-multinode-rotation-2025-10-01", "date": "2025-10", "date_precision": "month", "event_type": "test", "title_zh": "完成早期多节点轮流出块阶段验证", "title_en": "Early Multi-Node Block Rotation Validation", "summary_zh": "在受控测试窗口内，多个节点参与轮流出块并持续产生区块。", "summary_en": "During a controlled test window, multiple nodes participated in block rotation and continued producing blocks.", "limitations_zh": "属受控测试窗口内的阶段性运行证据，不代表长期稳定性、真实公网 NAT 组网或主网生产验证。", "limitations_en": "This is staged runtime evidence from a controlled test window; it does not represent long-run stability, real public-network NAT peering, or mainnet production verification.", "implementation_status": "Implemented", "production_status": "not_production_verified", "evidence_status": "controlled_runtime_evidence", "public_evidence_available": false, "evidence_level": "A/B", "affected_modules": [ "consensus", "node", "network" ], "supersedes": [], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "review_note": "public copy must use \"controlled test window\" and \"stage verification\", and must not use \"mainnet consensus completed\".", "historical_context_zh": "这是阶段性运行证据，不代表长期稳定性、真实公网 NAT 组网或主网生产验证。", "historical_context_en": "this is staged runtime evidence, and does not represent long-term stability, real public network NAT networking or mainnet production verification.", "public_status_labels": { "implementation_status": { "zh": "已实现", "en": "Implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "受控运行证据", "en": "Controlled runtime evidence" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E006", "display_title": "node implementation, storage and runtime paths undergo refactoring", "id": "msg-runtime-refactor-2025-10-22", "date": "2025-10", "date_precision": "range", "event_type": "refactor", "title_zh": "节点、存储和运行目录进入多轮重构", "title_en": "Node, Storage, and Runtime Layout Refactoring", "summary_zh": "项目经历了节点实现差异、量子钱包资料形成、RocksDB 到 BadgerDB 的存储路线演进，以及数据、钱包、合约、配置和日志路径重组。", "summary_en": "The project went through node implementation changes, quantum-wallet material development, storage evolution from RocksDB toward BadgerDB, and reorganization of data, wallet, contract, configuration, and log paths.", "limitations_zh": "不同历史目录与实现不能视为同一版本的连续状态；存储路线演进也不代表迁移已完成验收。", "limitations_en": "The different historical directories and implementations must not be read as one continuous version; the storage-path migration also does not mean the migration had passed acceptance.", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "historical_runtime_and_refactor_records", "public_evidence_available": false, "evidence_level": "B/C", "affected_modules": [ "node", "storage", "wallet", "runtime", "deployment" ], "supersedes": [], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "review_note": "the public version does not expose historical repository paths, internal report names or local log names, and only describes roadmap evolution and known boundaries.", "historical_context_zh": "这是项目多次修订、替换和重新开发的重要阶段；不同历史目录和实现不能简单视为同一版本的连续状态。", "historical_context_en": "this is an important stage of multiple revisions, replacements, and redevelopment; different historical directories and implementations cannot simply be treated as the continuous state of the same version.", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "历史运行与重构记录", "en": "Historical runtime and refactor records" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E007", "display_title": "standard Go Engineering layout and WSL the build system forms", "id": "msg-clean-go-wsl-foundation-2025-11-13", "date": "2025-11", "date_precision": "range", "event_type": "refactor", "title_zh": "形成标准 Go 项目布局和 WSL/Linux 构建体系", "title_en": "Standard Go Layout and WSL/Linux Build Foundation", "summary_zh": "项目从早期代码形态逐步重构为标准 Go 工程布局，并形成 Go module、Linux 节点构建目标和 WSL 开发环境。", "summary_en": "The project evolved toward a standard Go layout with a Go module, Linux node build targets, and a WSL development environment.", "limitations_zh": "工程布局与构建体系形成，不等于所有模块已完成生产验收或主网可用。", "limitations_en": "Forming a project layout and build system does not mean every module had passed production acceptance or was mainnet-ready.", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "documented_build_and_layout_records", "public_evidence_available": false, "evidence_level": "B/C", "affected_modules": [ "build", "node", "consensus", "crypto", "storage" ], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "review_note": "the public version can say \"formed the main development engineering foundation\", but cannot say \"all capabilities are complete\".", "historical_context_zh": "这是当前统一工程路径逐渐成形的关键阶段，但不能据此证明所有模块已完成生产验收。", "historical_context_en": "this is a key stage in which the current unified engineering path is gradually taking shape, but it cannot prove that all modules have completed production acceptance.", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "文档化构建与布局记录", "en": "Documented build and layout records" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E008", "display_title": "CosmWasm, consensus and network capabilities enter the integration stage", "id": "msg-core-integration-2025-11-22", "date": "2025-11", "date_precision": "range", "event_type": "integration", "title_zh": "核心链能力进入持续集成和阶段测试", "title_en": "Core Chain Capabilities Entered Integration and Stage Testing", "summary_zh": "CosmWasm、Round-Robin、节点发现、验证者同步和 BadgerDB 等能力进入集成或阶段测试。", "summary_en": "CosmWasm, Round-Robin, node discovery, validator synchronization, and BadgerDB entered integration or stage testing.", "limitations_zh": "集成或阶段测试不等于生产闭环；经济模型与其他生产门禁在当时仍未全部完成。", "limitations_en": "Integration or staged testing is not a production closure; the economic model and other production gates were still incomplete at the time.", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "stage_reports_and_architecture_records", "public_evidence_available": false, "evidence_level": "B/C", "affected_modules": [ "consensus", "contracts", "network", "storage" ], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "historical_context_zh": "项目在此阶段继续集成和修复，经济模型及其他生产门禁仍未全部闭环。", "historical_context_en": "the project continues integration and fixes at this stage; the economic model and other production gates are not yet fully closed.", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "阶段报告与架构记录", "en": "Stage reports and architecture records" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E009", "display_title": "Clean Native roadmap determined", "id": "msg-clean-native-route-2025-12-08", "date": "2025-12", "date_precision": "month", "event_type": "design", "title_zh": "确定 Clean Native 与精准技术借力路线", "title_en": "Clean Native and Selective Technology Reuse Route Confirmed", "summary_zh": "项目确定以自主共识、Dilithium-5、BadgerDB、CosmWasm 和 libp2p 为核心，暂缓 IBC，并重新评估钱包和生态兼容性。", "summary_en": "The project confirmed a Clean Native route centered on independent consensus, Dilithium-5, BadgerDB, CosmWasm, and libp2p, while deferring IBC and reassessing wallet and ecosystem compatibility.", "limitations_zh": "该事件是路线确定，不代表所有代码迁移当天完成，也不代表 IBC 相关工作已被删除。", "limitations_en": "This is a route decision, not proof that all code migration finished that day, and not proof that the IBC-related work was deleted.", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "architecture_decision_record", "public_evidence_available": false, "evidence_level": "B", "affected_modules": [ "architecture", "consensus", "crypto", "storage", "contracts", "network", "wallet" ], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "review_note": "the public version should emphasize \"roadmap determined\" and \"continued implementation\", and must not be written as \"mainnet completed\".", "historical_context_zh": "此前的 Cosmos/Tendermint 兼容性路线被重新评估；该事件是路线确定，不代表所有代码迁移当天完成。", "historical_context_en": "previous Cosmos/Tendermint The compatibility route was re-evaluated; this event is a route determination and does not mean all code migration was completed that day.", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "架构决策记录", "en": "Architecture decision record" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E010", "display_title": "core chain event persistence continuous fixes", "id": "msg-event-persistence-fix-2025-12-18", "date": "2025-12", "date_precision": "month", "event_type": "implementation", "title_zh": "持续完善 CosmWasm 事件与 Receipt 数据流", "title_en": "CosmWasm Event and Receipt Data Flow Continued to Improve", "summary_zh": "项目继续修复事件持久化并完善 Receipt 事件数据流。", "summary_en": "The project continued improving event persistence and the Receipt event data flow.", "limitations_zh": "属工程收敛阶段的持续修复记录，不代表核心链功能当时已达到生产级稳定。", "limitations_en": "This is an ongoing-fix record from the engineering convergence stage; it does not mean the core chain functions had reached production-grade stability.", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "stage_completion_report", "public_evidence_available": false, "evidence_level": "B/C", "affected_modules": [ "contracts", "receipts", "api" ], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "historical_context_zh": "路线确定后仍有核心链功能持续修复，说明项目尚处于工程收敛阶段。", "historical_context_en": "after the roadmap was determined, core chain features are still being continuously fixed, indicating the project is still in an engineering convergence stage.", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "阶段完成报告", "en": "Stage completion report" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E011", "display_title": "Windows → WSL/Linux Development environment migration", "id": "msg-windows-to-wsl-2025-12-20", "date": "2025-12", "date_precision": "month", "event_type": "refactor", "title_zh": "因构建链限制完成主要开发环境向 WSL/Linux 迁移", "title_en": "Primary Development Environment Moved to WSL/Linux Due to Build Constraints", "summary_zh": "由于 Windows 下 wasmvm 动态库编译和链接存在限制，项目将主要开发和构建环境转向 WSL/Linux。", "summary_en": "Due to wasmvm dynamic-library build and linking constraints on Windows, the primary development and build environment moved to WSL/Linux.", "limitations_zh": "这是开发环境迁移，不代表 Windows 钱包或历史工程资料全部失效，也不代表迁移后所有功能立即完成。", "limitations_en": "This is a development-environment migration; it does not invalidate the Windows wallet or the historical engineering materials, and it does not mean every feature was finished right after the move.", "implementation_status": "Implemented", "production_status": "not_production_verified", "evidence_status": "handover_report_with_build_constraints", "public_evidence_available": false, "evidence_level": "B", "affected_modules": [ "build", "contracts", "node", "deployment" ], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "historical_context_zh": "这是开发环境迁移，不代表 Windows 钱包或历史工程资料全部失效，也不代表迁移后所有功能立即完成。", "historical_context_en": "this is a development environment migration, and does not represent Windows even if the wallet or historical engineering materials all become invalid, it does not mean all functions are immediately complete after migration.", "public_status_labels": { "implementation_status": { "zh": "已实现", "en": "Implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "含构建约束的交接报告", "en": "Handover report with build constraints" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E012", "display_title": "continuous integration, stage verification, and roadmap closure", "id": "msg-continued-engineering-2025-12-24", "date": "2025-12/2026-08", "date_precision": "range", "event_type": "status_review", "title_zh": "在统一工程路径上持续推进核心能力和生产门禁", "title_en": "Continued Core Engineering and Production-Gate Work on the Unified Codebase", "summary_zh": "项目在统一工程路径上持续推进共识、网络、经济模型、PQC、AI、钱包、Explorer 和白皮书机器入口等能力，并通过阶段性测试、证据门禁和状态复核区分本地实现与生产验证。", "summary_en": "On the unified engineering path, the project continued work on consensus, networking, economics, PQC, AI, wallet, Explorer, and whitepaper machine-entry capabilities, using stage tests, evidence gates, and status reviews to distinguish local implementation from production verification.", "limitations_zh": "该阶段跨越多个开发周期，具体能力状态必须以对应模块的最新状态与证据为准，不得据此阶段记录推断生产可用。", "limitations_en": "This stage spans several development cycles. The status of any specific capability must come from that module's latest status and evidence; this stage record must not be used to infer production availability.", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "mixed_stage_and_production_gap_records", "public_evidence_available": false, "evidence_level": "B/C", "affected_modules": [ "consensus", "network", "economy", "pqc", "ai", "wallet", "explorer", "documentation" ], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "review_note": "must not treat this umbrella event as all modules having Production.", "historical_context_zh": "该阶段跨越多个开发周期，具体能力的状态必须以对应模块的最新状态和证据为准。", "historical_context_en": "This stage spans multiple development cycles; the status of specific capabilities must be based on the latest status and evidence of the corresponding module.", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "阶段记录与生产缺口记录混合", "en": "Mixed stage and production-gap records" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E012-A", "display_title": "DAR and phased progress of contract event persistence", "id": "msg-detail-dar-contract-persistence-2025-12-24", "parent_event_id": "msg-continued-engineering-2025-12-24", "phase_id": "phase_g_clean_native_continued_engineering", "milestone_level": "detail_milestone", "date": "2025-12", "date_precision": "month", "event_type": "implementation", "title_zh": "DAR 与合约事件持久化进入专项实现与验证", "title_en": "DAR and Contract Event Persistence Entered Focused Implementation and Validation", "summary_zh": "阶段报告记录了事件持久化、Receipt 数据流、BadgerDB 资源释放和 DAR 设计工作的推进。", "summary_en": "Stage records describe progress on event persistence, receipt data flow, BadgerDB resource release, and DAR design work.", "historical_context_en": "This node split the year-end integration stage into traceable focused workstreams. It records an engineering convergence process, not a final completion statement for DAR or the contract paths.", "narrative_zh": "该节点将年底集成阶段拆分为可追溯的专项工作：先处理会影响测试稳定性的存储资源问题，再继续推进合约事件与 DAR 机制。它记录的是工程收敛过程，而非 DAR 或全部合约路径的最终完成声明。", "narrative_en": "This node separates year-end integration into traceable work: storage lifecycle issues affecting test stability were addressed while contract events and DAR continued to advance. It records engineering convergence, not final completion of DAR or all contract paths.", "background_zh": "Clean Native 路线已确定，但真实 VM、DAR 和持久化链路仍存在待完成项。", "background_en": "The Clean Native route was set, while real VM, DAR, and persistence paths still had open work.", "problem_zh": "集成测试曾受资源生命周期和并发关闭问题影响；阶段报告也将 DAR 列为尚需实施与验证的能力。", "problem_en": "Integration testing had resource-lifecycle and concurrent-shutdown issues, and DAR remained an implementation and validation workstream.", "solution_zh": "通过迭代器追踪、优雅关闭和测试修复改善受控集成环境，并将 DAR 与事件持久化继续纳入专项工作。", "solution_en": "Iterator tracking, graceful shutdown, and test fixes improved the controlled integration environment while DAR and event persistence remained focused workstreams.", "rejected_or_replaced_approach_zh": "不以单次测试通过或阶段报告中的完成率替代长期运行、链上 query/receipt 与生产验证。", "rejected_or_replaced_approach_en": "A single passing test or reported completion percentage is not substituted for long-running, on-chain query/receipt, or production verification.", "development_steps": [ "Locate resource leaks and shutdown issues", "fix controlled integration test", "continuously complete events/Receipt data flow", "plan and advance DAR dedicated" ], "outcome_zh": "形成了后续真实 VM、DAR 合约和稳定性工作的工程前提。", "outcome_en": "The work established engineering prerequisites for subsequent real-VM, DAR-contract, and stability efforts.", "limitations_zh": "DAR 当时仍未形成生产级闭环；原始运行证据和最终合约验收需按后续事件单独判断。", "limitations_en": "DAR did not yet have a production-grade closure; raw runtime evidence and final contract acceptance must be assessed by later events.", "current_status": "historical_stage_record", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "stage_report_with_focused_test_excerpt", "public_evidence_available": false, "evidence_level": "B/C", "affected_modules": [ "consensus", "dar", "contracts", "receipts", "storage" ], "related_events": [ "msg-event-persistence-fix-2025-12-18", "msg-detail-libp2p-rpc-api-2025-12-25" ], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "historical_context_zh": "该节点把年底集成阶段拆分为可追溯的专项工作，记录的是工程收敛过程，而非 DAR 或合约路径的最终完成声明。", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "含聚焦测试摘录的阶段报告", "en": "Stage report with focused test excerpt" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E012-B", "display_title": "libp2p and RPC/API the roadmap enters dedicated integration", "id": "msg-detail-libp2p-rpc-api-2025-12-25", "parent_event_id": "msg-continued-engineering-2025-12-24", "phase_id": "phase_g_clean_native_continued_engineering", "milestone_level": "detail_milestone", "date": "2025-12", "date_precision": "month", "event_type": "integration", "title_zh": "libp2p 与 RPC/API 的集成路线被拆分推进", "title_en": "libp2p and RPC/API Integration Workstreams Were Split and Advanced", "summary_zh": "网络从早期 P2P 形态向 libp2p 集成推进，RPC/API 标准化被保留为独立后续工作。", "summary_en": "Networking advanced from earlier P2P forms toward libp2p integration, while RPC/API standardization remained a separate follow-on workstream.", "historical_context_en": "This node shows the network and interface layer entering a focused integration period. Starting focused integration is not the same as completing cross-public-network peering or interface production acceptance.", "narrative_zh": "该事件反映了 L2 网络与 L3 接口并非同时完成：libp2p、发现、同步和安全能力进入集成，而标准 JSON-RPC、gRPC、REST 的完整对外面仍有阶段边界。", "narrative_en": "This event records that L2 networking and L3 interfaces were not completed together: libp2p, discovery, synchronization, and security entered integration, while complete public JSON-RPC, gRPC, and REST surfaces retained stage boundaries.", "background_zh": "Clean Native 选择 libp2p 作为网络技术借力，同时保留自主核心。", "background_en": "Clean Native selected libp2p as targeted networking reuse while retaining an independent core.", "problem_zh": "早期节点通信、流帧、关闭和接口一致性仍需在受控环境中持续修复。", "problem_en": "Early node communication, stream framing, shutdown, and interface consistency still required controlled-environment fixes.", "solution_zh": "以 libp2p 的发现、pubsub、relay 等能力逐步集成；将接口标准化明确留为后续阶段而非虚报完成。", "solution_en": "libp2p discovery, pubsub, relay, and related capabilities were integrated incrementally; interface standardization was explicitly retained for a later phase.", "rejected_or_replaced_approach_zh": "不再将简单 P2P 或内部接口直接描述为完整公网 RPC/API 标准。", "rejected_or_replaced_approach_en": "Simple P2P or internal interfaces were not represented as complete public RPC/API standards.", "development_steps": [ "sort out L2/L3 Boundary", "advance libp2p integration and stream processing", "fix node communication test", "register RPC/API standardization follow-up items" ], "outcome_zh": "形成网络集成和接口标准化分层推进的工作边界。", "outcome_en": "The work established separate advancement boundaries for network integration and interface standardization.", "limitations_zh": "当时不构成广域网、跨 NAT、公共 API 或主网验证证据。", "limitations_en": "It was not evidence of WAN, cross-NAT, public API, or mainnet verification.", "current_status": "historical_stage_record", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "stage_reports_and_implementation_records", "public_evidence_available": false, "evidence_level": "B/C", "affected_modules": [ "network", "libp2p", "rpc", "api", "consensus" ], "related_events": [ "msg-detail-dar-contract-persistence-2025-12-24", "msg-detail-nat-real-vm-2026-01" ], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "historical_context_zh": "该节点反映网络与接口层进入专项集成期；专项集成开始不等于跨公网组网或接口生产验收已经完成。", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "阶段报告与实现记录", "en": "Stage reports and implementation records" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E012-C", "display_title": "NAT, cross-home network and real CosmWasm VM dedicated verification", "id": "msg-detail-nat-real-vm-2026-01", "parent_event_id": "msg-continued-engineering-2025-12-24", "phase_id": "phase_h_network_and_real_vm_validation", "milestone_level": "major_detail_milestone", "date": "2026-01", "date_precision": "range", "event_type": "integration", "title_zh": "开展 NAT、跨家庭网络与真实 CosmWasm VM 验证", "title_en": "NAT, Cross-Household Networking, and Real CosmWasm VM Validation Conducted", "summary_zh": "记录显示开展了 NAT/跨家庭网络联调；月底真实 CosmWasm VM 取代运行时 Mock 路径并完成受控启动验证。", "summary_en": "Records show NAT and cross-household networking exercises, while the real CosmWasm VM replaced the runtime mock path and completed controlled startup validation at month end.", "historical_context_en": "This node is an early focused validation window for real networking and a real VM. Passing inside the validation window does not imply long-run stability or public availability.", "narrative_zh": "网络侧持续尝试 NAT 穿透、relay 与跨家庭网络联调；合约侧定位到 CGO 构建配置使真实 wasmvm 未进入二进制的问题，并在 Linux 环境启用真实 VM。两条线均属于阶段性工程验证。", "narrative_en": "Networking continued NAT traversal, relay, and cross-household exercises. On contracts, a CGO build configuration was found to exclude real wasmvm from the binary, and the real VM was enabled on Linux. Both lines are stage engineering validation.", "background_zh": "统一工程已迁至 WSL/Linux，网络和合约运行时均需摆脱本地简化路径。", "background_en": "The unified engineering path had moved to WSL/Linux, and both networking and contract runtime needed to move beyond local simplified paths.", "problem_zh": "NAT 环境存在连接不确定性；运行节点曾因 CGO 配置回退到 Mock 执行器。", "problem_en": "NAT environments had connectivity uncertainty, and node runtime had fallen back to a mock executor because of CGO configuration.", "solution_zh": "持续验证发现、relay、同步和 NAT 路径；启用 CGO、链接 wasmvm 并检查真实 VM 初始化日志。", "solution_en": "Discovery, relay, synchronization, and NAT paths were exercised; CGO was enabled, wasmvm linked, and real-VM initialization checked.", "rejected_or_replaced_approach_zh": "以运行时 Mock 执行器替代真实 VM 的路径被替换；单机 NAT 成功不被等同于公网生产网络。", "rejected_or_replaced_approach_en": "The runtime mock-executor path was replaced; single-environment NAT success was not equated with a public production network.", "development_steps": [ "NAT/relay/cross-home-network joint debugging", "locate CGO build exclusion", "Enable real wasmvm", "check binary links and initialization logs", "retain subsequent acceptance of core contracts" ], "outcome_zh": "真实 VM 在受控节点启动，网络验证积累了后续跨网工作的工程输入。", "outcome_en": "The real VM started in a controlled node, and networking exercises supplied engineering inputs for later cross-network work.", "limitations_zh": "核心合约端到端验收、长期公网 NAT 运行和生产部署均未由该事件证明。", "limitations_en": "This event did not prove end-to-end core-contract acceptance, long-running public NAT operation, or production deployment.", "current_status": "historical_stage_record", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "controlled_runtime_and_stage_reports", "public_evidence_available": false, "evidence_level": "B/C", "affected_modules": [ "network", "libp2p", "nat", "relay", "wasm", "contracts", "build" ], "related_events": [ "msg-detail-libp2p-rpc-api-2025-12-25", "msg-detail-network-block-production-2026-02" ], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "historical_context_zh": "该节点是早期真实网络与真实 VM 的专项验证窗口；验证窗口内的通过不代表长期稳定性或公网可用性。", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "受控运行与阶段报告", "en": "Controlled runtime and stage reports" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E012-D", "display_title": "test chain continuous block production and stability fixes", "id": "msg-detail-network-block-production-2026-02", "parent_event_id": "msg-continued-engineering-2025-12-24", "phase_id": "phase_i_test_chain_stability", "milestone_level": "major_detail_milestone", "date": "2026-02", "date_precision": "month", "event_type": "test", "title_zh": "测试链围绕轮流出块和稳定性开展修复验证", "title_en": "Test Chain Performed Block-Rotation and Stability Fix Validation", "summary_zh": "二月记录了轮流出块、区块间隔、存储和稳定性测试的修复与阶段验证。", "summary_en": "February records cover fixes and stage validation for block rotation, block intervals, storage, and stability testing.", "historical_context_en": "This node records sustained test-chain block production and stability fixes. A test chain producing blocks is not mainnet production operation.", "narrative_zh": "该阶段关注受控测试链是否能持续出块、节点是否保持一致，以及已发现的间隔、同步和存储问题能否被复现与修复。", "narrative_en": "This phase focused on whether a controlled test chain could continue block production, maintain node consistency, and reproduce and address interval, synchronization, and storage issues.", "background_zh": "真实 VM 与网络集成后，需要验证共识运行路径的连续性。", "background_en": "After real-VM and network integration, continuity of the consensus runtime path needed validation.", "problem_zh": "历史报告记录轮流出块、区块间隔和节点一致性存在需要修复或持续观察的风险。", "problem_en": "Historical reports record risks in block rotation, block interval behavior, and node consistency that required fixes or continued observation.", "solution_zh": "通过受控多节点启动、出块/快照/稳定性测试和针对性修复进行阶段验证。", "solution_en": "Controlled multi-node startup, production/snapshot/stability tests, and targeted fixes were used for stage validation.", "rejected_or_replaced_approach_zh": "不将报告中的“测试稳定”直接转换为主网稳定或长期公网 SLO。", "rejected_or_replaced_approach_en": "Reported test stability was not translated directly into mainnet stability or long-running public SLOs.", "development_steps": [ "Reproduce block production and interval issues", "fix round-robin block production related paths", "execution stability and snapshot check", "record remaining observation items" ], "outcome_zh": "形成测试链持续出块的阶段性资料和后续稳定性门禁输入。", "outcome_en": "The work produced stage materials for continuing test-chain production and later stability gates.", "limitations_zh": "未形成最终候选绑定的 24h/公网/生产证据，不能解除 No-Go。", "limitations_en": "It did not create final-candidate-bound 24-hour, public-network, or production evidence and cannot lift No-Go.", "current_status": "historical_stage_record", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "controlled_test_and_fix_reports", "public_evidence_available": false, "evidence_level": "B/C", "affected_modules": [ "consensus", "quantum_node", "storage", "testing" ], "related_events": [ "msg-detail-nat-real-vm-2026-01", "msg-detail-security-pqc-dar-ai-2026-03" ], "public_visibility": "public_after_sanitization", "last_reviewed_at": "2026-08", "historical_context_zh": "该节点记录测试链持续出块与稳定性修复；测试链持续出块不等于主网生产运行。", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "受控测试与修复记录", "en": "Controlled test and fix reports" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E012-E", "display_title": "system security, PQC, DAR and AI dedicated review", "id": "msg-detail-security-pqc-dar-ai-2026-03", "parent_event_id": "msg-continued-engineering-2025-12-24", "phase_id": "phase_j_security_and_architecture_review", "milestone_level": "major_detail_milestone", "date": "2026-03", "date_precision": "month", "event_type": "security", "title_zh": "系统安全、PQC、DAR 与 AI 接口进入专项审查", "title_en": "System Security, PQC, DAR, and AI Interfaces Entered Focused Review", "summary_zh": "三月资料对 SHA3-512 覆盖、DAR 合约机制、硬编码风险、Code is Law 和 AI 工具使用边界进行了分析。", "summary_en": "March materials analyze SHA3-512 coverage, DAR contract mechanisms, hard-coded risks, Code is Law, and AI tool-use boundaries.", "historical_context_en": "This node reviews security, PQC, DAR and AI as parallel focused workstreams. Review and fix records do not mean those areas had passed production-grade acceptance.", "narrative_zh": "这一事件是审查与风险收敛节点，目标是让密码学覆盖、资格/评分机制、节点配置和 AI 接口的断言可被检查，而非凭分析报告宣称安全审计完成。", "narrative_en": "This event is a review and risk-convergence node intended to make cryptographic coverage, qualification/scoring, node configuration, and AI-interface claims inspectable, not to claim a completed security audit from analysis reports.", "background_zh": "随着网络、VM 和链功能推进，跨模块安全边界成为主线问题。", "background_en": "As networking, VM, and chain-feature work advanced, cross-module security boundaries became a central concern.", "problem_zh": "PQC 覆盖、DAR 规则、硬编码与 AI 工具调用均可能造成状态、权限或可审计性风险。", "problem_en": "PQC coverage, DAR rules, hard-coded values, and AI tool calls could each create state, authorization, or auditability risks.", "solution_zh": "开展源码/规则分析，形成待修复与待验证清单，并坚持 Code is Law 与真实证据边界。", "solution_en": "Source and rule analysis produced remediation and validation lists while retaining Code is Law and real-evidence boundaries.", "rejected_or_replaced_approach_zh": "拒绝将静态分析、AI 建议或文档自述当作安全收口或生产安全证明。", "rejected_or_replaced_approach_en": "Static analysis, AI suggestions, and self-reported documentation were not treated as security closure or production-security proof.", "development_steps": [ "Review hash/PQC coverage", "analysis DAR Contract rules", "check hardcoding and on-chain rule boundaries", "sort out AI Tool call risks", "register follow-up fixes" ], "outcome_zh": "形成跨安全域问题的可追溯审查输入。", "outcome_en": "The work created traceable review inputs across security domains.", "limitations_zh": "未替代真实公网节点的端到端安全验证；主网仍为 No-Go。", "limitations_en": "It does not replace end-to-end security validation on real public-network nodes; mainnet remains No-Go pending the official launch announcement.", "current_status": "historical_review_record", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "analysis_and_review_records", "public_evidence_available": false, "evidence_level": "B/C", "affected_modules": [ "crypto", "pqc", "dar", "contracts", "ai", "governance" ], "related_events": [ "msg-detail-network-block-production-2026-02", "msg-detail-economic-model-2026-04" ], "public_visibility": "internal_only_pending_security_review", "last_reviewed_at": "2026-08", "historical_context_zh": "该节点把安全、PQC、DAR 与 AI 并列做专项审查；审查与修复记录不等于这些领域已完成生产级验收。", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "分析与复核记录", "en": "Analysis and review records" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E012-F", "display_title": "the new economic model enters the implementation and evidence closed loop stage", "id": "msg-detail-economic-model-2026-04", "parent_event_id": "msg-continued-engineering-2025-12-24", "phase_id": "phase_k_new_economic_model", "milestone_level": "major_detail_milestone", "date": "2026-04", "date_precision": "month", "event_type": "implementation", "title_zh": "新经济模型进入实施、测试与证据闭环", "title_en": "New Economic Model Entered Implementation, Testing, and Evidence Closure", "summary_zh": "新口径以经济秒、双池累加器、资格审计、处罚闭环和金库制度替换历史经济表述，并要求真实 query/tx/receipt/log 证据。", "summary_en": "The new model replaces historical economic narratives with economic seconds, dual-pool accumulators, qualification audits, penalty closure, and treasury rules, requiring real query/tx/receipt/log evidence.", "historical_context_en": "This node marks the new economic model moving from design into implementation and evidence closure. Implementation and evidence closure are not genesis deployment or mainnet activation.", "narrative_zh": "四月是经济规则重构的关键节点。该阶段不仅调整公式，也要求合约化、状态可查询和证据可回放；现行基线明确 Phase 0-6 主体完成但仍有金库和注册中心闭环缺口。", "narrative_en": "April is a key economic-rule reconstruction point. It changes not only formulas but requires contractualization, queryable state, and replayable evidence; the current baseline says Phases 0-6 are substantially complete while treasury and registry closures remain open.", "background_zh": "旧总量、创世预分配、固定每块奖励和旧候选池补贴口径不能继续作为现行规则。", "background_en": "Historical total-supply, genesis pre-allocation, fixed per-block reward, and old candidate-pool subsidy narratives cannot remain current rules.", "problem_zh": "旧经济口径与现行目标不一致，且缺少完整的链上结算、金库和 canonical key 证据闭环。", "problem_en": "Historical economic narratives diverged from current goals and lacked complete on-chain settlement, treasury, and canonical-key evidence closure.", "solution_zh": "实施 economic seconds、双池 reward debt、Gas 分账、资格/处罚与治理边界，并以真实链上证据作为验收条件。", "solution_en": "Implement economic seconds, dual-pool reward debt, gas distribution, qualification/penalty, and governance boundaries, with real on-chain evidence as acceptance criteria.", "rejected_or_replaced_approach_zh": "明确替换 100 亿封顶、2100 万创世预分配、固定块奖励及旧候选/Archive 池口径。", "rejected_or_replaced_approach_en": "The 10-billion cap, 21-million genesis pre-allocation, fixed block rewards, and old candidate/archive-pool narratives are explicitly replaced.", "development_steps": [ "Define the new economic constitution and governance parameters", "Implement dual pools and reward debt", "Contractization Gas/treasury/qualification/penalty", "execute tests and query/tx/receipt/log evidence gathering", "register remaining closure gaps" ], "outcome_zh": "形成现行经济模型实施主线及严格证据门槛。", "outcome_en": "The work established the current economic-model implementation line and strict evidence threshold.", "limitations_zh": "截至复核日，基金会金库双门槛、金库入账 raw 证据与 registry canonical key query 闭环仍未完成；不得进入网络收口，主网 No-Go。", "limitations_en": "As of review, treasury dual-threshold testing, treasury inflow raw evidence, and registry canonical-key query closure remain open; network closure must not begin and mainnet is No-Go.", "current_status": "phase_0_to_6_substantially_complete_with_open_closures", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "mixed_implementation_tests_and_open_raw_evidence_gaps", "public_evidence_available": false, "evidence_level": "B/C", "affected_modules": [ "economy", "contracts", "governance", "treasury", "registry", "receipts" ], "related_events": [ "msg-detail-security-pqc-dar-ai-2026-03", "msg-detail-pqc-libp2p-identity-ruling-2026-04-29" ], "public_visibility": "public_after_evidence_closure_and_sanitization", "last_reviewed_at": "2026-08", "historical_context_zh": "该节点标志新经济模型从设计进入实施与证据闭环；实施与证据闭环不等于创世部署或主网激活。", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "实现测试记录与待补原始证据缺口混合", "en": "Mixed implementation tests and open raw-evidence gaps" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E012-G", "display_title": "PQC and libp2p identity roadmap ruling", "id": "msg-detail-pqc-libp2p-identity-ruling-2026-04-29", "parent_event_id": "msg-continued-engineering-2025-12-24", "phase_id": "phase_l_pqc_ai_route_governance", "milestone_level": "decision_detail_milestone", "date": "2026-04", "date_precision": "month", "event_type": "design", "title_zh": "裁决 PQC 与 libp2p 身份的分层路线", "title_en": "PQC and libp2p Identity Layering Route Decided", "summary_zh": "路线文件界定量子身份、网络身份与兼容层的职责，避免把 libp2p 现有身份能力误写为完整 PQC 身份闭环。", "summary_en": "Route materials define responsibilities among quantum identity, network identity, and compatibility layers, avoiding representation of existing libp2p identity as a complete PQC identity closure.", "historical_context_en": "This node records a ruling on the identity route. A ruling fixes a direction; it does not mean the related implementation finished that day.", "narrative_zh": "该裁决将“传输/网络身份可用”与“链上或共识身份的后量子安全”分开建模，并把迁移、绑定和验证视为需要独立验证的工程项。", "narrative_en": "The decision models usable transport/network identity separately from post-quantum security for on-chain or consensus identity, treating migration, binding, and verification as independently validated engineering work.", "background_zh": "Clean Native 路线要求 Dilithium-5 等 PQC 能力与 libp2p 生态集成同时保持边界清晰。", "background_en": "The Clean Native route requires PQC capabilities such as Dilithium-5 to integrate with the libp2p ecosystem while retaining clear boundaries.", "problem_zh": "身份域混用会导致安全声明、签名域和兼容性判断失真。", "problem_en": "Mixing identity domains can distort security claims, signing domains, and compatibility assessments.", "solution_zh": "采用分层身份路线并登记实施、迁移和核查要求。", "solution_en": "A layered identity route was adopted with implementation, migration, and verification requirements recorded.", "rejected_or_replaced_approach_zh": "拒绝把单一 libp2p identity、单一兼容适配或文档声明作为 PQC 全链路完成证明。", "rejected_or_replaced_approach_en": "A single libp2p identity, compatibility adapter, or documentation claim was rejected as proof of complete end-to-end PQC coverage.", "development_steps": [ "organize identity domains", "Definition PQC and network identity boundary", "register binding/migration/verification requirements", "Incorporate the roadmap into subsequent evidence indexes" ], "outcome_zh": "形成可审查的身份路线裁决和后续工程边界。", "outcome_en": "The work produced a reviewable identity-route decision and subsequent engineering boundary.", "limitations_zh": "这是路线裁决和实施索引，不是生产密钥迁移完成证据。", "limitations_en": "This is a route decision and implementation index, not proof of production key migration completion.", "current_status": "design_and_evidence_index_record", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "route_decision_and_evidence_index", "public_evidence_available": false, "evidence_level": "B/C", "affected_modules": [ "crypto", "pqc", "libp2p", "identity", "consensus", "network" ], "related_events": [ "msg-detail-economic-model-2026-04", "msg-detail-whitepaper-ai-entry-2026-05-06" ], "public_visibility": "public_after_independent_security_review", "last_reviewed_at": "2026-08", "historical_context_zh": "该节点是对身份路线的裁决记录；裁决确定方向，不代表相关实现当日全部完成。", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "路线决策与证据索引", "en": "Route decision and evidence index" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E012-H", "display_title": "whitepaper and AI entry engineering", "id": "msg-detail-whitepaper-ai-entry-2026-05-06", "parent_event_id": "msg-continued-engineering-2025-12-24", "phase_id": "phase_m_whitepaper_ai_entry_engineering", "milestone_level": "detail_milestone", "date": "2026-05/2026-06", "date_precision": "range", "event_type": "documentation", "title_zh": "白皮书与 AI 入口进入结构化工程化", "title_en": "Whitepaper and AI Entry Surfaces Entered Structured Engineering", "summary_zh": "白皮书系统、状态矩阵、结构化接口和外部 AI-Agent 生态需求被整理为可维护的工程输入。", "summary_en": "The whitepaper system, status matrices, structured interfaces, and external AI-agent ecosystem requirements were organized into maintainable engineering inputs.", "historical_context_en": "This node marks the whitepaper and AI entry moving into engineering maintenance. A working public machine entry is not completed mainnet capability.", "narrative_zh": "五月至六月的工作重点是让技术资料、机器入口和开发规划能够结构化维护与审计，同时将规划、实施和生产状态分离。", "narrative_en": "May-to-June work focused on making technical materials, machine entry, and development planning structurally maintainable and auditable, while separating planning, implementation, and production states.", "background_zh": "随着模块和证据增加，单纯叙述性文档不足以支撑公开解释和 AI 检索。", "background_en": "As modules and evidence increased, narrative-only documentation could no longer support public explanation and AI retrieval.", "problem_zh": "资料分散、状态口径易漂移，且 AI 入口可能误把规划或本地状态解读为现状。", "problem_en": "Materials were scattered, status language could drift, and AI entry points could misread plans or local states as current capability.", "solution_zh": "建设白皮书结构、状态矩阵、接口清单和外部 Agent 能力缺口清单，并保留公开前脱敏与核验要求。", "solution_en": "Whitepaper structure, status matrices, interface inventories, and external-agent capability gap lists were developed while retaining pre-publication sanitization and verification requirements.", "rejected_or_replaced_approach_zh": "拒绝把文档、JSON 或 AI 可读入口本身作为链功能已上线的证明。", "rejected_or_replaced_approach_en": "Documentation, JSON, or AI-readable entry points were not treated as proof that chain capabilities were live.", "development_steps": [ "organize whitepaper system differences", "Create state/interface list", "organize external AI-Agent capability gap", "retain publicization and mainnet gates" ], "outcome_zh": "形成后续公开机器入口维护的工程基础。", "outcome_en": "The work created an engineering foundation for later public machine-entry maintenance.", "limitations_zh": "多数内容属于文档、设计或待办输入，应按 D/C 级处理；不构成主网、外部生态或生产 AI 服务已验证。", "limitations_en": "Much of the content is documentation, design, or backlog input and is treated as D/C evidence; it does not verify mainnet, external ecosystem, or production AI services.", "current_status": "documentation_and_planning_record", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "documentation_design_and_gap_analysis", "public_evidence_available": false, "evidence_level": "C/D", "affected_modules": [ "whitepaper", "documentation", "ai", "api", "rag" ], "related_events": [ "msg-detail-pqc-libp2p-identity-ruling-2026-04-29", "msg-detail-ai-constitution-resource-control-plane-2026-07" ], "public_visibility": "public_after_sanitization_and_status_review", "last_reviewed_at": "2026-08", "historical_context_zh": "该节点标志白皮书与 AI 入口进入工程化维护；公开机器入口可用不等于主网能力完成。", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "文档、设计与缺口分析", "en": "Documentation, design, and gap analysis" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E012-I", "display_title": "AI Constitution, C11, resource ecosystem, and control plane degradation", "id": "msg-detail-ai-constitution-resource-control-plane-2026-07", "parent_event_id": "msg-continued-engineering-2025-12-24", "phase_id": "phase_n_ai_governance_resource_ecosystem", "milestone_level": "major_detail_milestone", "date": "2026-07", "date_precision": "month", "event_type": "design", "title_zh": "AI 宪法、C11、资源生态与控制面降级进入主线治理", "title_en": "AI Constitution, C11, Resource Ecosystem, and Control-Plane Degradation Entered Mainline Governance", "summary_zh": "七月资料将人机平权 AI 宪法、C11 真实环境验证、节点/技能包资源生态和 Cloudflare 等控制面降级纳入依赖化任务体系。", "summary_en": "July materials place the human-AI equality constitution, C11 real-environment validation, node/skill-package resource ecosystem, and degradation of control planes such as Cloudflare into dependency-managed workstreams.", "historical_context_en": "This node covers the AI constitution, the resource ecosystem and control-plane downgrades. A control-plane downgrade exists to keep the boundary honest; it does not mean the related capability is ready.", "narrative_zh": "该阶段把 AI 自治、资源发布获取、通信 C11 和中心化辅助控制面的风险统一纳入可审计的前置任务，而不是将其包装为已上线生态。", "narrative_en": "This phase puts AI autonomy, resource publish/acquire, communications C11, and centralized auxiliary control-plane risks into auditable prerequisite tasks rather than presenting them as a live ecosystem.", "background_zh": "主网上线前需要将 AI、通信、资源市场和外部依赖与共识、治理、安全门禁协同。", "background_en": "Before mainnet, AI, communications, resource markets, and external dependencies must be coordinated with consensus, governance, and security gates.", "problem_zh": "资源发布、自动升级、AI 权限和中心化控制面可能引入供应链、可用性、治理与权限集中风险。", "problem_en": "Resource publication, auto-upgrade, AI authority, and centralized control planes may introduce supply-chain, availability, governance, and privilege-concentration risks.", "solution_zh": "以 C11、资源生态子任务、AI 宪法和降级/失效边界建立分阶段依赖、审查和候选绑定要求。", "solution_en": "C11, resource-ecosystem children, the AI constitution, and degradation/failure boundaries establish phased dependencies, reviews, and candidate-binding requirements.", "rejected_or_replaced_approach_zh": "拒绝默认信任中心化控制面、自动发布或 AI 自治结果；所有高风险动作必须受治理、验证和回滚边界约束。", "rejected_or_replaced_approach_en": "Default trust in centralized control planes, automatic publication, or AI autonomy is rejected; high-risk actions require governance, verification, and rollback boundaries.", "development_steps": [ "Definition AI Constitution and responsibility boundaries", "register C11 real environment gate", "Establish resource ecosystem C00-C15 dependency", "design control plane degradation and public network cache boundary" ], "outcome_zh": "形成 AI/资源/通信/控制面协同治理的任务化框架。", "outcome_en": "The work produced a task-based governance framework for AI, resources, communications, and control planes.", "limitations_zh": "资源生态多数子项尚未实施，C11 及公网/central-off 长时证据未闭合；No-Go 保持。", "limitations_en": "Most resource-ecosystem children remain unimplemented, and C11 plus public/central-off long-running evidence is not closed; No-Go remains.", "current_status": "dependency_managed_planning_and_partial_local_closures", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "mixed_local_closure_and_planning_records", "public_evidence_available": false, "evidence_level": "C/D", "affected_modules": [ "ai", "governance", "resource_ecosystem", "network", "control_plane", "communication" ], "related_events": [ "msg-detail-whitepaper-ai-entry-2026-05-06", "msg-detail-mainnet-status-review-2026-07-31-08-01" ], "public_visibility": "internal_only_pending_security_and_governance_review", "last_reviewed_at": "2026-08", "historical_context_zh": "该节点覆盖 AI 宪法、资源生态与控制面降级；控制面降级是为保持诚实边界，不代表相关能力已就绪。", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "本地收口与规划记录混合", "en": "Mixed local-closure and planning records" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E012-J", "display_title": "mainnet status review and No-Go restate", "id": "msg-detail-mainnet-status-review-2026-07-31-08-01", "parent_event_id": "msg-continued-engineering-2025-12-24", "phase_id": "phase_o_mainnet_readiness_review", "milestone_level": "major_detail_milestone", "date": "2026-07/2026-08", "date_precision": "range", "event_type": "status_review", "title_zh": "复核主网状态并重申 No-Go", "title_en": "Mainnet Status Reviewed and No-Go Reaffirmed", "summary_zh": "独立只读复核确认项目存在大量实现与本地验证，但最终候选、真实环境、正式签名和最终证据仍不足，维持 No-Go。", "summary_en": "An independent read-only review confirmed substantial implementation and local validation, but final candidate, real-environment, external-audit, production-signing, and final-evidence gaps keep No-Go in force.", "historical_context_en": "This node is a mainnet status review and a restatement of No-Go. No-Go was the formal status at that time and does not flip automatically later.", "narrative_zh": "复核纠正了“未实现功能数量”等同于最终证据缺口的误读，同时明确不能把 ClosedLocal、本地 PASS 或短时双公网联调升级为正式主网资格。", "narrative_en": "The review corrects the mistaken equation of final-evidence gaps with unimplemented functionality, while making clear that ClosedLocal, local PASS, or short dual-public-network exercises cannot be elevated to formal mainnet eligibility.", "background_zh": "开发量、候选闭合和生产证据处于不同层级，必须避免状态混写。", "background_en": "Development volume, candidate closure, and production evidence occupy different layers and must not be conflated.", "problem_zh": "历史排期和状态描述存在将本地闭合、最终证据、工期预测混为一谈的风险。", "problem_en": "Historical scheduling and status language risked conflating local closure, final evidence, and duration forecasts.", "solution_zh": "按 Implemented、ClosedLocal、CandidateBound、Production/FinalClosed 分层复核，并固定 final collector、签名和真实环境验证门禁。", "solution_en": "The review separates Implemented, ClosedLocal, CandidateBound, and Production/FinalClosed, retaining final collector, signing, and real-environment validation gates.", "rejected_or_replaced_approach_zh": "拒绝以代码规模、测试数量、局部公网成功或固定日期预测替代最终 Go/No-Go。", "rejected_or_replaced_approach_en": "Code size, test counts, local public-network success, or fixed-date estimates are rejected as substitutes for final Go/No-Go.", "development_steps": [ "Read-only check of the master index and task tree", "layered inventory of local and final states", "Identify the final candidate and production gaps", "restate No-Go and dependency order" ], "outcome_zh": "形成当前主网状态的审查基线和依赖化后续顺序。", "outcome_en": "The work established a reviewed baseline for current mainnet status and dependency-ordered next steps.", "limitations_zh": "该报告不是生产签名、候选验收或 Go 决议，且未重跑长时公网验证。", "limitations_en": "The report is not production signing, candidate acceptance, or a Go decision, and it did not rerun long-duration public-network validation.", "current_status": "No-Go", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "independent_read_only_status_review", "public_evidence_available": false, "evidence_level": "B", "affected_modules": [ "mainnet_readiness", "consensus", "economy", "ai", "network", "release" ], "related_events": [ "msg-detail-ai-constitution-resource-control-plane-2026-07", "msg-detail-development-governance-scheduling-2026-08-17" ], "public_visibility": "public_after_sanitization_and_formal_status_approval", "last_reviewed_at": "2026-08", "historical_context_zh": "该节点是主网状态复核与 No-Go 重申；No-Go 是当时的正式状态，不构成后续自动翻转。", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "独立只读状态复核", "en": "Independent read-only status review" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E012-K", "display_title": "Development governance and model tiered scheduling review", "id": "msg-detail-development-governance-scheduling-2026-08-17", "parent_event_id": "msg-continued-engineering-2025-12-24", "phase_id": "phase_p_development_governance_scheduling", "milestone_level": "detail_milestone", "date": "2026-08", "date_precision": "month", "event_type": "status_review", "title_zh": "复核开发治理与模型分级调度", "title_en": "Development Governance and Model-Tier Scheduling Reviewed", "summary_zh": "复核确认高风险共识、经济、密码学和最终集成应显式采用更高推理等级，普通原子开发与检索采用分级调度；这不改变主网 No-Go。", "summary_en": "The review confirms that high-risk consensus, economics, cryptography, and final integration should explicitly use higher reasoning tiers, while ordinary atomic work and retrieval use tiered scheduling; this does not change mainnet No-Go.", "historical_context_en": "This node reviews development governance and model-tier scheduling. Governance scheduling is a development-process discipline; it does not change product capability status.", "narrative_zh": "该事件关注开发过程治理，而非链功能发布。它区分模型选择、任务分派和真实验收，并明确任何模型能力均不能替代真实公网节点验证、生产签名和官方上线决定。", "narrative_en": "This event concerns development-process governance rather than chain-feature release. It distinguishes model selection, task delegation, and real acceptance, making clear that no model capability replaces real public-network node validation, production signing, or the official launch decision.", "background_zh": "高风险任务需要明确的审查与调度策略，普通开发不应被历史流程工具无故阻塞。", "background_en": "High-risk work needs explicit review and scheduling strategy, while ordinary development should not be unnecessarily blocked by historical process tools.", "problem_zh": "默认模型配置与风险任务的推理需求不一定一致，且容易误解自动委派为自动跨模型选型。", "problem_en": "Default model configuration may not match the reasoning needs of high-risk tasks, and automatic delegation can be mistaken for automatic cross-model selection.", "solution_zh": "采用显式模型分级、独立 readback 验证和高风险任务的独立审查要求。", "solution_en": "Explicit model tiering, independent readback verification, and independent review requirements for high-risk work were adopted.", "rejected_or_replaced_approach_zh": "拒绝把模型配置、AI 生成内容或局部测试当作官方上线决定或生产签名替代品。", "rejected_or_replaced_approach_en": "Model configuration, AI-generated content, or local tests are rejected as substitutes for the official mainnet launch decision or production signing.", "development_steps": [ "Read the current scheduling configuration", "Distinguish automatic delegation from automatic model selection", "Define high-risk and routine task tiers", "retain provider readback and No-Go Boundary" ], "outcome_zh": "形成可追溯的开发治理调度建议，并与主网门禁保持分离。", "outcome_en": "The work produced traceable development-governance scheduling guidance separated from mainnet gates.", "limitations_zh": "该事件不修改链状态、不证明任何功能生产可用，也不构成模型提供方实际能力的永久保证。", "limitations_en": "This event does not modify chain state, prove any feature production-ready, or guarantee a provider's actual capability permanently.", "current_status": "development_governance_record", "implementation_status": "Partial", "production_status": "not_production_verified", "evidence_status": "local_configuration_and_policy_review", "public_evidence_available": false, "evidence_level": "C/D", "affected_modules": [ "development_governance", "review", "testing", "release_governance" ], "related_events": [ "msg-detail-mainnet-status-review-2026-07-31-08-01", "msg-public-knowledge-surface-maintenance-2026-08-16" ], "public_visibility": "internal_only", "last_reviewed_at": "2026-08", "historical_context_zh": "该节点复核开发治理与模型分级调度；治理调度属于开发过程纪律，不代表产品能力状态变化。", "public_status_labels": { "implementation_status": { "zh": "部分实现", "en": "Partially implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "本地配置与策略复核", "en": "Local configuration and policy review" }, "public_evidence_available": { "zh": "否", "en": "No" } } }, { "event_code": "E013", "display_title": "whitepaper and public machine entry maintenance", "id": "msg-public-knowledge-surface-maintenance-2026-08-16", "date": "2026-08", "date_precision": "range", "event_type": "documentation", "title_zh": "白皮书公开机器入口和脱敏发布链路完成阶段维护", "title_en": "Whitepaper Machine Entry and Sanitized Publication Pipeline Maintenance", "summary_zh": "白皮书公开基地址、机器入口 URL、JSON/JSONL 输出、脱敏规则、结构审计和线上可访问性完成阶段维护。", "summary_en": "The whitepaper public base URL, machine-entry URLs, JSON/JSONL outputs, sanitization rules, structural audits, and online accessibility received coordinated maintenance.", "limitations_zh": "维护事件只覆盖公开入口与机器输出，不改变任何模块的实现状态或生产状态；线上可访问性通过也不等于能力已通过生产验证。", "limitations_en": "A maintenance event covers only public entry points and machine outputs; it does not change any module's implementation or production status, and passing an online availability check is not the same as passing production verification.", "implementation_status": "Implemented", "production_status": "not_production_verified", "evidence_status": "public_surface_smoke_tested", "public_evidence_available": true, "evidence_level": "A/B", "affected_modules": [ "whitepaper", "machine_entry", "documentation" ], "public_visibility": "public", "last_reviewed_at": "2026-08", "review_note": "public releases may only expose stable public entries and generic pipeline names, not internal scripts, paths, credentials or work logs.", "historical_context_zh": "这是官网和白皮书维护事件，不代表 MSG 公链主网生产能力已经完成。", "historical_context_en": "this is a website and whitepaper maintenance event, and does not represent MSG public chain mainnet production capability has been completed.", "public_status_labels": { "implementation_status": { "zh": "已实现", "en": "Implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "公开界面冒烟验证", "en": "Public-surface smoke tested" }, "public_evidence_available": { "zh": "是", "en": "Yes" } } }, { "event_code": "E014", "display_title": "registration of scheduling for eight product branches and V3 economic model local closure", "id": "msg-eight-branch-registry-economic-v3-local-complete-2026-08-09", "date": "2026-08", "date_precision": "range", "event_type": "engineering_milestone", "title_zh": "八大产品分支调度注册与 V3 经济模型本地收口", "title_en": "Eight-Branch Scheduling Registry and Economic Model V3 Local Closeout", "summary_zh": "主网上线前八大产品分支的调度顺序完成注册（经济模型、去中心化资源市场、去中心化通信中心、L1 共识与候选完整性、人机平权与 AI 自治、后量子密码、L1 运维与网络韧性、发布与上线门禁）；经济模型 V3 以\"经济秒、双池累加、资格审计、处罚闭环、金库\"为核心完成本地收口：Go 参考实现与 emission_schedule_v3 合约测试通过，七项验收 manifest 全部达成。", "summary_en": "The scheduling order of the eight pre-mainnet product branches was registered: economic model, decentralized resource marketplace, decentralized communication hub, L1 consensus and candidate integrity, human-AI parity and AI autonomy, post-quantum cryptography, L1 operations and network resilience, and release and launch gates. Economic Model V3, built on economic-seconds, dual-pool accumulators, eligibility audit, penalty loop and treasury, completed its local closeout with the Go reference implementation and emission_schedule_v3 contract tests passing and all seven acceptance manifests met.", "limitations_zh": "本地收口只覆盖参考实现与本地测试；创世部署、主网激活与 V3 主网前门禁均未完成，需按治理排期单独判定。", "limitations_en": "Local closure covers only the reference implementation and local tests; genesis deployment, mainnet activation and the V3 pre-launch gates are all unfinished and must be judged separately under the governance schedule.", "implementation_status": "Implemented", "production_status": "not_production_verified", "evidence_status": "local_tests_and_manifests", "public_evidence_available": true, "evidence_level": "A/B", "affected_modules": [ "economics", "consensus", "documentation" ], "public_visibility": "public", "last_reviewed_at": "2026-09", "review_note": "public statements do not include internal task IDs or authorization document details.", "historical_context_zh": "本地收口不等于创世部署或主网激活；V3 相关的主网前门禁仍按治理排期推进。", "historical_context_en": "local closure does not equal genesis deployment or mainnet activation; V3 related pre-mainnet gates still proceed according to the governance schedule.", "public_status_labels": { "implementation_status": { "zh": "已实现", "en": "Implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "local_tests_and_manifests", "en": "local_tests_and_manifests" }, "public_evidence_available": { "zh": "是", "en": "Yes" } } }, { "event_code": "E015", "display_title": "Decentralized resource market completes local closure", "id": "msg-resource-market-local-closeout-2026-08-26", "date": "2026-08/2026-09", "date_precision": "range", "event_type": "engineering_milestone", "title_zh": "去中心化资源市场完成本地收口", "title_en": "Decentralized Resource Marketplace Completes Local Closeout", "summary_zh": "资源市场首版范围固定为 node_release（节点资源包）与 skill_package（技能资源包）两类；当前公开产品范围已扩展为三类，新增 file_bundle（任意文件包，仅设计态：设计层冻结，未实现、未部署、未启用，首发启用范围待定）。相关合约、准入与分发链路在本地完成验证收口，候选绑定与发布包链路具备可回读证据。主网上线后，节点软件迭代将经该市场以去中心化方式发布，各节点运营者自主决定是否升级，只要不违反公链共识规则。", "summary_en": "The first version of the resource marketplace fixed its scope to node_release and skill_package packages; the published product scope has since been extended to three kinds by adding file_bundle (arbitrary file bundles), which is design-only: frozen at the design level, not implemented, not deployed, not enabled, with first-release enablement scope still undecided. Contracts, admission and distribution completed local verification closeout with a candidate binding and a reproducible release pipeline. After mainnet launch, node software iterations will be published through this marketplace in a decentralized way, with each node operator deciding autonomously whether to upgrade, provided consensus rules are respected.", "limitations_zh": "本地收口只覆盖合约、准入与分发链路的本地验证；第三类 file_bundle 仅有设计层冻结，未实现、未部署、未启用，不构成任何能力或发布证据；市场尚未上线运行，候选绑定与发布包证据也不能替代主网运行证据。", "limitations_en": "Local closure covers only local verification of the contract, admission and distribution paths; the third kind, file_bundle, is design-frozen only and is not implemented, deployed or enabled, so it is not capability or release evidence; the market is not live, and candidate binding or release-package evidence cannot replace mainnet runtime evidence.", "implementation_status": "Implemented", "production_status": "not_production_verified", "evidence_status": "local_tests_and_manifests", "public_evidence_available": true, "evidence_level": "A/B", "affected_modules": [ "resource_market", "contracts", "documentation" ], "public_visibility": "public", "last_reviewed_at": "2026-09", "review_note": "public statements do not include internal task IDs or authorization document details.", "historical_context_zh": "本地收口不代表市场已上线运行；主网前门禁与分支评价仍按治理排期推进。", "historical_context_en": "local closure does not mean the market is live; pre-mainnet gates and branch evaluation still advance per governance schedule.", "public_status_labels": { "implementation_status": { "zh": "已实现", "en": "Implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "local_tests_and_manifests", "en": "local_tests_and_manifests" }, "public_evidence_available": { "zh": "是", "en": "Yes" } } }, { "event_code": "E016", "display_title": "Decentralized communication center enters the feature closure stage", "id": "msg-comm-hub-functional-closeout-2026-09-16", "date": "2026-09", "date_precision": "range", "event_type": "engineering_milestone", "title_zh": "去中心化通信中心进入功能收口阶段", "title_en": "Decentralized Communication Hub Reaches Functional Closeout", "summary_zh": "通信中心按七十六个验收切片推进：DID 与设备会话、端到端加密、双向确认、显式离线失败、房间与文件传输、relay/NAT 穿越与多平台确定性构建相继完成本地验收；发布物、签名、引导清单、公开矩阵、回滚、故障转移与总收口七个验收契约面全部关闭；时延测量确立正式采样口径（不少于二百八十八个样本，避免小样本结构性偏差）；真实公网与 NAT 环境的长时验收按治理排期依次推进。", "summary_en": "The communication hub advanced through seventy-six acceptance slices covering DID device sessions, end-to-end encryption, bidirectional acknowledgement, explicit offline failure, rooms and file transfer, relay/NAT traversal and deterministic multi-platform builds. Seven acceptance contract surfaces (artifacts, signing, bootstrap inventory, public matrix, rollback, failover and aggregate closure) were all closed locally, and a formal latency-sampling methodology of at least 288 samples was adopted to avoid small-sample bias. Long-duration validation on real public and NAT environments proceeds per governance schedule.", "limitations_zh": "功能收口只覆盖本地验收与契约面关闭；长时真实环境验收尚未执行，时延口径也只是测量规则而非已完成的真实环境结论。", "limitations_en": "Functional closure covers only local acceptance and contract-surface closure; long-run real-environment acceptance has not been executed, and the latency rule is a measurement convention rather than a finished real-environment result.", "implementation_status": "Implemented", "production_status": "not_production_verified", "evidence_status": "local_tests_and_manifests", "public_evidence_available": true, "evidence_level": "A/B", "affected_modules": [ "communications", "p2p", "documentation" ], "public_visibility": "public", "last_reviewed_at": "2026-09", "review_note": "public statements do not include internal task IDs or authorization document details.", "historical_context_zh": "功能收口不等于生产验证完成；长时真实环境验收尚未执行。", "historical_context_en": "Feature closure does not equal completed production verification; long-duration real-environment acceptance has not yet been executed.", "public_status_labels": { "implementation_status": { "zh": "已实现", "en": "Implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "local_tests_and_manifests", "en": "local_tests_and_manifests" }, "public_evidence_available": { "zh": "是", "en": "Yes" } } }, { "event_code": "E017", "display_title": "Official website and whitepaper system publish a unified launch position and AI integration path", "id": "msg-public-launch-narrative-release-2026-09-16", "date": "2026-09", "date_precision": "month", "event_type": "documentation", "title_zh": "官网与白皮书系统发布统一上线口径与 AI 接入路径", "title_en": "Unified Launch Narrative and AI Access Path Released Across Site and Whitepaper", "summary_zh": "官网与白皮书系统完成统一功能口径发布：能力只以功能状态（规划态、实现中、已实现（本地））与主网状态（未上线、已上线，官方公告为唯一翻转点）表达；AI 机器入口新增上线模型说明与六步 dApp 开发路径；完整免责声明页上线，说明节点升级经去中心化资源市场自主进行及各节点运营者自担风险；白皮书导航实现全部模块页直达覆盖，并新增发展史与 AI 入口专用通道；两次生产部署完成线上回查验证。", "summary_en": "The site and whitepaper released a unified functional narrative: capabilities are expressed only as functional status (planned, in progress, implemented locally) and mainnet status (not launched or launched), with the official announcement as the single flip point; the AI machine entry gained a launch-model note and a six-step dApp development path; a full disclaimer page went live covering decentralized node upgrades via the resource marketplace and operator-borne risk; whitepaper navigation now reaches every module page with dedicated entry channels for the development history and the AI entry; two production deployments passed post-release verification.", "limitations_zh": "该事件只改变公开信息面，不改变任何链上能力状态；官网与白皮书的能力状态仍以各模块证据为准。", "limitations_en": "This event only changes the public information surface; it does not change any on-chain capability status, which still follows each module's evidence.", "implementation_status": "Implemented", "production_status": "not_production_verified", "evidence_status": "public_surface_smoke_tested", "public_evidence_available": true, "evidence_level": "A/B", "affected_modules": [ "whitepaper", "machine_entry", "official_site", "documentation" ], "public_visibility": "public", "last_reviewed_at": "2026-09", "review_note": "public releases do not expose internal scripts, paths, credentials or work logs.", "historical_context_zh": "本事件是公开信息面发布，不构成上线公告；主网状态以官方公告为唯一翻转点。", "historical_context_en": "This event is a public information surface release and does not constitute a launch announcement; the mainnet state uses the official announcement as the sole flip point.", "public_status_labels": { "implementation_status": { "zh": "已实现", "en": "Implemented" }, "production_status": { "zh": "未通过生产验证", "en": "Not production-verified" }, "evidence_status": { "zh": "公开界面冒烟验证", "en": "Public-surface smoke tested" }, "public_evidence_available": { "zh": "是", "en": "Yes" } } } ] }