Ticulate

Sending someone the page is the main thing this is for, and until now that link showed up in Slack or a message as a blank rectangle with no title and no description — which reads as a broken link rather than a status page. Every project now has its own preview card carrying the three things somebody wants before deciding to open it: how the project is doing, what it is, and the one thing being worked on next. Your portfolio gets its own. The tab icon is the Ticulate mark rather than a leftover from the day the site was scaffolded. Projects that are not open to the public stay that way. A preview is fetched by whoever received the link, with no sign-in, so anything they could not read on the page gives them nothing here either — not the name, not the summary. Search engines are given a map of the public projects only; anything shared by link stays off it, because listing it would be handing the link to everyone.

Setting up an agent took two steps, and the first one quietly did not work where it was needed most. Connecting a workspace changes a config file, and a session already running in your project does not pick that up until it restarts — so the second step told the agent to use tools it could not reach yet. It is one thing to paste now. Create a token and you get a single sentence containing a link; give that to the agent already working in your project and it collects everything it needs in one go. Nothing to install, nothing to restart. Connecting properly is still there for people who want it, and it now says plainly that it applies from the next session on. The link is deliberately short-lived. It carries a credential, so it stops working after thirty minutes and can be replaced with a click.

Until now one setting decided everything about a project's page, and it was too blunt. Work you want counted on your portfolio had to be fully published to appear there at all, and any page someone could read was a page anyone could write to. Those are now three questions, asked separately in Share. Who can open the page is unchanged: private, anyone with the link, or public. Whether your portfolio counts it is its own choice. A published project keeps the full card and links to its page. Anything else is listed with just its name, how it is doing, and when it last moved — enough to show the work exists and is moving, without opening it. Who can leave feedback is the third. Open to anyone who can read the page, limited to the people you invited, or closed so the page only reports. Invited stakeholders each get their own link; opening it is what identifies them, still with no account to make, so what they say arrives with their name on it instead of "Anonymous". You can copy anyone's link again from their row under People.

A published page can show your own mark above the project name, and be set in one of eighteen typefaces across sans, serif and mono. Both are served from Ticulate rather than fetched from anywhere else, so nobody reading your page has their visit reported to a third party — and a logo keeps working even if the file it came from moves. Projects can also carry links now, so a reader can get from the page to the thing itself.

It described a better status page, with agents as the mechanism keeping it current. What it actually is: the hub for projects an agent is building and a person is steering. Three claims had also gone stale — the page no longer carries the architecture or the work list, and the site still said it did.

A line saying a thing shipped was something you either believed or did not. Features, work items and updates can now carry links — a pull request, a document, a dashboard — so anyone reading can go and see for themselves rather than taking it on trust.

An import that failed ambiguously and was run again used to post the whole history a second time. Re-running now recognises what it already wrote and skips it, and anything posted in error can be removed rather than living on the page forever.

An invitation sent to someone without an account asked them to sign up, then confirm their address, then dropped them on the home page with no word on whether it had worked and no sign of the project they had been invited to. The confirmation link now carries them back to the invitation, already signed in. Invitations also wait for them inside the app, so losing the email is no longer a dead end.

Setting a project up used to hand the agent a key to every project in the workspace, every time, because at that moment the project did not exist yet to be named. Those keys now attach themselves to the first project they touch and go no further. Keys handed out under the old behaviour can be narrowed in place without being replaced, so nothing has to be reconnected.

The roadmap shows what is planned. Its other half is what is not planned yet, so there is now a direct way to ask for something from the roadmap itself. Requests reach the team, get a reply either way, and the ones taken up appear on the roadmap where anyone can see they were taken up.

A published page was showing everyone the internal architecture, the build task list, the decision log, the team roster and which agent wrote each line. All real, none of it useful to someone following a project — and all of it pushing the things they came for further down. The page now answers four questions and stops: where it stands, what it has, what is coming, and how to say something about any of it. Everything else moved to the workspace, where the people building it were already looking.

Dev and production were split onto separate Neon branches this morning. The collaborator schema change went to dev; Vercel deploys on push, so the code that reads those columns reached production while production still lacked them, and every database-backed page returned a 500. It was found by probing the live site, not by anything in the system, which was the real gap. The schema is applied, the change is written down as guarded SQL under migrations/, and scripts/check-schema.mjs now reports what any branch is missing in a second. DEPLOY.md carries the rule that was absent: schema goes on before the code that needs it.

The first real sign-in failed because the account predated email verification, and the form said only that the credentials did not match — sending you to reset a password that was never the problem. It now recognises an unconfirmed address, resends the link, and says so.

Pushed to a private repository at mcinnisdev/ticulate — 15 commits, no environment files tracked. The Vercel project is the next step, with the environment variables and Cloudflare DNS steps written down in DEPLOY.md.

Resend is wired up and sending as ticulate.com, with three templates written for mail clients rather than browsers. Password reset is a complete flow including expired-link recovery and single-use tokens. Adding a stakeholder with an email address now actually tells them, which it never did before.

Features and tasks take a question. Setting one flags the item, shows the question on the thing it is about, banners it on the overview, and returns the answer in the next project.resume. It exists because the alternative is an agent picking silently and being wrong, or asking in a chat that ends.

The homepage still carried the design kit's copy: a testimonial from an invented person at an invented company, a showcase of customers that do not exist, and a $12 seat for a product with no billing. All removed. Pricing says free while in beta, the only example shown is this page, and an audit script now fails the build-adjacent check if invented people, unbuyable plans or dead links come back.

Build work was being filed as features, which buried the things stakeholders are meant to react to. Tasks are now their own shape with their own home under Activity. The workspace gained a Features tab with edit, delete and move-to-tasks, a task list, and editable project details and purpose — so anything an agent gets wrong can be corrected by hand.

Same code path as MCP, different door.

Deployment and the design-system port were filed as features, which put build work in front of the people being asked to review capabilities. Tasks are now their own thing, shown under Activity, and features are only what someone could have an opinion about.

This page was created by an agent calling the documented fallback rather than the MCP endpoint — the first real use of either, and the first project in the workspace.

Purpose, architecture, roadmap and theme are read-modify-write, so two agents on one project lost whichever wrote first. Those calls now take the revision you resumed at and refuse a stale write with a recoverable error.

Feedback can now be left from wherever the opinion forms — the header of every section, roadmap items, architecture open questions — and answered from the workspace, with the reply and its state appearing where the person left it. Promoting to the roadmap keeps the trace back to who asked.