Time Library 2026.7.18

优化了一些问题并改进稳定性。

Time Library 2026.7.11

优化了一些问题并改进稳定性。

Time Library 2026.7.7.2

Time Library 2026.7.7.2

2026.7.7.2 is a maintenance update over 2026.7.7.1. It optimizes local console
interaction reliability, settings loading behavior, and release package
consistency while keeping existing compatibility behavior.

What Changed

• Improved local task, note, and Reading Room project interactions.
• Optimized settings page loading and model preference controls.
• Kept installer defaults and compatibility behavior aligned with Time Library.

中文

2026.7.7.2 是 2026.7.7.1 之上的维护更新，优化本地控制台交互可靠性、
设置页加载体验和发布包一致性，同时保持已有兼容行为。

本版本包含

• 优化本地事项、线索和阅读室项目交互。
• 优化设置页加载和模型偏好控件。
• 保持安装器默认值与兼容行为和 Time Library 发布一致。

Time Library 2026.7.7.1

Time Library 2026.7.7.1

2026.7.7.1 is a maintenance update over 2026.7.7. It optimizes a few local
console and installer-flow details while keeping existing compatibility
behavior.

What Changed

• Optimized local console interactions and empty states.
• Improved Reading Room and Whiteboard local draft behavior.
• Kept installer defaults and compatibility behavior aligned with Time Library.

中文

2026.7.7.1 是 2026.7.7 之上的维护更新，优化了一些本地控制台和安装流程体验，
同时保持已有兼容行为。

本版本包含

• 优化本地控制台交互和空状态。
• 优化阅读室和白板的本地草稿体验。
• 保持安装器默认值与兼容行为和 Time Library 发布一致。

Time Library 2026.7.7

Time Library 2026.7.7

2026.7.7 is the rename-and-release-prep cut for Time Library. It moves the
public repository, release package, installer defaults, and user-facing install
paths to time-library while preserving legacy memcore-cloud roots as
migration and uninstall fallbacks.

What Changed

• One-command installers now download strmforge/time-library release assets
  named time-library-<version>.zip.
• Fresh installs default to Time Library paths:
  • macOS: ~/Library/Application Support/time-library
  • Linux: ~/.local/share/time-library
  • Windows: %LOCALAPPDATA%\time-library
• Existing memcore-cloud installs are copied forward by full installers when
  the new default path is empty, so user data is preserved.
• Windows, macOS, Linux, tray, and menu bar helpers now use the new public
  install path by default.
• Public docs and smoke commands now point at time-library paths and
  TIME_LIBRARY_* environment variables.
• Release packages are built as time-library-<version>.zip.
• The bge-m3 switch is wired through the saved recall preference path.
• Hermes autonomous learning is value-gated and budgeted: the background
  controller can wake on a schedule, but it only spends when new raw evidence
  makes a run due.

Compatibility

• Legacy MEMCORE_* environment variables still work as fallback inputs.
• Legacy install roots such as ~/Library/Application Support/memcore-cloud
  and %LOCALAPPDATA%\memcore-cloud remain migration sources and uninstall
  fallback targets.
• Internal service labels and watcher script names that still contain
  memcore are retained for compatibility in this cut.

Boundaries

• This release changes source/package/install defaults. It does not forcibly
  move a currently running local macOS installation at runtime.
• Production experience auto-adoption remains disabled by default.
• The rename does not claim cross-machine synchronization is fully proven.

中文

2026.7.7 是 Time Library 的公开版本，也是正名与发布准备版本：公开仓库、发布包、安装器默认值
和用户可见安装路径都切到 time-library，同时保留旧 memcore-cloud 目录作为迁移
和卸载兜底，避免老用户数据丢失。

本版本包含

• 一键安装器默认下载 strmforge/time-library 的 release 资产，包名为
  time-library-<version>.zip。
• 新安装默认路径改为：
  • macOS: ~/Library/Application Support/time-library
  • Linux: ~/.local/share/time-library
  • Windows: %LOCALAPPDATA%\time-library
• 如果新默认路径为空但旧 memcore-cloud 安装存在，完整安装器会把用户数据复制到
  新路径。
