Artifacts
An artifact is what an agent makes: a typed, versioned data file, and a page drawn from it. The page opens in any browser with no internet, and every change the agent makes redraws it.
Both files live in your project, in its turbinez/ folder, so git keeps their history. Connected, the same artifacts live in Turbinez, where your team works on them.
The three types
Board
turbinez/board.json · turbinez/board.html
The project's work as epics and tasks, each with its code from the document, a status, a priority, a size, acceptance criteria and its dependencies. The page shows it by status or by epic, with filters and each card's details.
Made by Board Builder · Its format, field by field
Project Brief
turbinez/brief.md · turbinez/brief.html
What the project is, in sections a team can plan from: the goals, the users, what's in and out of scope, the constraints, the timeline, the technology and the rest. Every unknown is an open question, never a guess, and a paragraph you write in it stays word for word.
Made by Project Intake · Its format, field by field
Survey
turbinez/surveys/intake-1.json · turbinez/surveys/intake-1.html
The questions the documents left open, as a page the client opens in any browser, answers and saves as a file to send back. The agent reads the answers into the Brief. A survey never changes once written, so answers always match their questions.
Made by Project Intake · Its format, field by field
What every type keeps
Each type follows the same contract, so any agent can make one and any viewer can show it.
A name
board, brief or survey, written in the file
A version
the format changes only with a new version
A JSON Schema
so any tool can check a file
Written docs
every field, in plain English
A page template
the same page for every project
The contract and each format are in the repo: docs/artifacts