edison/chanora
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: restore product scaffold to rollback baseline

Browse Source
This commit is contained in:
Edison Jwa
2026-05-29 14:02:04 +09:00
parent 2896f14ec9
commit fe6e07353e
434 changed files with 27278 additions and 63230 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/release/platform-release-policy.md
+26
View File
@@ -0,0 +1,26 @@
# Chanora Platform Release Policy
**Document status:** DV meeting baseline candidate
**Date:** 2026-05-29
## 1. Purpose
This policy defines platform release expectations for Chanora candidate builds.
## 2. Platform Policy
| Platform | Minimum release requirement | Current DV state |
|---|---|---|
| Android | Signed release or internal test artifact, target SDK compliance, permission/foreground-service validation | Internal validation only; Android DEK waiver active |
| iOS | Signed TestFlight/App Store build or explicitly unsigned verification build | Unsigned verification build only |
| Windows | Packaged build, smoke result, PTT capability evidence, signing decision | Source-buildable only |
| macOS | Universal build, signing/notarization, PTT capability evidence | Source-buildable only |
| Linux | Packaged build or documented source-build path, portal/fallback PTT evidence | Source-buildable only |
## 3. Release Claim Rule
Release notes and public wording must match the actual artifact and platform capability. A source-buildable platform must not be described as having a finished public binary release.
## 4. DV Conclusion
The platform policy is defined. Current candidate scope remains internal validation and documentation review.