• Windows、macOS、Linux、托盘和菜单栏工具默认都使用新的公开安装路径。
• 公开文档和 smoke 命令改用 time-library 路径与 TIME_LIBRARY_* 环境变量。
• 发布包改为 time-library-<version>.zip。
• bge-m3 开关已接入保存后的默认召回偏好。
• Hermes 自主学习改为价值门控和预算上限：后台可以按计划醒来，但只有新 raw 证据
  到期时才花费运行。

兼容边界

• 旧 MEMCORE_* 环境变量仍作为 fallback 可用。
• 旧安装目录仍作为迁移源和卸载 fallback 保留。
• 仍带 memcore 的内部服务 label 和 watcher 文件名本刀先保留，避免破坏现有运行态。
• 本版本不强搬当前正在运行的本机 macOS installed runtime。

Memcore Cloud 2026.6.20.2

Memcore Cloud 2026.6.20.2

2026.6.20.2 is a small safety-followup patch. It keeps the passive-first
OpenClaw/Zhiyi behavior and fixes two release hygiene problems:
runtime surfaces now report the real package version from VERSION, and
Windows scripts no longer collide with PowerShell's read-only $PID variable.

What Changed

• Runtime version reporting now uses a single source:
  • VERSION
  • src/memcore_version.py
• Raw gateway health, MCP/server metadata, preflight surfaces, console APIs, and
  the local console UI no longer report stale 2026.6.20 strings after a patch
  install.
• Windows guardian and uninstall scripts avoid assigning to PowerShell's
  read-only $PID automatic variable.
• Release gate now blocks runtime version literals in user-visible/reporting
  surfaces and blocks future PowerShell $PID assignment regressions.
• One-command installers now default to 2026.6.20.2.

Boundaries

• This release keeps the 2026.6.20 passive-first delivery behavior:
  • zhiyi_direct=false
  • zhiyi_inject=false
  • openclaw_rpc=false
  • passthrough=true
• This release does not publish benchmark scores or leaderboard claims.
• Contract identifiers such as agent_work_preflight.v2026.6.20 remain protocol
  ids and are not runtime package-version strings.

中文

2026.6.20.2 是一个小型安全跟进补丁。它保留 OpenClaw / 知意 passive-first
的止血结果，同时修掉两个发布卫生问题：运行态版本面统一从
VERSION 读取真实包版本，Windows 脚本不再撞 PowerShell 只读 $PID 变量。

本版本包含

• 运行态版本上报改成单一来源:
  • VERSION
  • src/memcore_version.py
• raw gateway health、MCP/server metadata、preflight、console API 和本地控制台
  UI 不再在补丁安装后继续显示旧的 2026.6.20。
• Windows guardian 和卸载脚本不再给 PowerShell 只读 $PID 自动变量赋值。
• release gate 增加机械门，阻止运行态版本字面量回到用户可见/健康上报面，也阻止
  PowerShell $PID 赋值类回归。
• 一键安装脚本默认版本更新到 2026.6.20.2。

边界

• 本版本保留 2026.6.20 的 passive-first 默认:
  • zhiyi_direct=false
  • zhiyi_inject=false
  • openclaw_rpc=false
  • passthrough=true
• 本公开版本不发布 benchmark 分数，也不声明任何公开榜单成绩。
• agent_work_preflight.v2026.6.20 这类 contract id 是协议版本，不是运行包版本。

Memcore Cloud 2026.6.20.1

Memcore Cloud 2026.6.20.1

2026.6.20.1 is a public-surface cleanup patch for the 2026.6.20 safety release.
It keeps the passive-first OpenClaw/Zhiyi defaults and removes internal evaluation tooling from the public product tree.

What Changed

• Keeps 2026.6.20 passive-first delivery:
  • zhiyi_direct=false
  • zhiyi_inject=false
  • openclaw_rpc=false
  • passthrough=true
• Removes internal benchmark, judge, model-matrix, and miss-report source files
  from the public product package.
• Keeps the product runtime dependencies required by dialog entry:
  • src/evidence_bound_model.py
  • src/memory_authority_policy.py
• Adds release-gate checks so product src/ cannot import eval modules and the
  public release source cannot carry those eval entry points again.
• Updates public README wording to focus on local diagnostics and health checks
  instead of exposing internal scoring machinery.

Boundaries

• This release does not change the 2026.6.20 passive-first runtime behavior.
• This release does not publish benchmark scores or leaderboard claims.
• Internal benchmark work, if needed, should run from a separate maintainer
  workspace instead of the public product package.

