# Vanta packages — conventions every app follows

- One directory per app: `vendor/vanta/packages/<Name>/` with `Android.bp`,
  `AndroidManifest.xml` (with `package=`), `src/` (Kotlin), `res/`.
- Package ids: `com.failure.vanta.<lowercase>`. Module names: `Vanta<Name>`.
- Soong: `android_app`, `certificate: "platform"`, `privileged: true`,
  `system_ext_specific: true`, `platform_apis: true`,
  `kotlin_plugins: ["kotlin-compose-compiler-plugin"]`,
  `static_libs: ["VantaCore", ...]`, `optimize: { enabled: false }`.
  Privileged permissions go in `permissions/privapp-permissions-<pkg>.xml`
  (installed by a `prebuilt_etc` with `sub_dir: "permissions"`,
  `system_ext_specific: true`).
- Look: only `VantaTheme`, `VantaTokens`, `Modifier.vantaGlass`, `vantaSpring()`
  from VantaCore. No Material look leaks through: no default TopAppBar, no
  FAB, no ripple-on-grey list rows. True black background everywhere.
- Config: `VantaConfig` keys only (VantaCore/src/.../VantaConfig.kt). VantaHub
  hosts the provider; every other app is a client and must behave sensibly
  when a key is unset.
- APIs: public + `@SystemApi` code must compile against the public SDK in the
  shadow build (`tools/shadow/build.sh`). Anything hidden goes behind a small
  reflective wrapper in that app's `Hidden.kt`, with a fallback.
- No comments restating code. Comments only for the non-obvious (why).
