TaiChiOS 0.1.0-mvp.6

TaiChiOS 0.1 MVP prerelease 6

本预发布版是 TaiChiOS 0.1 可启动、可安装系统基线的维护发布。它保持 mvp.5 已验收的 Debian 镜像、Harness 运行时、事务式变更、Guardian 与独立 Recovery 路径，同时升级 GitHub 构建来源证明动作并刷新官网依赖。它只适用于隔离的 x86_64 虚拟机，不适用于生产设备。

验收合同

发布流水线从同一标签构建二进制 ISO 与对应源码 ISO，并在发布前验证：

• 固定的 Cordis、DeepSeek Harness、Node.js 与 dsh-TUI 组合可离线启动；
• BIOS 与 UEFI 均可在无网络环境启动 Live 系统；
• BIOS 与 UEFI 均可执行整盘安装，移除 Live 介质并断网后可从硬盘启动；
• Guardian、Safe Profile、Recovery 与事务式 Change Set 验收保持通过；
• 生成包/源码清单、SHA-256 校验和、发布元数据、构建环境记录与 GitHub 构建来源证明。

请下载 taichios-0.1-amd64.hybrid.iso 并使用 SHA256SUMS 验证。Release 同时提供对应源码 ISO、源码/包清单、构建环境与机器可读兼容性元数据。

相比 mvp.5 的变化

• 将 actions/attest-build-provenance 从 v3 升级到 v4，发布制品继续生成 GitHub build-provenance attestation。
• 将官网 lucide-react 从 1.33.0 升级到 1.34.0。
• 将官网 @types/node 从 24.10.1 升级到 24.13.3，并随 lockfile 将 undici-types 更新到 7.18.2。
• Debian snapshot、Node.js 镜像运行时、Cordis、DeepSeek Harness 与 dsh-TUI 固定版本不变；本次没有新增系统迁移或磁盘格式变更。

迁移、失败与恢复

• 从 mvp.5 升级没有自动的跨版本原地迁移器；推荐在隔离虚拟机中全新安装 mvp.6。
• 托管文件和 /opt/taichios system-update 可使用已记录 Rollback Point 恢复；缺少回滚点或恢复失败会保留 rollback-failed 证据。
• Guardian/Harness 故障可回退到 Safe Profile 或独立 Recovery；Recovery 不提供任意 Debian 包状态的跨版本完整回滚。
• 如 mvp.6 无法满足需求，可重新安装经校验的 mvp.5 镜像；用户数据迁移仍需人工备份与恢复。

限制

• 工厂凭据只用于开发验收；尚未实现生产凭据注册。
• 默认 Provider 是离线 mock；尚未实现持久身份、加密 Secret 存储、配额、健康检查和生产 Provider adapter。
• 固定镜像策略仍禁用 Secure Boot 与额外固件。
• 社区插件尚未具备生产级来源验证、授权和强制执行隔离。
• 本预发布版没有生产安全 SLA。请通过 GitHub Security Advisories 报告漏洞。

English

This maintenance prerelease preserves the verified TaiChiOS 0.1 bootable and installable system baseline while upgrading GitHub build-provenance attestation and refreshing website dependencies. It is intended for isolated x86_64 virtual machines, not production devices.

Acceptance contract

The release workflow builds the binary ISO and corresponding-source ISO from the same tag, then gates publication on:

• offline startup of the pinned Cordis, DeepSeek Harness, Node.js, and dsh-TUI combination;
• BIOS and UEFI Live boot without networking;
• whole-disk installation under BIOS and UEFI, followed by disk boot without the Live medium or networking;
• continued Guardian, Safe Profile, Recovery, and transactional Change Set acceptance;
• package/source manifests, SHA-256 checksums, release metadata, build-environment recording, and GitHub build-provenance attestation.

Download taichios-0.1-amd64.hybrid.iso and verify it with SHA256SUMS. The Release also contains the corresponding-source ISO, source/package manifests, build environment, and machine-readable compatibility metadata.

