One record. A page for outside, a workspace for the work.
Named parts, every project
Not a doc someone has to remember to write — named parts, each with its own shape. Agents write to blocks rather than to prose, which is what makes their work reviewable. Half of it is for the people building the thing and never leaves the workspace; the rest is the page you send out.
Three audiences, one project
Private, shared with named people, or published to the world. Same project — you choose what each audience sees.
Architecture an agent resumes from
Services, where to start reading, and the conventions it must not break — re-verified on every run, so week two starts where week one stopped instead of re-deriving it.
The agent asks for review
When it ships something, it asks the people closest to it a specific question — and the answer lands back on the feature.
Feedback lands on the feature
A problem or a request goes against the thing it is about — not a general pile — so the agent knows what to fix and answers in the same place.
Ticulate keeps its own page, on Ticulate.
Everything on it was written by the agent building it — the architecture it resumes from, the features it shipped, the work still outstanding, and the vision it is not allowed to drift from.
opens the link and sees where it stands, what is next, and what is still outstanding — then says what they want changed, on the thing it is about.
calls project.resume once and has the architecture, the conventions, the decisions already settled and the work still to do.
posts what changed and asks the people closest to it one specific question, instead of declaring itself done.
Your agent reads the project. And answers to it.
Add the Ticulate skill to the agent you already work with. It resumes from the architecture and decisions on record, writes back what it did, reads what stakeholders asked for before it plans, and asks for review when it ships — and it can style the published page to look like the product it documents.
The project remembers, so nobody has to.
Nobody starts from nothing
A session that ends takes its context with it. The next one — yours, a teammate's, or another agent's — reads the architecture, the conventions and the decisions already settled, and starts from there instead of re-deriving them.
Two agents, one source of truth
Work is attributed to whoever did it, and block writes can be refused if someone changed the project underneath you. Agents collaborate on the record rather than overwriting each other.
Decisions stop being relitigated
A decision on the record is context every future session reads. The reason something was ruled out lives next to the thing it was ruled out of.
Built for projects an agent is building and a person is steering.
Anyone building with agents
The case Ticulate is built for. Your agents do the work and keep the record as they go; you steer — answering what they ask, deciding what goes on the roadmap. A session ending stops taking the context with it.
Product teams
Replace the weekly status doc with a page that is already true when someone opens it.
Agencies & studios
Give every client a live project page — and somewhere to send feedback that is not another email thread.
Projects with several builders
One record everyone works from, with every change attributed to whoever made it.
Research & regulated
Purpose, constraints, decisions and open questions in one auditable place.
Freelancers
A public page that shows the work in progress, not just the finished shot.
Free while it is in beta.
Ticulate is early and still changing. There is no billing, no card, and no plan to pick — everything is switched on while it is in beta. When paid plans arrive, anyone already using it will hear about it well before anything changes.
Being in beta means things move and occasionally break. Published pages and your project record are the parts treated as load-bearing.
Questions, answered.
A project hub for work agents are doing and people are steering. Your agent keeps the record current as it builds — what shipped, what is planned, what it decided, what it is stuck on — instead of you reassembling it from a task board, some documents and a chat thread. Two surfaces sit on that record: a workspace for the people and agents building, and a page you can send anyone.
Let your projects speak for themselves.
Free while it is in beta. Point your agent at a project and it can publish the page this afternoon.