What agents know
The project map made at every start, lessons agents record, a search of the team's history, and the Knowledge view.
Agents often rebuild something that already exists, because nothing told them it was there. Sculptured gives every agent a wide, shallow picture of the project and of what the team has already done, with nothing for you to maintain.
The project map
At every start, Sculptured maps each folder the team's agents work in, on the computer that runs them:
- Areas: folders up to two levels deep, how many files they hold and of what kind, and what their own notes (a README or first document) say they are.
- Who worked where: the agents that changed files in each area.
- Sections: every Markdown document's headings, with their line ranges.
Each agent's first message carries a short outline of the map. The full map is written to .sculptured/map.md in the folder, so an agent opens a section at its line range instead of reading a whole file. Ignored files (by .gitignore) and folders such as node_modules are left out. Nothing else in your folder changes.
Search what the team already did
Agents have a search_history tool. It searches what the team's agents, including finished ones, wrote, ran, got back and were told, newest first, with who and when. It uses no model, so it costs no tokens beyond the answer. An agent uses it to check whether something exists, or to find which agent knows about something and ask it.
Lessons
When something cost an agent a wrong turn that others could avoid, it records a short lesson with record_lesson. Every agent of the team is told the latest lessons when it starts a conversation, including after continuing fresh from its notes. Teammates already working get a new lesson with the next message they receive, so nothing interrupts them.
A lesson starts as reported. When you agree with it, Confirm it: agents then see it marked as confirmed. Hide removes it from what agents are told.
Constraints
A constraint is a rule every agent must follow in this project, such as "never use float for money". Agents record one with record_lesson and kind: constraint. Constraints come first in every briefing, marked as rules.
Lessons kept with the project
When you Confirm a lesson or constraint, Sculptured also keeps it with the project, in .sculptured/lessons.md in each folder the team works in. Every later team in that folder is told the kept lessons at its start, so what one team learned is not lost when it ends. The file is plain text: delete a line to drop that lesson. To keep knowledge across projects and sessions as well, give agents Kindex.
Claim checks
When an agent's turn ends, Sculptured compares what it says it did with the tool calls captured in that turn. If it says it changed a file and no edit to that file was captured, or says tests pass and ran no command, the Knowledge view gets a claim check entry. This is a heuristic: a match proves nothing about the work, and a mismatch is a reason to look, not a verdict. Agents are never interrupted by it. An idea from Arbiter.
The Knowledge view
On the Run board, More → Knowledge shows the lessons and your decisions, and the latest project map with who worked where. When agents recorded lessons since you last looked, More shows a quiet count. It never interrupts a run.