Changes since mvp.5

• Upgrades actions/attest-build-provenance from v3 to v4 while retaining GitHub build-provenance attestation for release payloads.
• Upgrades the website's lucide-react from 1.33.0 to 1.34.0.
• Upgrades the website's @types/node from 24.10.1 to 24.13.3 and refreshes lockfile-pinned undici-types to 7.18.2.
• Keeps the Debian snapshot and pinned Node.js image runtime, Cordis, DeepSeek Harness, and dsh-TUI versions unchanged; this release adds no system migration or disk-format change.

Migration, failure, and recovery

• There is no automated in-place cross-version migrator from mvp.5; use a clean mvp.6 installation in an isolated virtual machine.
• Managed files and the /opt/taichios system-update pointer can use a recorded Rollback Point. A missing rollback point or failed restore retains rollback-failed evidence.
• Guardian/Harness failures can fall back to Safe Profile or independent Recovery. Recovery does not provide arbitrary cross-version rollback of Debian package state.
• If mvp.6 is unsuitable, reinstall the verified mvp.5 image; user-data migration still requires manual backup and restore.

Limitations

• Factory credentials remain development-only; production credential enrollment is not implemented.
• The default Provider is an offline mock. Persistent identity, encrypted Secret storage, quotas, health checks, and production Provider adapters are not implemented.
• Secure Boot and additional firmware remain disabled by the pinned image policy.
• Community plugins do not yet have production-grade provenance validation, authorization, or enforced execution isolation.
• This prerelease has no production security SLA. Report vulnerabilities through GitHub Security Advisories.

TaiChiOS 0.1.0-mvp.5

TaiChiOS 0.1 MVP prerelease 5

本预发布版把 TaiChiOS 从可启动、可安装的系统基线推进到具备可审计控制面契约、事务式托管文件变更、独立 Guardian 控制通道和可信 Recovery 路径的候选系统。它只适用于隔离的 x86_64 虚拟机，不适用于生产设备。

验收合同

发布流水线从同一标签构建二进制 ISO 与对应源码 ISO，并在发布前验证：

• 固定的 Cordis、DeepSeek Harness、Node.js 与 dsh-TUI 组合可离线启动；
• BIOS 与 UEFI 均可在无网络环境启动 Live 系统；
• BIOS 与 UEFI 均可执行整盘安装，移除 Live 介质并断网后可从硬盘启动；
• 安装器、首次启动和 Recovery 不会与普通 Harness supervision 竞争；
• Guardian 能检测 Harness 崩溃、过期心跳和 tty1 丢失，并通过 root-only 控制通道请求重启、Safe Profile 或 Recovery；
• Recovery 在宣布 ready 前验证构建时封存的可信文件清单；
• 托管文件 Change Set 覆盖 Dry Run、授权拒绝、候选激活、摘要验证、提交、回滚和 rollback-failed；
• 生成包/源码清单、SHA-256 校验和、发布元数据、构建环境记录与 GitHub 构建来源证明。

请下载 taichios-0.1-amd64.hybrid.iso 并使用 SHA256SUMS 验证。Release 同时提供对应源码 ISO、源码/包清单、构建环境与机器可读兼容性元数据。

相比 mvp.4 的系统变化

• 新增 Organization、Human User、Working Agent、Service Principal、非放大委托、Provider 调用、单次 Secret Grant 与审计归属的稳定 schema 和 TypeScript 参考契约。
• taichios-change 实现事务式托管文件生命周期，并为 /opt/taichios 的原子 system-update 指针提供真实激活、验证和回滚语义；不支持的 adapter 不再报告虚假成功。
• 新增独立 taichios-guardian.service、每个 Harness supervisor 的持续心跳、tty1 恢复，以及 root-only taichios-guardianctl 控制通道。
• Safe Profile 会隔离损坏的普通或第三方 Profile；独立 Recovery target 不依赖 Guardian、Harness 或普通 Profile，并验证可信文件清单。
• 安装器和首次启动路径与运行时监督隔离，避免整盘安装、Recovery 或首次启动被 Guardian/Harness 竞争。
• GitHub Actions 固定到第 7 代 checkout/setup-node/upload-artifact；网站工具链的高风险 major 更新被隔离为独立 Dependabot 边界。
• AGENTS.md 现在按完整 Debian 衍生操作系统的构建、启动、安装、恢复、供应链和发布风险约束 Agent，而不是按普通 Web 应用约束。

