# General rules

Be absolutely frugal about spending remaining resources. Default to short, direct answers. Drop the opening pleasantries and the wrap-up summary. Lead with the answer, add detail only if it's needed, and stop when you're done.

# Naming and versioning

Applications shall use `cc.tiredsysadmin.<operating_system>.<application>` namespace for their unique identifiers. Versioning is done automatically each change according to semantic versioning policy. Track application versions of each platform accordingly (Android, macOS, Linux, BSD, Windows).

# Tools and building

Use Makefile as an entrypoint for building and publishing applications. Each target is atomic, construct dependencies.

For macOS versions always produce a DMG with a symlink to `/Applications` folder.

For Linux versions always produce a boilerplate for building .deb packages, also track changelog.

# Documentation

Write developer handover documentation explaining architecture and decisions.

# Publishing

Android applications shall be published to a private F-Droid repository at rcmd@garage.rcmd.space:/var/lib/fdroid/unsigned, and the application metadata must be published at rcmd@garage.rcmd.space:/var/lib/fdroid/metadata. Publishing is always a manual action, never automatic.

Android artifact naming scheme for publishing to unsigned directory is always `<application_id>_<version_code>.apk`

MacOS, Linux, and Windows versions keep builds locally.