software.release.project
A software project. The record key is the project name itself, making duplicate names per repo impossible and enabling AppView-free resolution. Name grammar (normative prose): 1 to 64 lowercase ASCII alphanumerics and interior hyphens only, no dots or colons, no leading or trailing hyphen.
Details · record, key any
| Kind | record |
|---|---|
| Record key | any |
| Authority | release.software |
| Indexed |
Record
record · key anyProperties
Machine name of the project. MUST equal the record key. Serves as URL segment, uniqueness key, display fallback, and install token.
minLength: 1maxLength: 64
parent
string · at-uriAn AT URI to a software.release.project that this project either derives or descends from.
renamedTo
string · at-uriWhen set, this project has been renamed: the record persists as a permanent alias to the successor software.release.project. Record keys are immutable, so rename is never an in-place edit and an old name is never reusable.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
software.release.version
recordAn immutable named pointer to a manifest. The record key is '{projectName}:{version}', making uniqueness per (project, version) mechanical and enabling AppView-free resolution. Version strings follow the project-name grammar (lowercase alphanumerics, interior hyphens) but allow dots. The version string cannot contain colons, but the rkey must contain exactly one colon. Valid only when same-DID with the referenced project, and only when target references a manifest of that same project.
-
software.release.channel
recordA mutable named pointer to a version. Resolve the manifest through the referenced version. The record key is '{projectName}:{channelName}', making uniqueness per (project, name) mechanical and enabling AppView-free resolution. Channel names follow the project-name grammar (lowercase alphanumerics, interior hyphens, no dots). The project name cannot contain colons, but the rkey must contain exactly one colon. Valid only when same-DID with the referenced project and version.
-
software.release.manifest
recordAn immutable collection of release artifacts. Written once and never updated: all facts (artifact digests, sizes, locations) are fixed at creation. Lifecycle changes use software.release.status records and software.release.channel moves. Any update to an existing release record is treated by indexers as a probable-compromise signal. Valid only when this record's DID matches the referenced project's DID.