控制面 TypeScript 包是用于固定 0.2 跨包契约和安全语义的内存型参考实现，尚未装入 0.1 Live 镜像；本版本不会将其描述为生产身份或 Provider 服务。

迁移、失败与恢复

• 从 mvp.4 升级没有自动的跨版本原地迁移器；推荐在隔离虚拟机中全新安装 mvp.5。
• 托管文件和 /opt/taichios system-update 可使用已记录 Rollback Point 恢复；缺少回滚点或恢复失败会保留 rollback-failed 证据，不会伪装成功。
• Guardian/Harness 故障可回退到 Safe Profile 或独立 Recovery；Recovery 不提供任意 Debian 包状态的跨版本完整回滚。
• 如 mvp.5 无法满足需求，可重新安装经校验的 mvp.4 镜像；用户数据迁移仍需人工备份与恢复。

限制

• 工厂凭据只用于开发验收；尚未实现生产凭据注册。
• 默认 Provider 是离线 mock；尚未实现持久身份、加密 Secret 存储、配额、健康检查和生产 Provider adapter。
• 固定镜像策略仍禁用 Secure Boot 与额外固件。
• 社区插件尚未具备生产级来源验证、授权和强制执行隔离。
• 本预发布版没有生产安全 SLA。请通过 GitHub Security Advisories 报告漏洞。

English

This prerelease advances TaiChiOS from its bootable and installable baseline to a candidate system with auditable control-plane contracts, transactional managed-file changes, an independent Guardian control channel, and a trusted Recovery path. It is intended for isolated x86_64 virtual machines, not production devices.

Acceptance contract

The release workflow builds the binary ISO and corresponding-source ISO from the same tag, then gates publication on:

• offline startup of the pinned Cordis, DeepSeek Harness, Node.js, and dsh-TUI combination;
• BIOS and UEFI Live boot without networking;
• whole-disk installation under BIOS and UEFI, followed by disk boot without the Live medium or networking;
• isolation of installer, first-boot, and Recovery paths from normal Harness supervision;
• Guardian handling of Harness crashes, stale heartbeats, and tty1 loss, with root-only restart, Safe Profile, and Recovery requests;
• verification of the build-sealed trusted-file manifest before Recovery declares readiness;
• managed-file Change Set coverage for dry run, authorization rejection, candidate activation, digest verification, commit, rollback, and rollback-failed;
• package/source manifests, SHA-256 checksums, release metadata, build-environment recording, and GitHub build-provenance attestation.

Download taichios-0.1-amd64.hybrid.iso and verify it with SHA256SUMS. The Release also contains the corresponding-source ISO, source/package manifests, build environment, and machine-readable compatibility metadata.

System changes since mvp.4

• Adds stable schemas and TypeScript reference contracts for Organizations, Human Users, Working Agents, Service Principals, non-amplifying delegation, Provider invocation, single-use Secret Grants, and audit attribution.
• Implements a transactional managed-file lifecycle in taichios-change, including truthful activation, verification, and rollback semantics for the atomic /opt/taichios system-update pointer. Unsupported adapters no longer report false success.
• Adds an independent taichios-guardian.service, continuous heartbeat supervision per Harness supervisor, tty1 recovery, and the root-only taichios-guardianctl channel.
• Makes Safe Profile isolate broken normal or third-party Profiles. The independent Recovery target does not depend on Guardian, Harness, or normal Profiles and verifies a trusted-file manifest.
• Isolates installer and first-boot paths from runtime supervision so Guardian/Harness cannot race whole-disk installation, Recovery, or first boot.
• Pins GitHub Actions to generation 7 for checkout, setup-node, and upload-artifact, while isolating risky website tooling major updates behind a separate Dependabot boundary.
• Rewrites AGENTS.md around Debian-derivative build, boot, installation, recovery, supply-chain, and release risks instead of ordinary web-application assumptions.

