Use this area first. If the answer already looks acceptable, choose where it should live and push it forward. Only promote it when the answer itself needs a real human decision.
Where should this live?
VAPOURS-CANADA-POLICIES.md
If the answer is about
- • actual standing company rules
- • customer-facing rules
- • compliance requirements
- • brand/legal guardrails
- • permanent business decisions
For example
- • required compliance wording
- • pricing rules
- • approval needed before public posting
- • official-asset-first as a standing brand rule
WORKFLOW-RULES.md
If the answer is about
- • how the team should handle the work
- • what step comes next
- • who should decide or own the next step
- • when to escalate, review, or approve something
- • what should happen before image production or publishing
For example
- • when something should go to review
- • when manager approval is required
- • when current source images are good enough to proceed
- • what should happen before building final visuals or posting
Wiki
If the answer is about
- • useful facts or reference knowledge
- • product or manufacturer background
- • recurring context agents may need again
- • information worth searching later that is not really a rule
For example
- • manufacturer background notes
- • product family context
- • recurring vendor facts
- • reference links or research findings
Task note
If the answer is about
- • only this one task or project
- • temporary context that does not belong in shared files
- • a one-off instruction, source, or blocker
For example
- • this customer supplied these assets
- • use this landing page for this campaign
- • wait for this one missing answer before continuing
- • this detail only matters for this specific thread
What happens next?
Write to file = if you are a manager, the answer is written immediately to the selected file and then lands in completed history.
Promote to question = use this when the answer itself still needs a real human decision, not just a file choice.
Dismiss = hide this item from the internal queue without changing the underlying task history.
Ready for approval or writeback = use this section to review pending items, completed history, and anything that still needs confirmation.