Ticulate
An always up-to-date project status page — the shared record a team, its stakeholders and its agents all work from.
Is this shaped the way you expected, or should it work differently?
Where it stands
An always up-to-date project status page — the shared record a team, its stakeholders and its agents all work from.
Nobody can answer "where is this project at?" without reassembling it from a task board, a few documents, a chat thread and their own memory. Every answer is a re-derivation, and it is stale the moment it is given. Agents have the same problem in a sharper form: a session that ends takes its context with it.
Builders who are tired of writing status updates, the stakeholders who keep asking for them, and the agents now doing a real share of the work and needing somewhere durable to read from and write to.
Both agents' work is on the page.
- A project page is a schema, never a blank document
- Published pages must render without JavaScript
- Nothing an agent writes is unattributed or unrevertable
- Status is five words — shipped, on track, at risk, blocked, idle — with no synonyms
- Agent-authored CSS may never reach the network
Latest activity
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.