Code Craft AI Landscaping
The codecraftai-landscaping package provides the topology model and device-discovery framework that ccai tests and automation tools use to reason about the machines, clusters, and services under test. A Landscape aggregates the devices declared by configuration, organises them through integration layers, and exposes them through friendly identifiers so that tests can address resources by role rather than by raw hostnames or IP addresses. It builds on codecraftai-foundations, codecraftai-interop, and codecraftai-credentials, and is typically consumed by higher-level orchestration packages.
Highlights
AutomationPod as the configuration-coupled entry point to the global Landscape.
CoordinatorCoupling subclasses that attach protocol- or service-specific coordinators (SSH, serial, VMware vSphere, DLI power, Raspberry Pi clusters, and more).
Client, service, and cluster base classes under clients/, services/, and clusters/ representing managed devices.
Pluggable coordinators for discovering and wiring devices of a given type.
Extension hooks under extensions/ for downstream packages such as codecraftai-interop-ext-upnp and codecraftai-interop-ext-tasker.
Repository Structure
development/ - Runtime environment scripts.
repository-setup/ - Repository homing and setup scripts.
source/packages/ - Package source code.
source/testroots/ccai/ - TestBase test roots.
specs/ - Requirements, design, and task documentation.
userguide/ - Standards, conventions, and documentation.
Environment Setup
When working in a Codex container:
./development/setup-agent-containerFor local development:
./repository-setup/rehome-repository
./development/setup-envrionmentRunning Tests
Activate the virtual environment:
source .venv/bin/activateRun the single-host test suite:
testbase testing run --root source/testroots/ccai --includes=ccai.tests.landscaping.singlehost --output=./.outputStandards and Conventions
Naming conventions: userguide/10-02-naming-conventions.rst
Code organization: userguide/10-01-code-organization.rst
Coding standards: userguide/10-00-coding-standards.rst
Additional Resources
User guide entry point: userguide/userguide.rst
Design documentation: specs/design.md
Requirements: specs/requirements.md
1 maintainer
Metadata
1 maintainer
Release files for codecraftai-landscaping 1.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| codecraftai_landscaping-1.3.1.tar.gz | 105.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codecraftai_landscaping-1.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 308.9 kB
Release files / codecraftai_landscaping-1.3.1.tar.gz
| Download URL | codecraftai_landscaping-1.3.1.tar.gz |
|---|---|
| Size | 105.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a6d2db32d9687fe65eb5ba8529a722c8e60394586d81790210f4ad48d267a993
|
|
BLAKE2b-256 checksum How to use checksums |
95503bc856cf9016754858780413f1f78631f4aeb49e53487f85e8e41e86f944
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / codecraftai_landscaping-1.3.1-py3-none-any.whl
| Download URL | codecraftai_landscaping-1.3.1-py3-none-any.whl |
|---|---|
| Size | 203.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a9854229a714d6fa4e409ef19615bfbc65fbba02b3bc5e0861d48a3c3af9d05f
|
|
BLAKE2b-256 checksum How to use checksums |
72f3ad4c7e87ec392565c49974f16a40ab733b9978f1033d86cc8a23d869f194
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for codecraftai-landscaping 1.3.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for codecraftai_landscaping-1.3.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA 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.
