How abhisheksingh407/aiagentsample works
Holdline turns a clerk’s shipment-review request into an evidence-linked disposition: the API coordinates policy, shipment, and disposition specialists, which consult shipment records through MCP, then records the review through Receiving in a durable ledger. Reviews can also be queued for a Celery worker. Optional model wording explains validated findings but cannot alter the Python-rule disposition. The README documents these service boundaries; implementation beyond the excerpts was not inspected, so documented links use README evidence.
Components 12
Review orchestration
- Review API
- Model provider
Specialist services
- Policy specialist
- Shipment specialist
- Disposition specialist
Queued processing
- Redis queue
- Celery worker
Evidence and records
- Shipment MCP
- Shipment records
- Receiving service
- Review ledger
Other components
- Clerk or client
Connections 15
- Clerk or client → Review API: submits review
README.md - Review API → Policy specialist: requests policy
README.md - Review API → Shipment specialist: requests shipment
README.md - Review API → Disposition specialist: requests disposition
README.md - Policy specialist → Shipment MCP: reads records
README.md - Shipment specialist → Shipment MCP: reads records
README.md - Shipment MCP → Shipment records: reads shipment data
README.md - Review API → Receiving service: records review
README.md - Receiving service → Review ledger: writes review
README.md - Review API → Redis queue: queues request
README.md - Celery worker → Policy specialist: requests policy
README.md - Celery worker → Shipment specialist: requests shipment
README.md - Celery worker → Disposition specialist: requests disposition
README.md - Celery worker → Receiving service: records review
README.md - Review API → Model provider: requests wording
README.md