HOW THIS SITE WORKS
This site is a working demonstration. Cecil, the AI secretary on the landing page, is a prompt-only agent: one language model, one carefully written brief, and a set of limits enforced in code. If you are evaluating Vinga's work, the machinery behind this page is part of what is on display.
The agent
Cecil runs on a single system prompt. Everything he knows about Vinga sits in a public dossier inside that prompt - there is nothing hidden behind it. Older turns are summarised as a conversation grows, so long exchanges stay coherent. Conversations are kept for about a day after your last message, then deleted.
The budget
A public AI endpoint can be drained by anyone with a script, so Cecil's day runs on a fixed budget - spend is computed from real API usage on every turn, per conversation and globally. When the day's budget is spent, he retires until tomorrow and the leave-word form takes over. Conversations are budgeted, and Cecil says so plainly when a limit is reached - bounded operating cost is part of the design, not an apology.
Messages
Word reaches Vinga two ways: the leave-word form, and Cecil himself - ask him to pass a message on, and he will. Both write into the same store: a database on a persistent volume holding contact, message, and timestamp. To have a message deleted, write to vinga@skyforge.sh.
The three tools
Cecil has three capabilities beyond conversation. The first is recording a message for Vinga. It is write-only - he can send word out, never read anything back. And it is consent-gated: nothing is recorded unless you ask or agree. If he offers to attach a few lines of his own context to your message, that is separately yours to decline, and he tells you what they will say before anything is sent. The limits are enforced in code, not by asking him nicely: two messages per conversation, daily caps on storage and email.
The archives clerk
The second is a research agent Cecil can send into one of Vinga's public repositories. It is a genuine exploration and takes a few minutes, so it runs only with your consent to the wait. The clerk downloads a fresh copy of the repository at its newest commit, reads it with read-only tools, and returns a report. Cecil relays it with receipts: the file paths become links pinned to the exact commit consulted, so every claim can be checked at its source. An honest "that is not in the repository" counts as a good answer here. One trip per conversation, daily caps in code, and the clerk reads only what anyone could read on GitHub.
Booking a call
The third is the diary. Ask Cecil for a call and he will find real times, hold one while you settle the details, and send a calendar invitation - no scheduling link, no waiting on a reply. He is not guessing: availability is computed from hours Vinga authorised in advance, minus the days she is working, so every yes and every no comes from arithmetic rather than from his judgement. He commits without asking her first because the permission was granted upstream, when she set the hours - and he refuses outside them for exactly the same reason. That refusal is the more interesting half: an agent that acts freely inside a boundary and stops at its edge is the thing worth demonstrating. One booking per conversation, daily caps in code.
What is recorded
When Cecil cannot answer a question about Vinga from his dossier, the question alone is logged. That is how the dossier learns what visitors actually need.
Visits are counted, too: each page request is tallied into a daily, aggregate count - the date, the referring domain (where the visit came from), a rough browser-or-bot label, and a country. We measure our own traffic, first-party. The country is resolved from a local copy of DB-IP's IP-to-Country Lite database (licensed CC BY 4.0). A cookie is set when you start talking to Cecil or hold a slot in the diary; the privacy page describes it.
Testing
Changes to Cecil's brief ship through a behavioural regression suite: scripted visitors run against the real system before anything reaches this page, and the awkward ones are included - rate probes, injection attempts.
Questions about any of this: vinga@skyforge.sh