Progull is early. This page collects design notes, engineering updates and calls for design partners — not customer wins, funding rounds or attested audit reports.
Everything below is written by the founder and reflects the current state of the build. It will be replaced with real deployment evidence once we have design-partner results to share.
Why a small, senior team is spending the next 12 months building the reasoning loop before onboarding any live production customer.
Early development happens entirely against synthetic datasets in a sandboxed Hercules z/OS emulator. Here is how we set it up and what it lets us prove.
Advisory, Approval and Autonomous — the three tiers we are building into the platform from day one, and why full autonomy is opt-in per abend family.
A centralized orchestration layer paired with subsystem-specific agents — JCL Agent, Db2 Agent, CICS Agent — behind a risk-based human-in-the-loop gate.
Following the 12-month build, we plan to onboard a small number of design-partner sites for a 6-month pilot at no charge. What we ask, what we bring.
Interested in the design-partner cohort, or curious how Advisory mode would look against your fleet? Write to zeeshan.afzal@progull.com.