docs(v0.8): sync README + spec headers to v0.8-asset-architecture (fix stale v0.6/v0.8+ references)#118
Merged
Conversation
README.md / README.en.md: title, version badge, and status-block lifted from v0.6.0 to v0.8-asset-architecture (~88% -> ~82%, reflecting the v0.7-vision-shift repositioning onto the .life dual standard). New v0.8 highlights block summarises the four-layer asset architecture, Schema D 12-tier naming, 5-stage assembly pipeline, and builder v0.2 auto-tier compute. 'Planned' list swaps media/build/runtime placeholders for reference runtime implementation (v0.9+), encrypted + signing (life-format v0.2), and permission models. docs/LIFE_RUNTIME_STANDARD.md + docs/LIFE_FILE_STANDARD.md: update three stale 'deferred to v0.8+' call-outs to 'deferred to v0.9+', matching the v0.8-asset-architecture release stanza and ROADMAP.md's current deferral milestone. Runtime spec header now also notes that v0.8-asset-architecture added Part B (5-stage assembly) as spec. No schema / builder / test changes. batch_validate 22/22 passed.
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The v0.8 close-out PR (#117) brought the status docs (
IMPLEMENTATION_STATUS.md/GAP_ANALYSIS.md/ROADMAP.md/CHANGELOG.md) up to date, but missed the externally visible surfaces — the repo front page (README.md/README.en.md) still showsv0.6.0in the title, version badge, and status block, and two spec docs still point the reader at a stale "deferred to v0.8+" milestone. This PR fixes those so every public-facing doc reports the real current state.Changes
README.md/README.en.mdv0.6.0→v0.8-asset-architecturereleases/tag/v0.8-asset-architecture.lifedual standard in v0.7-vision-shift).lifefile-format spec, runtime protocol spec, asset architecture, build pipelines, validation tools) rather than the generic v0.2-era listdlrs-runtimereference implementation (v0.9+), encrypted + signing (life-format v0.2), permission models — replacing the old "媒体采集规范 / 构建管线 / 运行时系统" placeholdersdocs/LIFE_RUNTIME_STANDARD.mdv0.8+ → v0.9+v0.8+ → v0.9+v0.8+ → v0.9+docs/LIFE_FILE_STANDARD.mdv0.8+ → v0.9+v0.8+ → v0.9+No schema / builder / test changes.
python tools/batch_validate.py→ 22/22 passed.Follow-up (not in this PR)
After this merges I will create the three missing GitHub Releases (v0.6.0 / v0.7-vision-shift / v0.8-asset-architecture) with tags pinned to the corresponding epic's final merge commit, using the existing CHANGELOG stanzas as release notes. The broken release badge URL in the README will resolve once the v0.8-asset-architecture tag exists.
Review & Testing Checklist for Human
README.md/README.en.mdto confirm the v0.8 highlights block + updated Completed / Planned lists read well and match your understanding of where we stand.v0.8--asset--architectureusing double-dash shields.io escape) renders correctly on GitHub once the tag exists.Notes
Addresses BELLO's callout that the docs / releases were never updated after the v0.8 close-out. CHANGELOG + IMPLEMENTATION_STATUS + GAP_ANALYSIS + ROADMAP were done in #117; this PR completes the surface refresh on the README and two spec headers.
Link to Devin session: https://app.devin.ai/sessions/ff7322e18fd94887875daa2c1c75f87d
Requested by: @LING71671