boluopai.Delivery and ownership
Resolve the actual environment rather than importing another host's directory layout or deployment process. This package supplies a method, not an installer.
Distinct planes
| Plane | Question and evidence |
|---|---|
| Semantic source | Which maintained text owns this meaning? Read that source and its ownership rules. |
| Package or projection | Which resources and transformations reach the target? Inspect package closure and generator inputs. |
| Discovery and enablement | How does this consumer find and select it? Inspect its current catalog or declared discovery configuration. |
| Installed runtime | Which exact entrypoint and resources can the consumer retrieve? Read them through the consumer's actual route. |
| Invocation and behavior | Was it selected, applied, and effective in the relevant task? Inspect attributable task evidence. |
A source, archive, example, or test copy is active only when a current consumer is configured or instructed to discover it and can read it. A matching name, repository presence, or enabled import does not establish installation on another host. Resolve project-local and shared scope independently. Native settings and permission owners retain their authority.
Package and publish
Identify the source owner and intended consumers before editing. For imported material, preserve rights and attribution; place semantic adaptations in an explicit maintained derivative or overlay rather than presenting changed text as an untouched upstream copy.
Keep discovery metadata specific to the capability and situations it serves. Make the entrypoint a useful router, and include resources required for the selected method. Resolve local references within the complete package. For a dependency outside it, verify that the consumer can discover and access that dependency, provide a self-contained alternative, or state the access boundary. Do not infer a sibling Skill's availability from its mention in a source.
Use the existing publisher, installer, or host-supported interface. Inspect its current contract and read back the persisted target; avoid inventing a second updater or mirror. Publication to different consumers may require distinct packages when their role, tools, or scope actually differs. Advisory and execution roles do not become identical because their files share a name.
For a rename, merge, migration, or retirement, inventory affected discovery, references, manifests, generated targets, wrappers, and runtime copies. Establish and read back the successor, update consumers through the owning interfaces, then retire obsolete active routes. Preserve inert archives when they serve recovery. Avoid two active semantic owners for the same capability.
Maintain corresponding editions
When a changed source has an explicitly mapped public or other consumer edition, identify that edition's owner, audience, role, scope, and resources. A matching name does not establish this relationship or justify creating a new edition. Compare materially changed purpose, invocation conditions, interfaces, methods, and resources against each actual consumer's needs.
An independently authored edition requires semantic adaptation: carry portable material improvements to its source within the authorized maintenance scope, while preserving private information, environment-specific responsibilities, rights, and actual authority boundaries. Distinct advisory and execution roles may need different wording. A local-only change may leave another edition unchanged; explain that judgment when material to completion. Close required edition updates rather than stopping at one consumer's installation.
A deterministic projection instead uses its existing generator. A website's cached reading copy follows its owning publication route; it is not a live view of local files. Use the existing package and publication owners, maintaining revision, version, and change metadata where their actual contracts require it. Verify the relevant published package and consumer readback. Source presence, publication, retrieval, and observed use remain distinct evidence. This does not call for another updater, scheduler, or edition registry.
Readback and recovery
Verify the intended consumer's discovery, entrypoint retrieval, supporting resource retrieval, and relevant tool prerequisites. A source hash or successful archive build supports those limited claims, not runtime availability. When host access is unavailable, report the exact unverified plane and keep source or package readiness separate from an installation claim.
Bind recovery to the actual changed source and deployment route. Preserve the prior working state where recovery cost warrants it; use the existing history or publisher rather than creating another version store. Read back an uncertain mutation before retrying, so a transport error does not cause duplicate work.