cf-install-services
cf-install-services owns semantic service operations for profile installation, profile transition, instance inspection and repair, semantic-source registration, and uninstall preparation. It runs after the bootstrap instance has accepted service handoff.
Operations are described in package-local TriG and invoked through the universal cf.service.call.v1 request and cf.service.result.v1 result envelopes. Principal inputs include the accepted profile, checkout, target Python, bootstrap plan, handoff receipt, and lifecycle-specific authority data. Outputs are deterministic previews, transaction receipts, inspection reports, and applied lifecycle results.
The package validates accepted digests and instance authority before mutation, separates preview from apply, preserves unrelated semantic sources, and delegates target transaction mechanics to the installed instance authority. It does not plan bootstrap, resolve or download artifacts, create the initial target environment, provide terminal presentation, or own runtime process startup.
Initial profile installation can begin before the production graph is available. Its operation and executor discovery therefore works from installed/local semantic documents and explicit Python execution affordances; steady-state service calls use the installed service plane after handoff.
1 maintainer
Metadata
1 maintainer
Release files for cf-install-services 0.1.17
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cf_install_services-0.1.17-py3-none-any.whl | Python 3 | none | any | Details for cf_install_services-0.1.17-py3-none-any.whl |
Release files / cf_install_services-0.1.17-py3-none-any.whl
| Download URL | cf_install_services-0.1.17-py3-none-any.whl |
|---|---|
| Size | 55.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ddd53e62a73b138d992de56786efd199440704caedb494bbc0c4ea421919a6b8
|
|
BLAKE2b-256 checksum How to use checksums |
935e56d74996c47c8920091c6df2644a876afc5041e3558a74f5509a5426c337
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.3
|
Security for cf-install-services 0.1.17
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
