Luka Killner

Luka Killner, selected work

Selected work

Four projects

01 / 04Running on invented data

Luka, a governed multi agent analyst

Ask a question in plain English. A planner scopes it, a data agent pulls the rows, a builder writes the answer, and an independent reviewer blocks any figure that does not trace back to source. Nothing reaches the screen until it passes. The demo below is interactive: click a question.

Luka Demo dataset Sample Retail Business
Demo dataset, fictional data
New chat

Luka

Ask anything about the sample retail business below. Luka will pull the numbers, write a summary, and chart what matters.

Pick one of the four questions to run the demo

Agent trace

  1. Plannerwaiting
  2. Data agentwaiting
  3. Builderwaiting
  4. Reviewerwaiting

Sent back to builder

Output is held until the reviewer passes it

Powered by Claude
Rebuilt interface, invented data, faked entirely client side. Four questions, four shapes of answer, one of them a refusal. The reviewer rejection on the first question is the moment worth watching, and it is the reason the rest of the answer can be trusted.
My part
A potential product I designed. The four agent roles and their instructions, the grounding rules and the interface.
Data
An invented sample business. No employer or client data anywhere in it.

02 / 04Delivery operating modelGeneric examples

Agentic Workflows and Standards

The operating model for how delivery work is built and signed off. Skills, agents and hooks carry the rules into the tooling, with one context per account, and it has been adopted across the business. Every workflow is drawn from trigger to a named person’s yes.

01Business functionDeliveryCalls, weekly status and getting work out of the door.Locked3workflows 02Business functionEngineeringTickets, shared models and keeping the standards in step.Locked3workflows 03Business functionData engineeringPipelines, mappings and read-only extracts.Locked2workflows 04Business functionData scienceSegmentations and scoring models, checked before use.Locked2workflows 05Business functionManagerial decision agentsTurning what leadership asks into standards every review uses.2workflows 06Business functionSecurityTools assessed before adoption, and the data protection pack.Locked2workflows 07Business functionOnboardingNew accounts and new starters, set up so nothing is missed.Locked2workflows 08In practiceHow this works in practiceAn LLM with an agent for each workflow, as well as the automated ones running.

03 / 04Multi tenant product, client facing

The portal users sign in to

Deployed inside an internal environment or within a client's own environment.

Locked

Portal · prototype demo

Ask for access or unlock
The prototype, made before the real portal was built, with an invented tenant and invented counts. The sign in is the part that carries the architecture: the identity is the client's own, nothing is typed here, and what loads afterwards is decided by the tenant the account belongs to.
My part
Sole developer. Specification to production, and it is live with more than one client rather than built once. Identity, tenancy, authorisation and every surface in it.
Stack
Next.js on a managed platform, enterprise identity for sign in, and a multi tenant architecture rather than a deployment per client.
Users
Client side and internal, live with more than one client and built to be rolled out to the next one rather than rebuilt for them.

04 / 04Concept, for client use

Service Desk & Booking

A service assistant that turns a problem typed in chat into a routed ticket with the evidence attached, then books the call to fix it against real free time. The model reads and writes the conversation; every action goes through a tool that checks before it commits.

Contact

Get in touch

For a conversation about the work, or access to the locked workflows.

killner.luka@gmail.com

Every interface on this site is rebuilt here in HTML and SVG with invented data. Nothing is a screenshot, no figure is a client figure, and no client or employer is named.