Lukas Dabkowski
Menu

Decisions and evidence

Architecture & Documentation

I communicate architecture through assessable decisions and delivery evidence: current and target states, boundaries, plans, controls, implementation artifacts, operational guidance, and validation material. The public examples below are reconstructed from approved case content and preserve each engagement’s delivery boundary.

Architecture approach

The work starts by making the present state, intended outcome, dependencies, responsibilities, and evidence needs explicit.

  1. Assess the current state and identify technical, security, identity, connectivity, and operating constraints.
  2. Define a target state with clear system boundaries, implementation scope, ownership, and migration dependencies.
  3. Treat resilience, least privilege, validation, and human approval as design inputs where they are material.
  4. Record decisions and evidence so implementation teams and reviewers can inspect the reasoning and remaining limits.

Decision-making & trade-offs

Architecture decisions become useful when the alternatives, consequences, and delivery status remain visible.

Proof of concept or hardened production

The multi-agent implementation proves orchestration, structured outputs, infrastructure code, logging, and tests while keeping production hardening outside the evidenced scope.

Enterprise Agentic AI Architecture & Prototype

Documentation & evidence

The artifact set varies by engagement. These are supported deliverable families, not a claim that every item exists for every project.

  • Architecture decisions, high-level and detailed design material
  • Current-state assessments and target-state documentation
  • Migration assessments, dependency maps, waves, validation, and rollback guidance
  • Control and policy definitions with exception and qualification evidence
  • Infrastructure code, tests, implementation guidance, and technical workshop material
  • Runbooks, operational guidance, audit trails, and evidence journals

Professional Work

Professional Work examples

A curated set of reconstructed diagrams from the case studies shows how scope, sequence, approval, and delivery ownership are made inspectable.

Human-gated time-record workflowCalendar events move through normalization and live catalog validation into a reviewable plan before a narrowly scoped draft write.
  1. Calendar sessionImplemented
  2. Event normalizationImplemented
  3. Mapping memoryImplemented
  4. Live PSA validationImplemented
  5. Draft planImplemented
  6. Human confirmationHuman approval
  7. Scoped draft writeImplemented
  8. Post-write verificationImplemented

No submit · No approve · No generic write tool

Open case study: Agentic AI Time Tracking Assistant for Enterprise Workflows

Regulated policy-as-code lifecycleRequirements and classification lead to control profiles, automated infrastructure checks, reviewable evidence, governed exceptions, and enablement.
  1. RequirementsImplemented
  2. Workload classificationImplemented
  3. Control profilesImplemented
  4. Policy as codeImplemented
  5. IaC / CI validationImplemented
  6. Findings and evidenceImplemented
  7. Exceptions and rolloutImplemented
  8. EnablementImplemented

Classification determines the applicable profile; evidence and exceptions remain reviewable.

Open case study: Policy-as-Code and Compliance Engineering for Regulated AWS Workloads

Multi-region recovery architectureA primary serverless region connects through replication and recovery controls to a secondary region, with design and delivery responsibilities identified.
  1. Primary regionDesigned
  2. Traffic routingDesigned
  3. ReplicationDesigned
  4. Recovery controlsDesigned
  5. Secondary regionImplemented by delivery team
  6. Architecture oversightDesigned
  7. Delivery teamImplemented by delivery team

Architecture by Lukas; implementation by the cloud engineering delivery team.

Open case study: Multi-Region Disaster Recovery Architecture with Implementation Oversight

Oracle-to-PostgreSQL migration designOracle workloads move through compatibility assessment and a staged migration approach toward managed PostgreSQL, with operational design and team enablement alongside.
  1. Oracle sourceDesigned
  2. Compatibility assessmentDesigned
  3. Migration approachDesigned
  4. RDS PostgreSQLDesigned
  5. Security and resilienceDesigned
  6. OperationsDesigned
  7. DB-team workshopHuman approval

The workshop supported technical confidence and shared alignment; implementation remained with the delivery teams.

Open case study: Oracle-to-Managed-PostgreSQL Migration Architecture

Synthetic Reference Architecture · Not client work

Reference / Lab

A detailed secure enterprise Agentic AI reference architecture is reserved for a newly created, bilingual artifact with its own text equivalent and review. Its intended method separates model reasoning from deterministic enforcement and covers capability-scoped tools, authorization, least privilege, human approval, validation, execution limits, provenance, and auditability.

Public reconstruction & confidentiality

Public diagrams are newly reconstructed abstractions. They demonstrate architecture reasoning without reproducing confidential client documents, identities, systems, values, or operational evidence.