OMP profiles
What a profile actually is, which fields OOMPF reads, and where the runtime authority stays.
Profiles get passed around as screenshots and half a YAML file. OOMPF indexes them from public GitHub Gists, shows the facts —models, providers, advisors, hooks, prerequisites— and hands back a command that installs the profile natively.
oompf publish daily-driver ✓ gist gist.github.com/alice/cfcdad13… ✓ indexed oompf.run/p/prof_00e08f39…oompf add https://oompf.run/p/prof_00e08f39… ✓ installed ~/.omp/profiles/alice-daily-driveromp --profile alice-daily-driver
OOMPF documents the shareable profile format. OMP remains the authority for how a profile behaves once it is installed.
What a profile actually is, which fields OOMPF reads, and where the runtime authority stays.
Turn a local profile into a public Gist, scan it for secrets, and register its metadata.
Install someone else's profile by its OOMPF URL, and what happens when the name collides.