TownCloud · build monitor
Meeting Intelligence
Overall progress
2
13 remain · Audio extraction is building
Waiting on you
Nothing right now
Upcoming owner steps are listed below so you can prepare.
Live stages
● Deployed · Both stages run Agenda import (#3). live_rzzo: 19 of 19 checks passed, including creating the Trafalgar Town Council Meeting (26 Oct 2026), now waiting for audio. demo: 16 of 16 passed; no Meeting is stored there.
In flight now
Audio extraction and upload (#4): one Opus 5.5 implementer is building it. It is the only unblocked ticket; transcription (#5) and live progress (#6) follow its merge.
No open pull requests currently. Agenda import (#3) has merged and deployed.
Tickets
Coming up for you
May be needed for #4: R2 uploads need S3-style credentials for each stage. If Alchemy cannot provision them, you may need to create an R2 API token. This is not yet known and is not blocking on you now.
- #5 · Transcription: register an ElevenLabs speech-to-text webhook for each stage, store each signing secret, and approve the first paid Trafalgar run.
- #7 · Watch: spot-check Trafalgar in a real browser.
- #8 · Agenda links: provide the OpenAI key through Cloudflare AI Gateway.
- #10 · Packet keyterms: approve one paid Scribe regression run.
- #16 · Accuracy: approve the paid Scribe and LLM run, estimated at about $0.30.
Worth knowing
- After the #3 deploy, one live_rzzo check initially returned 405; a direct probe and five subsequent runs passed. The previous version briefly answering is a likely but unproven cause. #4 carries a check that waits for the new version.
- The web app’s API passthrough still reads a request body without its own cap; the orchestrator has carried this into #4.
- Separate sign-in limits for two real visitors are still unproven on a deployed stage; this machine has only one outward address. Forged addresses were rejected.
- Four of Trafalgar’s ten attachments are scans without text, and its packet yields few people’s names. Packet keyterms may add little; OCR is out of scope.
- Local tests do not enforce some D1 and Worker limits. Deployed checks are needed after merges.
- Audio extraction worked in Helium, Edge Beta, Chrome Beta and the test browser: 190.8 MB became 13.3 MB in about 21 seconds. Stable Edge and a slower laptop remain untested.
- 12 Nov incident: a reviewer stopped processes by name, risking other local servers. A rule now requires stopping only processes the agent started, by ID.
Decisions
13 Nov · Orchestrator · When a Meeting already exists, say the submitted people were not applied if they differ from the stored list; that statement is always true.
13 Nov · Orchestrator · Declined special handling for a start time in a daylight-saving gap, judged implausible for a Meeting.
13 Nov · Orchestrator · Refuse API request bodies over 4 MiB before sign-in to bound work.
13 Nov · Orchestrator · Keep a short traps file for recurring time-wasters that tests do not catch; rules stay in AGENTS.md. The merged file has 15 entries.
13 Nov · Orchestrator · Keep 32 kbps mono Opus, the bitrate already scored with Scribe; measured audio was 13.3 MB.
13 Nov · Orchestrator · Assume a town’s time zone from its state for import. Split-state towns can be wrong; the reported effect is list ordering.
12–13 Nov · Orchestrator · Deploy only merged main from a clean checkout, avoiding migration divergence and accidental upload of the local video link. Run research early but do not build dependent tickets on unmerged branches.
12 Nov · Owner · Clerk tools support Chromium-based browsers in v1, including Edge and Helium; Watch remains ordinary cross-browser web.
12 Nov · Owner · Use current releases and docs, including Svelte and Cloudflare lookups; parallelize only where safe.
12 Nov · Owner · Opus 5.5 at extra-high implements; Sonnet 5.5 through Cursor and Sol 6.1 review. Cloudflare sign-in and demo password were confirmed.