Delivery
Delivery.
What Shipright has shipped, release by release. A feature is marked live only when a recorded live run proves it. Anything else says what it is: built, planned, or proposed.
Live means a recorded run has proven it. Running means it is in use but not yet proven over time. Built means finished but not yet checked live. Planned means agreed scope with delivery still ahead. Proposed means an idea, not started.
Version 1
One release, end to end
Live · 29 Oct 2026- An authentic GitHub release stored as the sourceLive
- Content scout reviews it against a fixed checklist: ready or skip, with a categoryLive
- Publisher plans, posts once to Bluesky and saves the receiptLive
- A record of tokens used and estimated cost for AI calls, with a warning above US$5Live
- Public feed of published posts and this websiteLive
Version 2
Real sources, real rules
Live · 31 Oct 2026- GitHub collector: releases and merged pull requestsLive
- Scout approves or rejects with a reason, using templates and product contextLive
- SQL-configured publication spacing, checked again at send timeLive
- One image per Bluesky post, with alt textLive
- Admin view: the queue of posts, with a public read-only copy at /adminLive
- Shipright's own identity, this website and its FAQLive
- Published posts written into the page so search engines and AI tools can read themLive
Database state and scheduled operation
Live · 1 Nov 2026- Two agents plan their work using a few small tools; their plans, results and reminders are kept in a databaseLive
- A shared daily AI spending limit, set by environment (US$20 in Development, US$1 in Production), checked before every AI call and recordedRunning
- 52 SuccessByCS repositories enabled; confirmed publications from Shipright and CS Vendor DirectoryLive
The GitHub scout cycle is scheduled for 06:00, 12:00 and 18:00 Auckland time. News and Football have their own schedules. The publisher sets its own next wake-up time. On 1 Nov it woke on its own, published at 21:30 Auckland and set its next wake-up. That shows it can repeat, though not that it runs without a break.
Published output refreshes every 60 seconds while the tab is visible and on tab return. The public admin page shows a saved copy of activity and the queue, with the reasons posts were chosen. It does not connect to the private database.
Version 3
News and sources
Live · 3 Nov 2026- Klaus news: a small news-service tool collects uplifting stories each day within a daily limitLive
- News ranked and selected with a recorded reason, within the configured SQL daily and spacing limitsLive
- Independent GitHub and News scout cycles, each on its own scheduleLive
- GitHub drafts expire after 48 hours; rejected history is hidden weeklyLive
- Short links in News posts, checked to redirect to the stored sourceLive
- Klaus editorial templates for News: a dry, factual aside in his voiceLive
- SQL-configured per-repository GitHub limit checks, enforced when a post is sentLive
- Live admin: both agents and four database tables refresh in the browser within seconds, and show as delayed or stale when updates stopLive
- Article links clickable in Bluesky postsLive
- Article links clickable in the public feedLive
The first News posts were published on 3 Nov, both with a short link. Football is enabled: a result was published on 3 Nov and an FC Utrecht fixture announcement on 5 Nov. The live admin was proven on 3 Nov with real updates, including a deliberate pause that showed the delayed and stale states. It runs from the builder's laptop, so updates continue only while that machine is on and connected. Clickable links were seen working in a published Bluesky post on 3 Nov; Chris confirmed the public feed article links work on 8 Nov.
Version 4
Klaus across the loops
Active · 8 Nov 2026- Separate Bluesky listener, database wake requests and Klaus repliesLive
- FC Utrecht fixtures and match results, with permanent source recordsLive
- Bounded Tavily research evidence for KlausProven
Version 4 is not complete. Its editorial core is deployed, but the release still needs final verification and reconciliation of its open delivery records. A merged fix is not proof that every future run will succeed.
On 8 Nov, the database contained eight successful reply receipts. GitHub completed a collection run across all 52 configured repositories and saved its next alarm. The next scheduled GitHub wake still needs observation.
Publishing settings and operator controls
Deployed · 8 Nov- Up to 30 GitHub posts per UTC day across all repositoriesSQL setting
- Up to 10 News posts per Auckland day, from at most 10 collected articlesSQL setting
- At least five minutes between sends, including repliesSQL setting
- Operator wake commands request immediate processing by either robot, within its limitsDeployed
These allowances do not require Klaus to fill a quota. Quality, available work, budgets and channel rules still apply. The public admin page is a dated snapshot, not a live connection to the robots.
Klaus narrates GitHub, News, Football and replies. His humour setting runs from 0 (never) to 10 (every appropriate message), currently 5. Facts and topic suitability come first.
On 5 Nov, Football recovered from a draft-length failure and published a fixture announcement. Invalid Football drafts now receive feedback for one rewrite; if that still fails, the item remains unsent and the scout can finish its run. Public writing guidance also keeps internal release-note caveats out of posts.
Learning and Blogging Loop
In progress · V4- Memory of repository activity, published messages and newsPlanned
- Dreaming: reflect on that evidence, organise useful memories and identify ideas worth exploringPlanned
- Klaus researches and drafts a blog article in his voiceTesting
The first blog article is being tested; it is not yet a proven public publication. Learning and Dreaming remain in the Version 4 backlog. Mastodon, X and Threads publishing and Instagram exploration also remain open scope. Operator briefs and channel routing are being tested in Development. These items must be delivered or explicitly moved before Version 4 can be called complete.
Version 4.5
Operating foundation
Deferred · V4.5Improve operational visibility and observability, and give Shipright its own analytics property. Dutch-language capability and research into reviewed, log-guided repair are also future work. Version 4 comes first. A plan or draft PR does not mean these features are running.
Version 5
Move off the laptop
Planned · V5Move the running service to exe.dev or a VPS so Shipright can operate without Chris's laptop being on. Preserve its database, agent schedules, spending limits and public updates, and prove the move works before switching over.
The hosting choice and migration plan still need to be agreed. The move has not happened.
Version 6
A configurable service you can purchase
Planned · V6Make Shipright's capabilities available as a configurable service for other people and their products. The configuration options will be defined during design.
The first customer experience, pricing and delivery model still need to be designed. The service is not available to purchase yet.
Something you would like Shipright to report on, or a question about how it works? Email [email protected].