alissa-tools-github-orcloop
The alissa.tools.github.orcloop module: the orchestrator daemon of the
Alissa GitHub daemon family. It walks the Alissa task graph, releases tasks
marked ready as alissa:develop issues, and closes the loop when the resulting
PR merges — sitting one level above
alissa-tools-github-devloop
(which turns those issues into developer sessions) and
alissa-tools-github-reviewloop
(which reacts to the review requests those developers fire).
This distribution ships only that module. Everything above it —
alissa, alissa.tools, alissa.tools.github — is a
PEP 420 namespace package with no
__init__.py, so other distributions in other repositories can contribute
their own packages under the same namespace:
alissa/ ← namespace (no __init__.py)
└── tools/ ← namespace
└── github/ ← namespace
├── orcloop/ __init__.py ← THIS distribution
├── devloop/ __init__.py ← ships from alissa-github-develop-daemon
└── reviewloop/ __init__.py ← ships from alissa-github-review-daemon
The rule: a distribution owns a leaf package and declares only that subtree
(find_namespace_packages(include=[PACKAGE, f"{PACKAGE}.*"])). Adding an
__init__.py at any namespace level would claim it for one distribution and
shadow the others.
Status
The daemon is live: the config surface (O1), the Alissa/GitHub clients and the
release ledger (O2), and the decision loop — both the release and close edges
(O3) — are all in place, driven by the alissa-orcloop CLI. The repository
README carries the end-to-end documentation: the pipeline role, the
Autonomous-Dev / Autonomous-Scope marker contract, both decision matrices,
the full ALISSA_ORC_* configuration surface, and the escalation catalog.
Packaging the daemon as a container image (O5) is the remaining lane. The
reserved runtime env prefix is ALISSA_ORC_*.
Install
pip install -e ./alissa-tools-github-orcloop
alissa-orcloop --version
License
Licensed under the
Apache License, Version 2.0. The
sdist and wheel ship that license and a NOTICE file with them, and both land
in the installed distribution's .dist-info/.
"Alissa" and "Fahera" are trademarks of CORE FAHERA ENTERPRISE HOLDINGS S. DE R.L. and are not covered by the license — it grants no permission to use them.
1 maintainer
Metadata
1 maintainer
Release files for alissa-tools-github-orcloop 0.18.19
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 | |
|---|---|---|---|---|
| alissa_tools_github_orcloop-0.18.19.tar.gz | 471.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| alissa_tools_github_orcloop-0.18.19-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 957.7 kB
Release files / alissa_tools_github_orcloop-0.18.19.tar.gz
| Download URL | alissa_tools_github_orcloop-0.18.19.tar.gz |
|---|---|
| Size | 471.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1b9152d0c88d2801c12745cb956aad94ac01b97f7f1636d8c1747c38c276dd5c
|
|
BLAKE2b-256 checksum How to use checksums |
df77eb3e2cc9575db42b3974e26e417a784f6f0c53dad00579f02d9205b976da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Release files / alissa_tools_github_orcloop-0.18.19-py3-none-any.whl
| Download URL | alissa_tools_github_orcloop-0.18.19-py3-none-any.whl |
|---|---|
| Size | 486.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44519ddf12260b569ba19c492232b8910bdc35c8e362c2fe24779f5ec0fb1f3d
|
|
BLAKE2b-256 checksum How to use checksums |
7966e2a2913e9bf1480d8f6054dbcbac860fbc8fe37a53d30fe47d85b7303d0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Security for alissa-tools-github-orcloop 0.18.19
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.