中文

2026.6.20.1 是 2026.6.20 安全公开版本之后的公开面清理补丁。它保留普通聊天
passive-first 的止血结果，同时把内部评测、裁判、模型矩阵和错例报告源码从
公开产品树里移出。

本版本包含

• 保留 2026.6.20 的 passive-first 默认:
  • zhiyi_direct=false
  • zhiyi_inject=false
  • openclaw_rpc=false
  • passthrough=true
• 从公开产品包移除内部 benchmark / judge / model-matrix / miss-report 入口。
• 保留 9860 dialog-entry 必需的产品依赖:
  • src/evidence_bound_model.py
  • src/memory_authority_policy.py
• release gate 增加机械门，防止产品 src/ 再 import eval 模块，也防止公开
  release source 再夹带这些评测入口。
• README 改成普通用户可理解的本地诊断和健康检查口径，不再暴露内部跑分机器。

边界

• 本版本不改变 2026.6.20 的 passive-first 运行行为。
• 本版本不发布 benchmark 分数，也不声明任何公开榜单成绩。
• 如需继续内部评测，应在维护者自己的独立工作区运行，不进入公开产品包。

Memcore Cloud 2026.6.20

Memcore Cloud 2026.6.20

2026.6.20 is a safety-focused public release for Memcore Cloud. It lowers the
risk of local agent memory overreach, especially OpenClaw-style interception,
while keeping recall source-backed and local-first.

Memcore Cloud remains a local AI memory library: original records stay on the
user's machine, recall is source-backed, and reusable experience must keep a
traceable evidence trail.

What This Release Contains

• Local AI memory library: original records remain the local source of
  truth, while source refs, library ids, and receipts make recall auditable.
• Safer local-agent authority: Zhiyi is a memory and evidence layer, not a
  default replacement for the host agent. OpenClaw-style interception defaults
  to off; direct Zhiyi answers and platform actions require explicit entry or
  authorization.
• Low-resource defaults: watchers default to a light profile, a 5-second
  interval, and narrow source selection instead of full-source 250ms scans.
• More honest local tool display: public docs may describe supported AI
  tools, but the local console should emphasize tools actually detected on the
  current machine.
• Pre-work checks: work_preflight / preflight doctor can run as a quick
  daily smoke path, with full diagnostics reserved for explicit troubleshooting.
• Source-backed recall: recall remains compact by default, with source refs
  first and raw excerpts only when explicitly requested.
• Evidence-bound model path: MiniMax, DeepSeek, and OpenAI-compatible
  models can be used for evidence-bound answer refinement and candidate
  checking without treating models as benchmark-only toys.
• Fast model diagnostics: the model matrix can compare baseline top+pack
  two-call behavior with a single-call fast audit, including call count,
  latency, CPU/RSS, decision drift, and risk flags.
• Benchmark diagnostics, not leaderboard claims: public docs now separate
  no-key retrieval diagnostics, internal answer judging, and official
  evaluator paths so scoring work does not masquerade as a published benchmark.
• Evaluation guardrails: daily use, targeted regression, and offline
  benchmark entry points are separated so scoring work does not overload a
  workstation or silently become the daily path.

中文

2026.6.20 是一次以安全降险为核心的公开版本。它降低本机 agent 记忆层越权的
风险，尤其是 OpenClaw 这类拦截入口默认抢答的问题，同时继续保持本机优先和
可回源召回。

本版本包含

• 更安全的本机 agent 权限边界：知意是记忆和证据层，不默认替代宿主
  agent。OpenClaw 这类拦截入口默认关闭；直接回答和平台动作必须有显式入口
  或授权。
• 低资源默认：watcher 默认 light profile、5 秒间隔、窄来源选择，不再默认
  全来源 250ms 扫描。
• 更诚实的本机工具展示：公开文档可以说明支持哪些 AI 工具，但本机控制台应
  优先展示当前机器真实检测到的工具。
• 开工前检查：work_preflight / preflight doctor 支持日常快速 smoke，
  full 体检保留给显式排障。
• 可回源召回：默认返回紧凑 source refs；只有明确需要原文证据时才取 raw
  excerpt。
