Giuseppe CastelluccioIT technician, self-taught
Capo d'Orlando (ME)Province of Messina, or remote
Looking for workIT support
IT

Projects

What I've built.

Eight things, in two groups worth keeping apart. The first three I use myself, daily. The other five are businesses I invented, one per trade, built to show you how far this goes.

01Kira

Kira: the cli screenKira: the commands screenKira: the overview screenKira: the models screenKira: the benchmarks screenKira: the finetune screen
screens taken off the screen

Kira

A coding agent that runs locally.

You give it a model between 7B and 20B that you run yourself. It reads code, edits it with real tools, runs commands inside a sandbox, checks its own work and remembers what it learned. The code stays on the machine until you point it at a cloud endpoint. Whether a small model is good enough for everyday work, I still do not know. The README says as much.

Status
in development · MIT · ~2,400 tests
What you see
Six real screens. The CLI first, because Kira is the CLI. Then the hub, which watches it work. Taken off my own machine while it ran.
The code

02Kairos

Kairos: the automazioni screenKairos: the calendario screen

contents withheld

the two screens with no third-party data

Kairos

The panel I run the work from.

Five screens. Home, leads, work, calendar, automations. I open them forty times a day, so they have to stay out of the way. I keep enquiries and projects in there. I wrote it myself and I have used it for months.

Status
in use · private
What you see
Two real screens: the automations and the calendar. The other three — home, leads, work — show real people’s names and contact details, so in their place is the drawing of the structure, measured from the real panel.

03Orpheus

Orpheus: the control room screenOrpheus: the renders screenOrpheus: the analytics screenOrpheus: the render #358 screen
archived · real screens

the chain, from idea to file

  1. Research
    research
  2. Assert research
    assert_research
  3. Create
    create
  4. Assert quality
    assert_quality
  5. Confirm
    confirm
  6. Council
    review
  7. Deliver
    deliver
Each box is a directory in the project. An idea goes in at the left and comes out as an edited video. Second from the end, a council of models watches the render and decides whether it passes — the chain judges itself before anything ships.

Orpheus

Generated reels, from idea to finished video.

Makes short AI-generated videos. You start with an idea and end with an edited file, and I touch nothing in between. It was an experiment in how much of that chain could come out. The answer was almost all of it, and then I archived it.

Status
archived
What you see
Four screens of the panel, taken while it ran. The control room, the render history, the numbers, and one render opened with its whole chain. The chain is below it.

04Demo sites

Five trades, five identities that share nothing.

None of these is a client. I invented five businesses, one per trade, and gave each of them their own colour, their own voice and one tool that does a real job. I built them so I would have something to show instead of something to claim.

The names, places, prices and reviews are invented for demonstration. None of these businesses exists, and none of these pages is online.

None of the five is online; they run on my own machine. The day one goes up, its card in the window above becomes a link.

This is how far it goes, today.

Not a catalogue of things I sell: it is what I can build and keep running, put somewhere it can be checked. The code is readable, the tests run, and the machines with my work on them are still up.

Write to me