diff --git a/README.en.md b/README.en.md
index 7f0c259..8554321 100644
--- a/README.en.md
+++ b/README.en.md
@@ -1,4 +1,4 @@
-# Digital Life Repository Standard (DLRS) v0.6.0
+# Digital Life Repository Standard (DLRS) v0.8-asset-architecture
@@ -14,7 +14,7 @@ Privacy-first, consent-based, structured, revocable, auditable, schema-validated
> This is an early-stage open standard draft. Feedback, translations, schema improvements, and ethical review are welcome.
[](https://github.com/Digital-Life-Repository-Standard/DLRS/blob/master/LICENSE)
-[](https://github.com/Digital-Life-Repository-Standard/DLRS/releases/tag/v0.6.0)
+[](https://github.com/Digital-Life-Repository-Standard/DLRS/releases/tag/v0.8-asset-architecture)
[](https://github.com/Digital-Life-Repository-Standard/DLRS/tree/master/docs/i18n)
[](https://github.com/Digital-Life-Repository-Standard/DLRS/blob/master/docs/community/RFC-DLRS-v0.2.md)
@@ -58,7 +58,7 @@ Spec: [`docs/LIFE_RUNTIME_STANDARD.md`](docs/LIFE_RUNTIME_STANDARD.md).
DLRS also defines the underlying structures that the `.life` standard rests on:
-- 📋 DLRS repository / archive directory structure and JSON schemas (stable as of v0.6)
+- 📋 DLRS repository / archive directory structure and JSON schemas (stable as of v0.6; v0.8 adds the four-layer asset architecture and tier system)
- ✅ Consent and withdrawal models
- 🔒 Privacy boundaries and sensitivity levels
- 🏛️ Governance rules and review processes
@@ -76,7 +76,7 @@ DLRS also defines the underlying structures that the `.life` standard rests on:
- ❌ **NOT** a guarantee that AI avatars equal real persons
- ❌ **NOT** a guarantee of legal compliance
- ❌ **NOT** a permanent storage solution — every `.life` MUST declare `expires_at`; runtimes MUST refuse to mount after it
-- ❌ **NOT** a mature production system — this repo currently ships specs + schema + an example builder; **no reference runtime implementation is shipped** (deferred to v0.8+)
+- ❌ **NOT** a mature production system — this repo currently ships specs + schema + an example builder; **no reference runtime implementation is shipped** (deferred to v0.9+)
- ❌ **NOT** a substitute for legal advice
---
@@ -222,30 +222,40 @@ Welcome contributions for more language translations! See [i18n guide](docs/i18n
## 📊 Current Status
-**Version**: v0.6.0
+**Version**: v0.8-asset-architecture
**Status**: RFC (Request for Comments) stage
-**Completion**: Approximately 88% (v0.6.0 release)
+**Completion**: Approximately 82% (v0.8-asset-architecture release; v0.7's ~80% plus Asset Architecture four layers + Tier system + 5-stage assembly; denominator expanded when ULTIMATE was repositioned as the `.life` dual standard)
+
+### v0.8 highlights
+
+v0.8-asset-architecture ([epic #106](https://github.com/Digital-Life-Repository-Standard/DLRS/issues/106)) completes the asset dimension and runtime assembly protocol for `.life`:
+
+- **Four-layer asset architecture**: Genesis (traceable provenance) / Lifecycle (supersedes, memorial, withdrawal cascade) / Binding (capability declaration + orchestration + hard constraints) / Tier (6-dimensional weighted credit rating)
+- **Schema D Cosmic Evolution**: 12 tier levels (Quark → Singularity); machine fields frozen; name/glyph in an evolvable appendix
+- **5-stage assembly pipeline**: Verify / Resolve / Assemble / Run / Guard; Provider Registry + `LifeCapabilityProvider` interface + graded sandbox + hosted-API AND-gate
+- **Builder v0.2**: `tools/build_life_package.py` auto-derives the tier block from contents; hand-rolled tier blocks are rejected at the schema layer via the `computed_by` pattern
+
+See `docs/LIFE_ASSET_ARCHITECTURE.md` + `docs/LIFE_TIER_SPEC.md` + `docs/LIFE_RUNTIME_STANDARD.md` Part B.
### ✅ Completed
- Basic directory structure
-- JSON schema definitions
-- Consent and withdrawal model
-- Privacy boundary definitions
-- Validation tools
-- Example archives
+- `.life` file-format spec + JSON Schema (v0.7-vision-shift)
+- `.life` runtime protocol spec (v0.7 + v0.8 Part B 5-stage assembly)
+- Consent, withdrawal, memorial, forbidden_uses
+- Four-layer asset architecture + tier system + Schema D naming (v0.8)
+- Build pipelines (v0.5 offline-first + v0.6 memory_atoms / knowledge_graph)
+- Validation tools + example archives
- Bilingual documentation
### 🚧 In Progress
- Community feedback collection
- Schema optimization
-- Documentation refinement
- Multi-language translation
### 📋 Planned
-- Media collection standards
-- Build pipelines
-- Runtime systems
-- Permission and audit implementation
+- `dlrs-runtime` reference implementation (v0.9+; first version that actually runs the 5-stage assembly per spec)
+- Encrypted mode + signing (life-format v0.2)
+- Permission models (RBAC / ReBAC / ABAC)
See [ROADMAP.md](ROADMAP.md) and [Implementation Status](docs/IMPLEMENTATION_STATUS.md)
diff --git a/README.md b/README.md
index 1e92af5..f3f9b48 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# Digital Life Repository Standard (DLRS) v0.6.0
+# Digital Life Repository Standard (DLRS) v0.8-asset-architecture
@@ -15,7 +15,7 @@
> 这是早期开放标准草案。欢迎反馈、翻译、Schema 改进和伦理审查。
[](https://github.com/Digital-Life-Repository-Standard/DLRS/blob/master/LICENSE)
-[](https://github.com/Digital-Life-Repository-Standard/DLRS/releases/tag/v0.6.0)
+[](https://github.com/Digital-Life-Repository-Standard/DLRS/releases/tag/v0.8-asset-architecture)
[](https://github.com/Digital-Life-Repository-Standard/DLRS/tree/master/docs/i18n)
[](https://github.com/Digital-Life-Repository-Standard/DLRS/blob/master/docs/community/RFC-DLRS-v0.2.md)
@@ -59,7 +59,7 @@ Schema [`schemas/life-package.schema.json`](schemas/life-package.schema.json)。
DLRS 同时定义了 `.life` 标准依赖的底层结构:
-- 📋 DLRS 仓库 / 档案目录结构和 JSON Schema(v0.6 已稳定)
+- 📋 DLRS 仓库 / 档案目录结构和 JSON Schema(v0.6 已稳定,v0.8 新增资产架构四层 + Tier 系统)
- ✅ 授权和撤回模型
- 🔒 隐私边界和敏感度分级
- 🏛️ 治理规则和审核流程
@@ -77,7 +77,7 @@ DLRS 同时定义了 `.life` 标准依赖的底层结构:
- ❌ **不是**保证 AI 分身等同真人的承诺
- ❌ **不是**法律合规的保证
- ❌ **不是**永久存储解决方案 —— `.life` 必须有 `expires_at`,超期 MUST 拒绝挂载
-- ❌ **不是**成熟的生产系统 —— 本仓库当前阶段交付的是规范 + Schema + 示例打包器;**reference runtime 实现尚未交付**(推迟到 v0.8+)
+- ❌ **不是**成熟的生产系统 —— 本仓库当前阶段交付的是规范 + Schema + 示例打包器;**reference runtime 实现尚未交付**(推迟到 v0.9+)
- ❌ **不是**法律建议的替代品
---
@@ -223,30 +223,40 @@ python tools/validate_repo.py
## 📊 当前状态
-**版本**: v0.6.0
+**版本**: v0.8-asset-architecture
**状态**: RFC(征求意见)阶段
-**完成度**: 约 88% (v0.6.0 release)
+**完成度**: 约 82% (v0.8-asset-architecture release;v0.7 的 ~80% 基础上 +Asset Architecture 四层 + Tier 系统 + 5 阶段 assembly,分母因 ULTIMATE 重新定位为 `.life` 双标准而扩大)
+
+### v0.8 主要增量
+
+v0.8-asset-architecture([epic #106](https://github.com/Digital-Life-Repository-Standard/DLRS/issues/106))为 `.life` 补齐资产维度和 runtime 装配协议:
+
+- **资产架构四层**:Genesis(产生过程可追溯)/ Lifecycle(支持 supersedes、memorial、撤回级联)/ Binding(能力声明 + 编排 + 硬约束)/ Tier(6 维加权派生的信用评分)
+- **Schema D Cosmic Evolution**:Tier 12 档命名(Quark → Singularity),机器字段冻结,name/glyph 进可演化附录
+- **5 阶段 assembly 流水线**:Verify / Resolve / Assemble / Run / Guard,Provider Registry + `LifeCapabilityProvider` 接口 + 分级沙箱 + hosted-API AND-gate
+- **Builder v0.2**:`tools/build_life_package.py` 自动从 contents 派生 tier 并写回 descriptor,hand-rolled tier 被 `computed_by` 模式直接 schema 层拒绝
+
+详见 `docs/LIFE_ASSET_ARCHITECTURE.md` + `docs/LIFE_TIER_SPEC.md` + `docs/LIFE_RUNTIME_STANDARD.md` Part B。
### ✅ 已完成
- 基础目录结构
-- JSON Schema 定义
-- 授权和撤回模型
-- 隐私边界定义
-- 验证工具
-- 示例档案
+- `.life` 文件格式 spec + JSON Schema(v0.7-vision-shift)
+- `.life` runtime 协议 spec(v0.7 + v0.8 Part B 5 阶段 assembly)
+- 授权、撤回、memorial、forbidden_uses
+- 资产架构四层 + Tier 系统 + Schema D 命名(v0.8)
+- 构建管线(v0.5 offline-first + v0.6 memory_atoms / knowledge_graph)
+- 验证工具 + 示例档案
- 中英文文档
### 🚧 进行中
- 社区反馈收集
- Schema 优化
-- 文档完善
- 多语言翻译
### 📋 计划中
-- 媒体采集规范
-- 构建管线
-- 运行时系统
-- 权限和审计实现
+- `dlrs-runtime` 参考实现(v0.9+,按 spec 跑 5 阶段 assembly 的第一版)
+- 加密 mode + 签名(life-format v0.2)
+- 权限模型(RBAC / ReBAC / ABAC)
详见 [ROADMAP.md](ROADMAP.md) 和 [实施状态](docs/IMPLEMENTATION_STATUS.md)
diff --git a/docs/LIFE_FILE_STANDARD.md b/docs/LIFE_FILE_STANDARD.md
index 9b9209c..0ea1011 100644
--- a/docs/LIFE_FILE_STANDARD.md
+++ b/docs/LIFE_FILE_STANDARD.md
@@ -58,7 +58,7 @@ A `.life` package can include:
`.life` files require an authorized representative + an active
withdrawal endpoint.
- ❌ A working runtime — this epic ships specs + schema + an example
- builder. Runtime reference implementations are deferred to v0.8+.
+ builder. Runtime reference implementations are deferred to v0.9+.
- ❌ A container for raw biometric data in pointer mode. By default
raw audio / video / image stays in upstream object storage; the
`.life` only ships *pointers*.
@@ -357,7 +357,7 @@ with `.life` and SHOULD NOT advertise itself as such.
## 9. Non-goals (deferred)
-- Working runtime reference implementation (deferred to v0.8+ DLRS
+- Working runtime reference implementation (deferred to v0.9+ DLRS
repo versions).
- Cryptographic signature scheme for `signature_ref` (deferred to
`life-format v0.2`, likely C2PA).
diff --git a/docs/LIFE_RUNTIME_STANDARD.md b/docs/LIFE_RUNTIME_STANDARD.md
index 9152fc0..2e62afe 100644
--- a/docs/LIFE_RUNTIME_STANDARD.md
+++ b/docs/LIFE_RUNTIME_STANDARD.md
@@ -6,7 +6,8 @@
> ([`docs/LIFE_FILE_STANDARD.md`](LIFE_FILE_STANDARD.md), schema
> [`schemas/life-package.schema.json`](../schemas/life-package.schema.json))
> to produce an *AI digital life instance*. This epic ships the spec
-> only; a reference runtime implementation is **deferred to v0.8+**.
+> only; v0.8-asset-architecture added Part B (5-stage assembly) as
+> spec; a reference runtime implementation is **deferred to v0.9+**.
[#79]: https://github.com/Digital-Life-Repository-Standard/DLRS/issues/79
@@ -39,7 +40,7 @@ regardless of transport.
- Data residency / sovereignty rules (those are encoded in the
`.life` itself via `verification_level`, `withdrawal_endpoint`,
and the upstream object-storage policy in pointer mode).
-- Reference runtime implementation (deferred to v0.8+).
+- Reference runtime implementation (deferred to v0.9+).
---
@@ -418,7 +419,7 @@ A runtime that does not enforce all five is **not** compatible with
## 11. Non-goals (deferred)
-- Working runtime reference implementation (deferred to DLRS v0.8+
+- Working runtime reference implementation (deferred to DLRS v0.9+
in this repo, OR an out-of-tree implementation by a downstream
project).
- Specific transport protocol (WebSocket / gRPC / REST) — runtime is