The .ai folder · Yuli Code

What Yuli stores inside your project, what is versioned with the team and what stays only on your machine.

In each project's .ai/ folder, Yuli stores the quality contract, missions, memory, rules and its working data. Part of it is shared with the team through Git; part of it is local and never pushed.

Yuli never edits your .gitignore. Whatever must stay out of Git is added to .git/info/exclude, which is local to your copy of the repository.

What stays out of Git

Yuli adds these lines to .git/info/exclude:

.yuli/
**/.ai/codebase/
**/.ai/state/

Structure

.ai/
├── contract.json          quality contract
├── quality.json           measurement settings and assumptions
├── memory/                project memory
├── rules/                 team rules and learned rules
├── missions/              agent missions
├── state/                 working data (local)
├── codebase/              code index (local)
├── requirements/          requirements traceability
├── design/                Web Studio design system
├── web/                   preview mocks and contracts
├── glossary.json          domain glossary
├── team.json              team configuration
├── devops.json            CI/CD connections
└── compound.yaml          Compound definition

Versioned files

Path	Contents
`contract.json`	The quality contract. It is a protected path: an agent can't edit it.
`quality.json`	Settings for the Measurement phase and estimation assumptions. Optional.
`memory/`	`memory.json` and `MEMORY.md`: what the agent must remember about the project.
`rules/`	Team rules in `*.md` and `learned.md` with the learned rules.
`glossary.json`	Domain glossary, editable from the Governance Center.
`team.json`	Shared team settings.
`devops.json`	The project's CI/CD connections.
`compound.yaml`	Services that Compound starts in Web Studio.
`requirements/traceability.json`	Rule ↔ test traceability.
`design/system.json`	Web Studio design system (tokens).
`web/mocks.json` and `web/contracts/`	API simulator rules and contracts.

Local folders

`state/`

Working data that only makes sense on your machine. It is never pushed.

Path	Contents
`state/quality/versions.json`	Figures for the current version and for N−1.
`state/quality/history.jsonl`	A short series of numbers (up to 30 versions).
`state/quality/agent.jsonl`	Statistics about the agent itself.
`state/contract-audit.jsonl`	Audit trail of every change to the contract.
`state/deployments.jsonl`	Deployments recorded for DORA.
`state/reviews.jsonl`	Independent reviews.
`state/agent-cost.jsonl`	Agent cost.

`codebase/`

The code intelligence index: code_intelligence.db, a SQLite database with the symbol graph. It regenerates itself; you can delete it without losing anything.

Missions

Each agent mission lives in missions/<conversación>/ with two files:

mission.json: original request, requirements, acceptance criteria, decisions, assumptions, plan, files touched and handoff point.
PLAN.md: the human-readable plan.

See Missions and phases.

Outside the project

Personal data doesn't live in .ai/. Your settings, your own prompts, skills and hooks, and the chat history are in your user's Yuli configuration folder. On Windows:

Folder	What it stores
`%APPDATA%\.yulicode`	Settings, prompts, your own skills, hooks and chat history.
`%LOCALAPPDATA%\.yulicode`	Runtimes, indexes, caches and logs. Safe to delete.

Documents the agent writes

Outside .ai/, the agent only writes documents when appropriate:

Path	When
`docs/quality/reporte-calidad.md`	When a quality version is recorded.
`docs/sistema/`	Only if you ask it to document the system.
`docs/architecture/`	ADRs, threat model and C4, from the Governance Center.