The control-plane TypeScript packages are in-memory reference implementations for the 0.2 cross-package contracts and security semantics. They are not installed in the 0.1 Live image and are not presented as production identity or Provider services.

Migration, failure, and recovery

• There is no automated in-place cross-version migrator from mvp.4; use a clean mvp.5 installation in an isolated virtual machine.
• Managed files and the /opt/taichios system-update pointer can use a recorded Rollback Point. A missing rollback point or failed restore retains rollback-failed evidence instead of claiming success.
• Guardian/Harness failures can fall back to Safe Profile or independent Recovery. Recovery does not provide arbitrary cross-version rollback of Debian package state.
• If mvp.5 is unsuitable, reinstall the verified mvp.4 image; user-data migration still requires manual backup and restore.

Limitations

• Factory credentials remain development-only; production credential enrollment is not implemented.
• The default Provider is an offline mock. Persistent identity, encrypted Secret storage, quotas, health checks, and production Provider adapters are not implemented.
• Secure Boot and additional firmware remain disabled by the pinned image policy.
• Community plugins do not yet have production-grade provenance validation, authorization, or enforced execution isolation.
• This prerelease has no production security SLA. Report vulnerabilities through GitHub Security Advisories.

TaiChiOS 0.1.0-mvp.4

TaiChiOS 0.1 MVP prerelease 4

本预发布版修复首个可启动、可安装、可运行 TaiChiOS 镜像的图形控制台交接。它只适用于隔离的 x86_64 虚拟机，不适用于生产设备。

验收合同

发布流水线从同一标签构建二进制 ISO 与对应源码 ISO，并在发布前验证：

• BIOS 与 UEFI 均可在无网络环境启动 Live 系统；
• tty1 实际出现 taichi 用户会话后才输出 TAICHIOS_LIVE_SHELL_READY；
• BIOS 与 UEFI 均可执行整盘安装；
• 移除 Live 介质并断网后可从硬盘启动，且 tty1 实际出现 agetty 用户登录页后才输出 TAICHIOS_INSTALLED_LOGIN_READY；
• 本地主机名解析、固定 Harness 组合和独立 Recovery target 均通过；
• 生成包/源码清单、SHA-256 校验和、发布元数据、构建环境记录与 GitHub 构建来源证明。

请下载 taichios-0.1-amd64.hybrid.iso 并使用 SHA256SUMS 验证。Release 同时提供对应源码 ISO、源码/包清单、构建环境与机器可读兼容性元数据。

相比 mvp.3 的控制台变化

• 串口继续用于自动化验收，tty1 是主要图形控制台。
• Live 启动会等到既有 taichi 自动登录会话附着 tty1，使用户直接进入 Shell，而不是停在启动日志页。
• 安装后不会自动登录；只有 tty1 正在显示用户登录页才算验收通过。
• Install 启动项不执行 Live tty1 交接，避免 getty 重启与受保护的整盘安装器竞争。
• 安装器写入匹配的 IPv4/IPv6 主机名映射，避免本地 sudo 产生主机名解析警告。

限制

• 工厂凭据只用于开发验收；尚未实现生产凭据注册。
• 默认 Provider 是离线 mock；尚未实现生产 Provider 与 Secret Service 注册。
• 固定镜像策略仍禁用 Secure Boot 与额外固件。
• Recovery 支持已记录的 Profile 禁用和托管文件回滚，不提供跨版本完整系统回滚。
• 本预发布版没有生产安全 SLA。请通过 GitHub Security Advisories 报告漏洞。

