[email protected]
AI workflow automation — initial inquiry We're looking to automate our claims processing pipeline. Do you have experience with…
Apr 3
[email protected]
Business Requirements — Draft v1 Please review the attached BRD. Goals, scope, constraints, and acceptance criteria…
Apr 7
[email protected]
PRD + ADR-001 ready for review PRD finalised. ADR-001 covers the event-driven architecture decision. SHACL shapes…
Apr 14
[email protected]
Ontology & workflow spec — delivered Domain ontology (TTL) and workflow spec (YAML) are attached. Ready to build.
Apr 18

Business Requirements — Draft v1

From: [email protected]  ·  To: [email protected]  ·  Date: April 7, 2026

Goals

  • Reduce manual claims review time by 60%
  • Zero false-rejection rate for compliant claims
  • Full audit trail for regulatory reporting

Scope

  • Ingest: PDF + structured JSON claims
  • Validate: business rules engine against policy TTL
  • Classify: ML model (binary + confidence score)
  • Route: auto-approve / queue / escalate

Constraints

  • GDPR Art. 22 — no fully automated decisions on contested claims
  • Data must remain in EU-West (Helsinki region)
  • Integration with existing Temenos T24 core system

Acceptance criteria

  • < 200ms decision latency at p99
  • 99.9% uptime over rolling 30 days
  • All decisions logged with input hash + model version
Engagement Tracker
Happy Bank — AI Claims Processing
Discovery → Spec → Build
April 2026
BRD
Delivered Apr 7
PRD
Delivered Apr 14
ADRs
1 decision locked
Ontology
Delivered Apr 18
Deliverables
DocumentStatus
Business Requirements (BRD)Delivered
Product Requirements (PRD)Delivered
ADR-001: Event ArchitectureDelivered
Domain Ontology (TTL)Delivered
Workflow Spec (YAML)Delivered
Scope
ItemValue
Decision latency (p99)< 200ms
Uptime SLA99.9%
Data residencyEU-West
ComplianceGDPR Art. 22
Spec complete — ready to build
Updated Apr 18
workflow.yml
Run
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
# Claims Processing Workflow — Happy Bank AI
# aktagon.com · April 2026
name: claims-processing
version: 1.0.0
trigger:
  type: http
  path: /claims/submit
steps:
  - id: ingest
    type: parse
    input: $.claim_payload
    schema: schemas/claim.json
  - id: validate
    type: rules-engine
    rules: rules/happy-bank-claims.ttl
    on_fail: route_to_review
  - id: classify
    type: ml-inference
    model: models/claims-classifier-v2
    threshold: 0.92
  - id: route
    type: conditional
    conditions:
      - if: $.classify.score > 0.92
        then: auto_approve
      - if: $.classify.score < 0.40
        then: auto_reject
      - else: queue_for_review
  - id: notify
    type: webhook
    url: ${TEMENOS_WEBHOOK_URL}
    payload: $.route.decision
# GDPR Art. 22 — contested claims bypass auto_reject
# and are always routed to queue_for_review

One conversation. No handoffs.

You talk to the person who researches, designs, automates, and deploys. Same person. Start to finish.

Tell me what needs to ship.