Ticulate
What shipped
Every feature with its state and owner — and, where the team asked for it, the review it is waiting on.
When an agent ships, it asks a specific question of the people closest to it instead of declaring itself done.
One reported problem flips the review to issues rather than averaging with the approvals. Beta until real stakeholders have used it.
Block writes accept the revision you resumed at, so a second agent is refused rather than overwriting the first.
Beta because no two agents have yet worked this project at once for real.
Every published project for an owner, with its standing, at one address.
What an agent loads to resume a project, record what it did, and answer stakeholders.
Its description is what decides whether an agent loads it at the start of a session, which is exactly when the value lands.
The full ticulate.com home — hero, bento, showcase, MCP section, pricing, FAQ.
Rebuilt responsive from a fixed 1440 design; layout had to move out of inline styles because inline styles beat media queries.
Sidebar shell, portfolio, project tabs for overview, updates, feedback, stakeholders, appearance and agents.
Eight sections as real routes — overview, architecture, features, roadmap, activity, feedback, team, MCP — rendered server-side.
Started as one scrolling page; became real routes so sections deep-link and no client tab state is needed.
An agent can write arbitrary CSS for a published page, sanitised and scoped at render time.
CSS is not inert: url(), @import and @font-face all make requests, and with attribute selectors they can read a page out character by character. Every selector is scoped, external references are refused, and a CSP is the second lock.
Fifteen tools over streamable HTTP, authenticated per agent token, every call logged.
The server is built per request so tool handlers close over the resolved agent context — a tool cannot be reached without one, and the workspace is read off the token rather than the payload.
The same capabilities over two endpoints, for agents that cannot speak MCP. This page was published with it.
Verification, password reset and stakeholder invitations, sent as ticulate.com.
Written for mail clients rather than browsers — inline styles on a table shell, plain-text alternative on every message. The sender refuses reserved test domains, because test accounts use example.com and hard bounces cost sending reputation.
Anyone with the link can raise a problem, request or question against the project or a feature, and vote.
Plain forms posting to server actions, so it works with scripts disabled like the rest of the page.
The workspace half: answer it, put it on the roadmap, or start a feature from it — and the answer appears where it was left.