Package discipline for builders.
The developer area defines how SentinelOS packages, tools, apps, reports, and release material should be prepared before publication.
Local-firstApps should work offline by default where practical.
No silent networkNetwork features should be explicit, documented, and user-visible.
Private filesDatabases, backups, exports, and sidecars should use safe permissions.
Package-owned policyOfficial system changes belong in versioned packages.
Rollback-awareRelease notes should document recovery and downgrade expectations.
AEGIS-safeActions should be bounded, auditable, and user-authorised.
Package checklist
Release material expected from builders.
Before promotion, each package should have metadata, changelog, validation notes, manifest, checksums, and known issue notes.
debian/control
debian/changelog
debian/postinst / prerm review
package manifest
validation report
SHA256SUMS