Project context

What belongs in context

Uploads, connected-service sources, saved Assets, Project Map specs, design-system guidance, repository snapshots, decisions, task conversations, and accepted receipts can all inform the project.

Draft capability documents are deliberately excluded until Save to Assets. That prevents unsaved experiments from silently changing later work.

How engines receive it

Before a Build round Iterel freezes a bounded Context Pack containing the objective, prior conversation and rounds, receipts, changed files, remaining plan items, mission PRD, task/mission references, effective rules, recalled memories, design guidance, and source provenance. The pack is engine-neutral, so changing engines does not reset the task.

Context panel

The panel supports Living Project Context, uploads, sources, cited Q&A, and semantic health across audience, problem, value, constraints, success, and decisions. Health distinguishes settled or evidenced areas from genuine gaps; a gap can open optional setup work without blocking the project.