v0.8 close-out: tier integration into life-package.schema.json + auto-compute builder + status docs#117
Merged
Conversation
- schemas/life-package.schema.json: inline $defs.tier_block + $defs.tier_dimensions (copied from tier.schema.json); add optional top-level tier property; mark verification_level deprecated (remains required for v0.1 back-compat). - tools/build_life_package.py v0.2: auto-compute tier from contents + CLI overrides; weighted-average scoring per docs/LIFE_TIER_SPEC.md §4.1; Schema D banding; computed_by stamped with mandatory @<version> separator (hand-rolled blocks rejected). - tools/test_life_package_schema.py: +10 tier cases (54 -> 64) covering back-compat omission, consistent happy path, both boundaries, score↔level mismatch, hand-rolled computed_by, score range, off-enum dim, missing dim, unknown field. - tools/test_minimal_life_package.py: verifies builder emits well-formed tier block with @-separated computed_by and all 6 dimensions. - docs/LIFE_FILE_STANDARD.md: adds tier row; marks verification_level deprecated with link to docs/LIFE_TIER_SPEC.md §6. - docs/IMPLEMENTATION_STATUS.md (v6.0), docs/GAP_ANALYSIS.md, ROADMAP.md, CHANGELOG.md: v0.8 release stanza + delivery table updates; reference runtime deferral moved from v0.8+ to v0.9+. All 22/22 batch_validate checks pass; test_life_package_schema 64/64; test_minimal_life_package deterministic bytes match across two builds. Closes v0.8-asset-architecture follow-up (epic #106).
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:
|
2 tasks
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
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
Final integration PR that closes out the v0.8-asset-architecture epic (#106). Weaves the standalone
schemas/tier.schema.json(shipped in #113) into the top-levelschemas/life-package.schema.jsonso v0.8 builders emit a single descriptor that carries the tier block, and teachestools/build_life_package.pyto auto-compute that block at build time. Also refreshes the long-lived status documents (IMPLEMENTATION_STATUS.md,GAP_ANALYSIS.md,ROADMAP.md,CHANGELOG.md) to reflect the v0.8 release.Schema integration
schemas/life-package.schema.jsontierproperty that$refs#/$defs/tier_block.$defs.tier_block+$defs.tier_dimensionscopied verbatim fromschemas/tier.schema.json, so offline validators do not need to resolve cross-file$ref(same pattern the repo already uses everywhere else).verification_levelas deprecated in v0.8 in the description text while keeping itrequiredfor v0.1 back-compat. Points atdocs/LIFE_TIER_SPEC.md §6for the migration mapping.tier) keep validating; v0.8 packages (withtier) are additionally score↔level consistency-checked via the 12allOfbands.tools/test_life_package_schema.pytieromitted,tierpresent + consistent (score 54 → VII), lowest-bound (0 → I Quark), highest-bound (100 → XII Singularity), score↔level mismatch rejection, hand-rolledcomputed_byrejection, score > 100 rejection, off-enum dimension, missing required dimension, unknown field.Builder auto-compute
tools/build_life_package.pyv0.2_compute_tierthat deterministically maps v0.7verification_level→ v0.8identity_verification(perdocs/LIFE_TIER_SPEC.md §6), infersasset_completenessfrom capability-bearing top-level directories, and defaults the remaining four dimensions conservatively._TIER_BANDStable used by the schema, so any drift is a test-visible bug.computed_by = "tools/build_life_package.py@0.2.0"; the mandatory@<version>separator is schema-enforced, so hand-rolled tier blocks fail validation.--tier-<dim>CLI overrides for issuers who can declare higher-than-default levels (e.g. a studio-recorded voice asset →--tier-detail-level high_fidelity) and a--no-tierescape hatch for emitting v0.7-shaped descriptors.tools/test_minimal_life_package.pynow asserts the emitted descriptor contains a well-formed tier block with all 6 dimensions and an@-separatedcomputed_by.Spec / status doc refresh
docs/LIFE_FILE_STANDARD.md— adds thetierrow to the descriptor table; marksverification_levelas deprecated with a pointer todocs/LIFE_TIER_SPEC.md §6.docs/IMPLEMENTATION_STATUS.md— bumps to doc version 6.0; adds v0.8 increment summary; overall maturity ~80% → ~82%.docs/GAP_ANALYSIS.md— baseline moves to post-[EPIC] v0.8 — Asset Architecture (Genesis / Lifecycle / Binding / Tier / Assembly) #106;.lifeArchive Standard 70% → 82%;.lifeRuntime Standard 30% → 45%.ROADMAP.md— markslife-format v0.1.0andlife-runtime v0.1as Delivered; addslife-format v0.1.1(Asset Architecture) andlife-runtime v0.1.1(Assembly) rows as Delivered under v0.8-asset-architecture; reference runtime deferral moved from v0.8+ → v0.9+.CHANGELOG.md— v0.8-asset-architecture stanza flipped from Draft → Released; new entries describing the tier integration + builder v0.2 + status doc bumps.Local verification
python tools/test_life_package_schema.py→ all 64/64 cases pass.python tools/test_minimal_life_package.py→ OK (descriptor valid, contents inventory matches, audit chain links, deterministic bytes across two builds).python tools/batch_validate.py→ 22/22 passed.Review & Testing Checklist for Human
$defs.tier_block/$defs.tier_dimensionsinlife-package.schema.jsonstays byte-for-byte identical toschemas/tier.schema.json(the repo has no automated drift check yet; future signature/cross-schema PR should add one)._compute_tierdefaults intools/build_life_package.py— conservative defaults are intentional (consent_completeness: text_only,audit_chain_strength: linked,jurisdiction_clarity: unspecified). If the org expects a different default for the demo record, issuers can lift them with the new--tier-*flags.tierrow indocs/LIFE_FILE_STANDARD.mdreads correctly and theverification_leveldeprecation note is visible.Notes
This is the spec-layer close-out for v0.8. It is not the start of v0.9 runtime implementation. No runtime code is added; the builder is the only code change and its behaviour remains deterministic + offline + pointer-mode.
Closes out epic #106 follow-up (integration). Sub-issues #100–#105 were already merged via PRs #107, #108, #110, #111, #113, #115; follow-ups #109, #112, #114, #116 merged alongside.
Link to Devin session: https://app.devin.ai/sessions/ff7322e18fd94887875daa2c1c75f87d
Requested by: @LING71671