From a0dbebe21a37f4c378b510b8fc08a8ab95e1b066 Mon Sep 17 00:00:00 2001 From: oxmc7769 Date: Sat, 25 Jul 2026 00:44:15 -0700 Subject: [PATCH] README: attribute policy-override payload to PawletOS's profiled fork, not stock vesperprofiled --- README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d98f7f8..6161191 100644 --- a/README.md +++ b/README.md @@ -93,9 +93,11 @@ policy (see the table below). Policy is resolved from three tiers, **most specific wins**: 1. **Runtime override** — `/data/misc/pawletcache/policy.json`. Written by - a `vesperprofiled` `content-cache` payload (MDM-pushed, can arrive any - time after first boot). Can pin `mode: lan` / `central` / `disabled`, or - pin an exact server + fingerprint, skipping discovery entirely. See + a `content-cache` payload from **PawletOS's fork of `vesperprofiled`** + (`git.oxmc.me/PawletOS/profiled` — the stock/upstream VesperOS daemon has + no such payload) via MDM push, any time after first boot. Can pin + `mode: lan` / `central` / `disabled`, or an exact server + fingerprint, + skipping discovery entirely. See [`vesperprofiled-config-schema/schema/profile.schema.yml`](../vesperprofiled-config-schema/schema/profile.schema.yml). 2. **Vendor/OEM default** — `/vendor/etc/pawletcache/policy.json`. Same file shape, read-only, set at build time. Lets a device builder ship a