Fallen Angel Labs and Waterfall

Secure AI Operations for teams that cannot afford uncontrolled agents.

Fallen Angel Technologies LLC builds private, approval-gated AI workflows with evidence trails, deterministic checks, and client-owned deployment patterns.

waterfall/runapproval gated
pass intake.normalized pass risk.classified hold approval.required: customer_data pass ledger.event_written pass deterministic_checks policy: human approval before external action network: private bind and client-owned deployment result: autonomy with evidence
PrivateNo public ports by default.
LedgeredTasks and events leave evidence.
GatedHumans approve risky actions.
RepeatableWorkflows become product modules.

First sellable offers.

Fixed-scope packages that turn unsafe automation pressure into governed workflows, deployment plans, and evidence-backed operating systems.

Deployment

Client-Owned AI Deployment Blueprint

Private single-tenant deployment plan for organizations that want automation without shared-control risk.

  • n8n and Hermes control plane
  • secret handling
  • backup and handoff runbook
Pilot

Commercial Roofing AI Assistant

Estimate intake, missing-information detection, job-card creation, and follow-up drafts with human approval.

  • mock-data demo first
  • no automatic quotes
  • assumptions ledger

Waterfall is the control plane.

Every workflow is treated as a governed state machine with intake, risk, approval, execution, verification, logging, and handoff.

IntakeForms, inboxes, webhook events, documents, and operator requests.
RiskClassify customer data, production changes, financial, legal, and security actions.
ApprovalStop for human approval before external or high-impact action.
Agent workHermes/JARVIS and bounded workers draft, transform, inspect, and package.
EvidenceChecks, ledger events, artifact paths, and final runbooks.

Fallen Angel Labs builds the prototypes.

The R&D branch turns operational pain into tested workflows before they become Waterfall product modules.

R&D

Prototype discipline

Labs work starts with mock data, scoped tools, deterministic tests, and explicit approval boundaries. No customer workflow becomes production until the control path is proven.

Productization

From one-off build to repeatable kit

When a workflow repeats across customers, it becomes a module with docs, tests, diagrams, runbooks, deployment templates, and support boundaries.

Start with a workflow that is risky to automate blindly.

Best first fits include customer data, estimates, inboxes, CRM updates, file workflows, compliance evidence, and internal copilots with tool access.

Email jarvis@cyiver.tech