English

This prerelease corrects the graphical-console handoff of the first public bootable, installable, runnable TaiChiOS image. It is intended for isolated x86_64 virtual machines, not production devices.

Acceptance contract

The release workflow builds the binary ISO and corresponding-source ISO from this exact tag, then gates publication on:

• BIOS and UEFI Live boot without networking;
• a taichi user session actually attached to tty1 before TAICHIOS_LIVE_SHELL_READY is emitted;
• whole-disk installation under BIOS and UEFI;
• installed boot without the Live medium or networking, with agetty actually presenting the tty1 user login page before TAICHIOS_INSTALLED_LOGIN_READY is emitted;
• local hostname resolution, pinned Harness composition, and the independent Recovery target;
• package/source manifests, SHA-256 checksums, release metadata, build-environment recording, and GitHub build-provenance attestation.

Download taichios-0.1-amd64.hybrid.iso and verify it with SHA256SUMS. The Release also contains the corresponding-source ISO, source/package manifests, build environment, and machine-readable compatibility metadata.

Console changes since mvp.3

• The serial console remains available for automated acceptance, while tty1 is the primary graphical console.
• Live boot now waits until the existing taichi autologin session is attached to tty1, leaving the user directly at a shell instead of a boot-log page.
• Installed boot does not autologin. It is accepted only when tty1 is actively presenting the user login page.
• Installer boots are excluded from the Live tty1 handoff, preventing a getty restart from racing the guarded whole-disk installer.
• The installer writes matching IPv4/IPv6 hostname entries so local sudo does not emit a hostname-resolution warning.

Limitations

• Factory credentials remain development-only; production credential enrollment is not implemented.
• The default Provider is an offline mock. Production Provider and Secret Service enrollment are not implemented.
• Secure Boot and additional firmware remain disabled by the pinned image policy.
• Recovery supports the documented Profile-disable and managed-file rollback paths, not full-system cross-release rollback.
• This prerelease has no production security SLA. Report vulnerabilities through GitHub Security Advisories.

TaiChiOS 0.1.0-mvp.3

TaiChiOS 0.1 MVP prerelease 3

This is the first public bootable, installable, runnable TaiChiOS image. It is an engineering prerelease for isolated x86_64 virtual machines, not a stable or production release.

Verified delivery contract

The release workflow builds the binary ISO and corresponding-source ISO from this exact tag, then gates publication on:

• pinned Debian and runtime compatibility checks;
• network-isolated BIOS and UEFI Live boot;
• whole-disk installation under BIOS and UEFI;
• disk-first-boot and independent Recovery-target acceptance;
• package/source manifests, a recorded CI build toolchain, SHA-256 checksums, release metadata, and GitHub build-provenance attestation.

Download taichios-0.1-amd64.hybrid.iso to boot or install. Verify it from SHA256SUMS; release-metadata.json records the Debian snapshot, runtime compatibility, actual image Profile/Bundle and system-plugin digests, artifact hashes, and rollback contract. taichios-0.1-source.iso carries the corresponding Debian source payload, source.contents lists its files, and build-environment.txt records the CI toolchain.

Important limitations

• The installer erases the selected disk. Use only a disposable VM disk.
• Automated acceptance covers QEMU x86_64 BIOS/UEFI; real hardware and firmware are not qualified.
• Installed factory credentials are taichi / taichi and creator / creator; there is no production credential-enrollment flow.
• The default Provider is an offline mock. Production Provider and Secret Service enrollment are not implemented.
• Secure Boot and additional firmware are disabled by the pinned image policy.
• Recovery can disable a Profile or roll back the last managed file Change Set; cross-release data migrations and full-system rollback are not provided.
• This prerelease has no production security SLA. Report vulnerabilities through GitHub Security Advisories.