Trigger
API · event · schedule
TECHNICAL ARCHITECTURE
One durable execution pipeline.
A shared LangGraph runtime coordinates domain agents, tools, policy gates, resumable state, human decisions, artifacts, and pull-request delivery.
REFERENCE ARCHITECTURE
Every generated change gets boundaries and custody.
Context
Repository · specs · knowledge
Execute
Domain graph · tools
Verify
Security · quality · policy
Approve
Interrupt · human decision · resume
Deliver
Branch · pull request · release
PostgreSQL resumable checkpointsRedis + Celery async coordinationMinIO / S3 reports, logs, and diffsLangSmith execution tracing
RUNTIME BEHAVIOR
Durable state makes agents recoverable.
The same state machine handles execution, approval waits, retries, errors, and completion without losing tenant or run context.
01InitializeCreate run identity, tenant context, inputs, and trace
02ExecuteRun domain nodes and collect findings, tool results, and artifacts
03CheckpointPersist JSON-serializable state in PostgreSQL
04ApproveInterrupt before consequential action and resume with the decision
05FinalizeAggregate results, record lifecycle, and clean completed checkpoints
RBACTracingRetriesArtifactsErrorsWebSockets
DOMAIN AGENT ARCHITECTURE
Shared runtime. Specialized graphs.
Delivery + Change
Specifications, implementation, verification, drift, pipeline hardening, security analysis, approval, PR, and deployment tracking.
Operations
Topology-aware telemetry, proactive detection, root cause, generated runbooks, cloud cost changes, and RTO/RPO validation.
Assurance
Requirements-derived testing, coverage, database and data-quality analysis, plus model usage, security, cost, and compliance reporting.
INTEGRATION BOUNDARIES
Adapters keep the core decoupled.
Typed clients normalize provider differences at the boundary while agent state, workflow semantics, approval, and evidence stay stable.
Source + Pipelines
GitHub · GitLab · Bitbucket · Jenkins · CircleCI · Azure DevOps
Cloud + Infrastructure
AWS · Google Cloud · Azure · Terraform · OpenTofu · Kubernetes
Telemetry + Incidents
OpenTelemetry · Datadog · Dynatrace · New Relic · PagerDuty
State + Artifacts
PostgreSQL · Redis · MinIO · S3 · pgvector
Work + Notifications
Slack · Jira · Linear · GitHub Issues · Teams · ServiceNow
SECURITY ARCHITECTURE
Controls preserve the chain of custody.
Execution
Every AI action is tied to a timestamp, user, model, run, and change record; evidence can route to SIEM.
Identity
Tenant boundaries, granular RBAC, least privilege, SAML 2.0, and OIDC support named decisions and overrides.
Decisions
Versioned policy-as-code gates enforce GDPR, HIPAA, PCI-DSS, SOX, security, quality, cost, and reliability rules.
Evidence
Runs, findings, decisions, artifacts, PRs, releases, deployments, and rollbacks map to internal controls.
DEPLOYMENT + ADOPTION
Start read-only. Expand under explicit control.
Select the wedge
Choose Guard, IaC, CI/CD, AppSec, or an operations workflow with a named owner.
Connect safely
Use least-privilege credentials for repository, cloud, telemetry, pipeline, and ticketing adapters.
Define controls
Version checks, approval thresholds, release policy, deployment evidence, and rollback expectations.
Run the pilot
Begin read-only or proposal-only, validate outcomes, then enable branch and PR delivery.
Evaluate NeilaOps in your stack.
Validate runtime, state, security, integrations, approval semantics, evidence, and PR delivery on one governed workflow.