Project overview: attach files and documents to enrich project context

[optimize07]

Right now project context lives in text fields — goals, descriptions, scope. That's fine for simple projects but breaks down quickly when the real context lives in documents: a brief, a spec, a brand guide, a contract, a research PDF.
The problem

Agents operate on the context they're given. If your project has a 10-page product spec or a brand guidelines PDF that defines how all creative work should be done, there's currently no clean way to surface that at the project level. You end up copy-pasting content into descriptions, linking external docs agents can't read, or re-explaining the same context in every task.
The proposal: a Files / Documents section in Project Overview
A simple file cabinet attached to the project — uploadable and referenceable by agents working within that project.
Supported formats to start:

Markdown (.md) — specs, briefs, SOPs, READMEs
PDF — contracts, research, brand guides, decks
Plain text (.txt)

How agents use it
Files attached at the project level get surfaced in the agent's context when it picks up a task under that project — the same way goal ancestry already flows down to tasks. An agent working on a design task automatically has access to the brand guidelines PDF. A coding agent has the spec doc. No manual re-injection needed.
Example scenarios

Attach a brand-guidelines.pdf → every creative agent in the project references it automatically
Attach a product-spec.md → engineering agents know the full scope without being told per-task
Attach a tone-of-voice.md → copywriter agents stay consistent across all output

Why the project level
Tasks are too granular and short-lived to store reference material. Company level is too broad. Project is the right scope — it maps to how humans naturally organize work. A project has a brief. The brief should live with the project.
This also pairs naturally with the existing goal alignment system — files become part of the "why and how" context that flows down to every agent and task in the project.

[contentfree]

This would be great. However, I think that having artifacts available both at a company-level and project-level makes sense. For example, brand guidelines are often shared across a whole company, but a product spec is often project-based.

(It would also be nice to have a company-level secrets store!)

[contentfree]

Please consider this, @cryppadotta!

[youenchene]

+1 on this suggestion. My first idea were to have reference document repository (drive?) where you can get access the documents approved.

It would serve as a context for new tickets and agents.

Currently they are lost inside the tickets.