acgs-deliberation
Deliberation, HITL orchestration, consensus, and impact routing for ACGS agents.
acgs-deliberation is the extraction-friendly deliberation package for the ACGS runtime.
Today it re-exports the stable surface from enhanced_agent_bus.deliberation_layer, so
you can start using the standalone import path now without waiting for the full source
move.
Installation
acgs-deliberation supports Python 3.11+.
pip install acgs-deliberation
Quick Start
from acgs_deliberation import Vote, VotingService, calculate_message_impact
from enhanced_agent_bus.models import AgentMessage, MessageType, Priority
message = AgentMessage(
from_agent="planner",
to_agent="compliance",
message_type=MessageType.COMMAND,
priority=Priority.HIGH,
content={"action": "deploy", "target": "payments"},
)
voting = VotingService(force_in_memory=True)
election_id = await voting.create_election(
message,
participants=["security", "risk", "compliance"],
)
await voting.cast_vote(
election_id,
Vote(agent_id="security", decision="APPROVE", reason="controls in place"),
)
decision = await voting.get_result(election_id)
impact = calculate_message_impact(message.to_dict(), {"environment": "production"})
Redis-Backed Voting
from acgs_deliberation import get_redis_voting_system
redis_voting = get_redis_voting_system()
Key Features
- Voting primitives including
VotingService,Election,Vote, andVotingStrategy. - Event-driven collection via
EventDrivenVoteCollector,VoteSession, andVoteEvent. - Deliberation queue support with
DeliberationQueueandDeliberationTask. - Optional Redis-backed queueing and voting primitives for distributed deployments.
- Impact scoring and GraphRAG context enrichment hooks for review routing.
Package Relationship
- Install name:
acgs-deliberation - Import namespace:
acgs_deliberation - Runtime dependency:
enhanced-agent-bus>=3.0.0
License
AGPL-3.0-or-later. Commercial licensing is available; contact hello@acgs.ai.
Links
Constitutional Hash: 608508a9bd224290
Metadata
Release files for acgs-deliberation 0.1.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 | Actions |
|---|---|---|---|---|
| acgs_deliberation-0.1.1.tar.gz | 3.5 kB | Without provenance | Details for acgs_deliberation-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| acgs_deliberation-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for acgs_deliberation-0.1.1-py3-none-any.whl |
Total release size: 6.9 kB
Release files / acgs_deliberation-0.1.1.tar.gz
| Download URL | acgs_deliberation-0.1.1.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
980f11a50d38f55e2811d446cfaabde5ae1ff4e7ede7387e1c40b492d99ae819
|
|
BLAKE2b-256 checksum How to use checksums |
515c6c21981b17c2957e0550652dcb2311360f4515867f8600e6d4dfb718f523
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / acgs_deliberation-0.1.1-py3-none-any.whl
| Download URL | acgs_deliberation-0.1.1-py3-none-any.whl |
|---|---|
| Size | 3.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a2fd2dc171f99d8fa8c28d4e58a715fd7654fcb7c1a4f16406307e90d571053
|
|
BLAKE2b-256 checksum How to use checksums |
14426b95e2872bb4a2ecc56ae94091b42c0acd2014069a25de6be6ac52c92849
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for acgs-deliberation 0.1.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.
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.