Goals

A goal is something you want found out about a project, in your own words. For example: find the typologies in this project from the sunlight studies, the design documents and what we've said about them. Agents plan the work, read the project's own data, and write the answer up with its sources, like an agent in a chat app. A goal only reads. It never changes your project's data or your Rhino model.

Set a goal#

In the project chat, in Rhino or on the web, press + and choose Goal, or choose Set a goal… from the command palette. Write what you're after and send it. The goal becomes your message in the conversation, with its card under it.

Good goals name what to find and where to look:

• Find the typologies in this project, with how much sun each one gets.
• Which of our studies contradict the design statement?
• Summarise every decision we made about the courtyard, with where each was made.

What a goal reads#

Only the project it was set in, and only what you can see:

Archived files and deleted conversations are left out. Text from files and people is read as information, never as instructions: a document can't tell a goal what to do.

How it works#

1. Plan. A planner looks at what the project holds and splits the goal into a few parts, each reading one or two kinds of data. If it can't make a plan, the goal runs as one part that may read everything.
2. Work. A worker per part reads what its part needs: a list first, then the items that matter. Every item it reads gets a reference such as S3.
3. Write. A writer turns the findings into the answer: first the answer itself, then the detail (often a table), then what the project's data didn't have. Every claim cites its source.

Numbers#

A number in the answer comes only from a recorded fact: a study's result, a tag, or an agreed workspace fact. It's quoted as it's stored. A number that only a document or a person gives is attributed to them: the design statement gives 24 m.

After the answer is written, Wrengler checks every number in it. A number beside a cited study, tag or workspace fact must be in that source. A number on a line that cites none of those must be in some fact the goal read. Any number that fails is listed under the answer, so you know to check it:

Not found in the recorded facts cited: 24. Check these against the sources before relying on them.

The answer#

The answer is posted in the conversation like any other, with its Sources listed under it: studies, files (with the page) and conversations, each opening where it came from. You can rate it, and it becomes part of the conversation. Ask a follow-up in the same thread and the assistant builds on it.

If the write-up itself fails, the answer is each part's findings as they came, so the work isn't lost. If the write-up reaches its length limit, it ends with a line saying it stops there.

Stop and resume#

• Stop ends the goal after the step in hand. The person who set it and the project's leads can stop it.
• If the platform stops before the goal finishes, the card says Interrupted. The person who set it can press Resume. The plan and every finished part are kept, and only the part that was in progress starts over.

Limits#

When a goal reaches its limit, it writes the answer from what it has and names the parts it couldn't finish.

Goals come with Wrengler Pro. They count against your organization's monthly assistant messages, and an organization that has turned AI features off can't run them.

Not yet#

• Goals across projects. A goal reads the project it was set in.
• Changing things. A goal can't add tags, save files or change the model. It tells you what it found, and you decide.
• Comments on files and results. What people say is read from the project's conversations and notes.

When something goes wrong#

Related#

• The project assistant: asking, sources and privacy.
• Assistant and goals overview: what the assistant does, and what waits for you.
• Projects: the files, facts and conversations a goal reads.