PM Documents and artifacts
Home · PM Documents and artifacts
Goal
This page explains the review flow for artifacts and PM Documents: find a deliverable, review content, compare versions, download, publish or add it to knowledge.
Lifecycle
The common flow is run → structured output → artifact → version → PM Document → Download / Publish / Add to knowledge.
| Term | Meaning |
|---|---|
| Structured output | Agent result that still needs human review |
| Artifact | Governed object from a run or review |
| Version | Specific artifact state with history and diff |
| PM Document | Reviewed project document ready for downstream action |
Review a document
- Open PM Docs, Reports or Reports & artifacts.
- Verify the active project.
- Filter by status, type, date or author if available.
- Open the document.
- Review content, metadata, lineage and available actions.
- Save edits if your role allows it.
- Check the diff before approval or publication.
Actions
| Action | Effect |
|---|---|
| Download | Downloads a local copy |
| Publish | Publishes to a governed destination |
| Add to knowledge | Adds the reviewed document back to project knowledge |
Common issues
| Symptom | Likely cause | Recommended action |
|---|---|---|
| Document not found | Wrong project or filters | Check active project and reset filters |
| Publish unavailable | Missing destination, policy or role | Check project integrations and policy |
| Diff unexpected | Wrong reference version | Open lineage and compare versions |