• 证据绑定模型路径：MiniMax、DeepSeek 和 OpenAI-compatible 模型可以用于
  证据绑定回答、候选判断和经验精炼，不再只作为 benchmark 工具。
• fast 模型诊断：模型矩阵可比较 top+pack 双调用 baseline 和单调用 fast
  audit，记录调用数、耗时、CPU/RSS、逐题漂移和风险标记。
• 评分诊断不冒充榜单：公开文档已区分免费检索诊断、内部答案判分和官方
  evaluator 路径，避免把本地诊断说成公开 benchmark 成绩。
• 评测护栏：日常入口、定向回归和离线 benchmark 分开，避免跑分任务拖垮
  工作机，也避免把评分路径误当成日常路径。

Boundaries

• Local benchmark and model-matrix reports are diagnostics, not official
  leaderboard scores.
• Benchmark run outputs, caches, and local R730XD pressure-test artifacts are
  not part of the public release payload.
• Direct Zhiyi answers and platform actions remain explicit-entry or
  explicit-authorization paths; ordinary OpenClaw chat is passive by default.

Memcore Cloud 2026.6.16

Memcore Cloud 2026.6.16

Memcore Cloud 2026.6.16 focuses on making the local AI memory library easier to
connect, inspect, and trust. It fixes the local AI "finished the chat, lost the
context" problem by keeping original records, preferences, project boundaries,
proven work paths, and borrowing receipts on the user's own machine.

Highlights

• Local AI memory library: original records remain the archive, library ids
  make memories findable, and usage receipts show what an agent borrowed before
  it answered.
• Source-backed recall: recall can return compact source refs, rank reasons,
  and bounded original excerpts when explicitly requested.
• Pre-work context checks: before coding, installing, syncing, or
  troubleshooting, an agent can check whether the work looks already built,
  miswired, missing diagnostics, or truly missing.
• Zhiyi and Xingce stay distinct: Zhiyi keeps preferences, corrections,
  habits, and boundaries; Xingce keeps repair paths, validation steps, and work
  methods.
• Experience reaches local agents: skill-, instruction-, and MCP-capable
  local agents can read the same Xingce guidance before work instead of keeping
  separate private experience stores.
• Traceable experience evolution: successful fixes, mistakes, and user
  corrections can become candidates. Source-backed candidates with original
  evidence and acceptance checks can be adopted, upgraded, rejected, or rolled
  back with receipts.
• Record Doctor: a safe read-only check shows whether source records, raw
  mirrors, the canonical index, and memory/experience links are guarded before
  real recall is tested.
• Quieter first response: capability check remains read-only and no-recall;
  real memory is only retrieved when an agent calls recall.
• Installer entry points: macOS, Linux, and Windows installers use the
  2026.6.16 release tag and keep local data such as memory/, raw/, zhiyi/,
  and config/ separate from app files.

中文

Memcore Cloud 2026.6.16 的重点，是让“忆凡尘这座本机 AI 记忆图书馆”更容易接入、检查和信任。它解决本机 AI “聊完就散、换窗就忘、做过还重做”的硬伤：原始记录仍然是最高事实；召回要能回源；有用的工作经验必须经过证据和验收，才能变成下一次可复用的行策。

主要更新

• 本机 AI 记忆图书馆：原始记录是馆藏原件，馆藏号负责定位，借阅记录说明 agent 回答前用了哪些记忆。
• 可回源召回：召回可以返回精简来源线索、命中理由，并在明确需要时给出有界原文摘录。
• 开工前上下文检查：写代码、安装、同步、排障前，agent 可以先判断这件事更像已经做过、接线错了、缺诊断，还是确实缺功能。
• 知意和行策分开：知意保存偏好、纠正、习惯和边界；行策保存修复路径、验证步骤和工作方法。
• 经验可以接给本机 agent：支持 skill、自定义指令或 MCP 的本机 agent，都可以在动手前读取同一套行策经验，而不是各自攒一套私有经验。
• 经验可追踪进化：做成、踩坑、纠错都可以先成为候选；带得回来源、原文和验收条件的候选，才能被采纳、升级、拒绝或回滚，并留下回执。
• 记录医生：真实召回前，可以先用只读自检确认源记录、raw 镜像、canonical index 和记忆/经验链路是否守住。
• 更安全的第一次测试：capability check 仍然只读、无真实召回；只有 agent 明确调用 recall，才读取真实记忆。
• 安装入口对齐：macOS、Linux、Windows 安装器使用 2026.6.16 release tag，并把 memory/、raw/、zhiyi/、config/ 等本地数据和软件文件分开。

