Repository navigation
Permissions and Preflight
Permissions are scoped to the target host. The format transports declarations; YLPlugin does not assign built-in meanings to bits, byte positions or names.
required_permissions = ["save", "custom.feature"]required_permissions = { format = "bitmask", registry = "xyz.example.bits", registry_version = "1", value = 37 }required_permissions = { format = "bytes", registry = "xyz.example.bits", registry_version = "1", values = [37, 8, 255, 0] }Each required/optional declaration chooses one representation. Strings are unique and nonempty. Integer masks are exact integers from 0 through 9223372036854775807. Larger masks use up to 8192 numeric bytes. Values are not strings/floats/bools. Byte i contains bits 8i through 8i+7, least significant bit first. C/C++ and bindings expose actual byte buffers.
A host advertises supported representations. For bit/byte masks it also advertises the exact registry version. A similarly named registry with a different version is insufficient. Required grants are supplied under the target ID using the matching representation; declarations do not create grants.
For example, the data fixture's analysis target requests the maximum signed-64 mask. A JS host must preserve it as bigint; a number would lose bits. Java uses Long and Python exact int. The viewer target requires no permissions; its optional byte declaration demonstrates representation negotiation without authorizing those optional operations automatically.
Preflight checks host/API, runtime/version, OS/architecture/ABI, capabilities,
permissions, signature policy, content keys, extraction and budgets. Exact host
matches outrank generic targets; generic matching requires explicit opt-in.
Priority then lexical target ID determine deterministic ordering. fallback=false
can stop selection before lower-ranked candidates.
| Status | Interpretation |
|---|---|
| SUPPORTED | Declared requirements match host state |
| UNSUPPORTED / UNSUPPORTED_PROFILE | Target or profile cannot be used |
| NEEDS_RUNTIME | Required runtime is absent or outside bounds |
| NEEDS_PERMISSION | Host grant is missing/inadequate |
| NEEDS_LICENSE | Content key/entitlement unavailable |
| NEEDS_EXTRACTION | Required strategy is not allowed by the host |
| RESOURCE_LIMIT / UNKNOWN | Budget is insufficient or required budget is unknown |
| INVALID_SIGNATURE / INVALID_CONTAINER | Trust/validation failure |
Inspect reasons and candidate details rather than treating all non-SUPPORTED results identically. A positive report does not itself execute code or promise that a separately supplied adapter behaves safely. Read the normative profile and Host Integration.
YLPlugin · Repository · Releases · Issues · Support · LGPLv3 · Maintained by Cavanshirpro.
Release guide 0.1.3; source development 0.1.4; later features are tracked in the roadmap. Normative contracts: container and profile.