Package discipline for builders.
The developer area defines how Sentinel Linux packages, tools, applications, reports and release material should be prepared before publication.
Local-first
Apps should work offline by default where practical.
No silent network
Network features should be explicit, documented and visible to the user.
Private files
Databases, backups, exports and sidecars should use safe permissions.
Package-owned policy
Official system changes belong in versioned packages.
Rollback-aware
Release notes should document recovery and downgrade expectations.
AEGIS-safe
Actions should be bounded, auditable and user-authorised.
Package checklist
Release material expected from builders.
Before promotion, each package should have metadata, a changelog, validation notes, a manifest, checksums and known-issue notes.
debian/control
debian/changelog
debian/postinst and debian/prerm review
package manifest
validation report
SHA256SUMS