Boundaries

• Summaries help navigation, but they do not replace original records.
• Experience is not a skill marketplace and Xingce is not a callable function
  library.
• Experience evolves, but it stays source-backed, reviewable, and reversible.
• Local data stays on the user's machine by default.

Memcore Cloud 2026.6.15

Memcore Cloud 2026.6.15

Memcore Cloud 2026.6.15 is a release for the Tiandao-governed memory and
experience system. It keeps the 2026.6.14 cleanup base, then makes
the next codebase easier to audit by turning experience adoption into a
receipt-backed, source-traceable dry-run flow.

Status: published GitHub Release.

English

Highlights

• Tiandao-governed module split: the former giant console, platform guard,
  Claude Desktop, raw gateway, Hermes liveness, and record-guardian surfaces
  have been split by ownership boundary rather than arbitrary line count.
• Record origin remains first: canonical indexing, raw evidence excerpts,
  and raw backfill now live in dedicated record modules, but raw source records
  remain the highest authority.
• Console stays an entrypoint: p6_console.py remains the human console and
  compatibility wrapper, while UI, action gates, status diagnostics, OpenClaw
  inlet, Zhiyi runtime, and experience governance live in smaller modules.
• Platform Guard is clearer: catalog, model identity, package inventory,
  and surface scanning are separated from authorized platform-config apply.
• Claude Desktop capture boundary is clearer: Claude Desktop raw ingest
  logic is isolated from the connector entrypoint, and local relay references
  remain development/compatibility metadata rather than public requirements.
• Runtime version alignment: the release reports 2026.6.15 in the version
  file, gateway health, active-memory routing, preflight metadata, local console
  text, platform storage contract, and packaged Zhiyi skill.
• Install readiness waits for large local libraries: macOS, Linux, and
  Windows installers now wait for slow-starting local services instead of
  failing after a single early smoke probe.
• Experience validation receipts: Xingce can now emit a dry-run validation
  receipt schema that records pass/fail status, evidence links, and adoption
  blockers without mutating the experience library.
• Receipt-backed apply gate: adoption checks prefer validation receipts when
  present, while preserving compatibility with the older validation-report
  fallback path.
• Apply package preview: a ready apply package can be built as a local
  dry-run artifact. package_status=ready means ready for a future authorized
  apply, not already adopted.
• Experience flow overview: the console can now show a compact record chain
  across experience evolution, review action, validation report, validation
  receipt, review queue, apply gate, apply receipt schema, and apply package.
• Release validation: 2026.6.15 was tested in this
  run on macOS and two Windows hosts. Full local tests passed, the working-tree
  release gate passed before commit, the committed-HEAD release gate passed
  before publication, Windows native smoke passed, and the record-chain audit
  found no lost source or lost raw. Claude Desktop bridge presence was verified
  on detected Windows Claude config homes; one package-scoped Windows config
  is still malformed JSON and remains a local follow-up.
• Record doctor and record chain: a new read-only doctor/demo check shows
  whether source records, raw mirrors, the canonical index, and memory/experience
  links are guarded. The timeline/replay surface is framed as a record chain,
  not a memory wall.
• Recall output is quieter by default: Zhiyi recall now returns compact
  source refs, counts, receipts, and rank reasons by default. Bounded raw
  excerpts remain available only when explicitly requested with a raw response
  budget.
• Runtime bootstrap starts the foundation cleanup: new and migrated command
  entry points can share one repository/import bootstrap instead of adding more
  ad-hoc path setup snippets.
• Double-click install entries: release zips now include a macOS
  Memcore Cloud Installer.command and a Windows Memcore Cloud Installer.cmd;
  the Windows entry opens a folder picker before running the same installer.
• Public wording tightened: public copy now leads with local continuity,
  source-backed records, recall, and reusable work paths, while the detailed
  integration capability coverage stays maintainer test material rather than
  user-facing product text.
• Release checks remain guarded: public wording scans, private local
  agent-rule file exclusion, release artifact checks, internal direction audit,
  and full tests passed before publication.

Boundaries

