Compose.

Two tools, one output.

The Configuration Assistant writes a single EntityConfig from a sentence. The App Config Tool assembles a whole application from 10+ archetypes and 8+ composition patterns. This page is a scripted walk-through of both — the output is the same config you would hand-write.

The walk-through

Two scripted flows.

Click through to see the LLM generate the same shape you would type by hand.

Describe the entity

Scripted demo. Pre-filled — edit freely.

What you would have typed by hand

SupportTicketConfig.scala

val supportTicket = EntityConfig(
  name         = "SupportTicket",
  accessMode   = EntityAccessMode.TENANT,
  fragments    = Seq("priority", "status", "assignedAgentId"),
  externalKeys = Seq("ticketNumber"),
  sortKeys     = Seq("slaDeadline"),
).withLifecycle(ticketLifecycle)
 .withFieldTransformer("slaDeadline", DeriveSlaDeadline)
 .withNotifications(
   OnTransition("Assign",  "ticket.assigned"),
   OnTransition("Resolve", "ticket.resolved"),
 )

The assistant is typing the same config you would have typed by hand. Faster, not different. You are free to hand-edit the output — it is ordinary Scala, and your edits survive regeneration.

III

A note

On this page.

The conversations above are canned. They follow the same prompt structure the production Configuration Assistant uses, with the same output shape, but the LLM calls are stubbed so the demo stays fast and reproducible.

The live tools ship in the Functory CLI and the Admin Console; both emit real, committable files into your repository that you can edit, diff and revert like any other Scala source.