• Release assets are built from committed HEAD after the release gate passes.
• Local maintainer-only files and private local agent-rule files remain ignored
  and are not part of public release artifacts.
• Capability check remains read-only and no-recall.
• LAN reachability for OpenClaw and Hermes remains supported when explicitly
  configured.
• Multi-machine validation for 2026.6.15 was filled from the 2026-06-15
  current run only; older 2026.6.14 results were not reused as proof.

中文

主要更新

• 天道管辖下拆分模块：原先过大的 console、Platform Guard、Claude Desktop、raw gateway、Hermes liveness 和记录守护相关文件，按真实管辖边界拆分，而不是按行数硬切。
• 记录起源仍然第一：canonical index、raw evidence excerpt、raw backfill 进入独立记录模块，但 raw source record 仍然是最高事实。
• 控制台仍是入口：p6_console.py 保留为人类控制台入口和兼容 wrapper；UI、动作安全门、状态诊断、OpenClaw inlet、知意 runtime、体验治理拆到更小模块。
• Platform Guard 更清楚：catalog、model identity、package inventory、surface scan 与授权 platform config apply 分开。
• Claude Desktop 采集边界更清楚：Claude Desktop raw ingest 从 connector 入口中拆出；本地中转痕迹只保留为开发/兼容元数据，不写成公开依赖。
• 运行版本对齐：发布版在 VERSION、gateway health、active memory routing、preflight metadata、本地控制台文本、platform storage contract 和随包 Zhiyi skill 中统一报告 2026.6.15。
• 安装 smoke 适配大库慢启动：macOS、Linux、Windows 安装器现在会等待本地服务就绪，不再把一次过早探测失败当成最终失败。
• 经验验证回执：行策可以生成 dry-run 验证回执格式，记录通过/失败状态、证据链接和采纳阻断点，但不改写经验库。
• 采纳门禁引用回执：采纳检查会优先使用验证回执；旧的验证报告路径仍然保持兼容。
• 采纳包预览：可以生成本地 dry-run 采纳包。package_status=ready 只表示未来授权采纳已准备好，不表示已经采纳。
• 经验链路总览：控制台可以展示经验演进、review action、验证报告、验证回执、review queue、采纳门禁、采纳回执格式、采纳包的紧凑记录链路。
• 发布验证：2026.6.15 已在本轮对本机 macOS 和两台 Windows 主机实测；本地全量测试通过、提交前 working-tree release gate 通过、发布前 committed-HEAD release gate 通过、Windows 原生 smoke 通过，记录链路巡检未发现遗失源或遗失 raw。已在检测到的 Windows Claude 配置位置确认 Claude Desktop bridge 存在；其中一个 package-scoped Windows 配置仍是异常 JSON，作为本机后续项保留。
• 记录医生与记录链路：新增只读 doctor/demo 自检，展示源记录、raw 镜像、所有会话底座、记忆与经验链路是否守住；timeline/replay 按记录链路展示，不做记忆墙。
• 召回默认降噪：知意召回默认返回精简的来源线索、计数、回执和命中理由；有界原文摘录仍可用，但必须显式请求 raw response budget。
• 运行地基统一起步：新增统一 repository/import bootstrap，新入口和后续迁移可以复用同一套路径初始化，不再继续增加零散 path setup。
• 双击安装入口：release zip 现在包含 macOS Memcore Cloud Installer.command 和 Windows Memcore Cloud Installer.cmd；Windows 入口会先弹出目录选择，再调用同一套安装脚本。
• 公开文案收紧：公开文案改为强调本机工作续接、可回源记录、召回和可复用工作路径；细分接入覆盖留作维护者测试材料，不作为用户可见产品文本。
• 发布检查继续守门：公开文案扫描、私有本机 agent 规则文件排除、发布包检查、内部方向审计和全量测试已在发布前通过。

边界

• 发布资源从提交后的 HEAD 构建，并在 release gate 通过后上传到 GitHub Release。
• 维护者本地文件和私有本机 agent 规则文件仍然被忽略，不进入公开发布包。
• capability check 仍然只读、无真实召回。
• 明确配置时仍然保留 OpenClaw / Hermes 的局域网访问能力。
• 2026.6.15 的多机验证已来自 2026-06-15 当前运行；没有沿用旧版 2026.6.14 的结论。