Resources¶
Purpose¶
The Resources area exists to make creative work easier by giving teams reliable access to background information before production starts.
What Belongs Here¶
- source-of-truth reference links
- brand and product context
- reusable briefs and templates
- media library entry points
- assistant-access patterns for external systems
- metadata descriptor definitions for traceability
Rule¶
Resources should help creation move faster without embedding policy. If a page tells people what they must or must not do, that content belongs under Compliance.
Core Components¶
| Component | Why It Exists |
|---|---|
| Resource catalog | one index of available background materials |
| Access links | fast entry into libraries, drives, or systems |
| Access skills | repeatable ways for assistants and operators to tap into each system |
| Metadata descriptors | structured fields that make assets searchable and auditable |
| Reusable templates | repeatable inputs for briefs, requests, and production setup |
Placeholder Source Systems¶
The initial canonical resource surface should include:
- raw media from Cloudinary
- company information from SharePoint
- discussion context from Microsoft Teams via Azure-backed access paths
- product and article sources from Odoo BFF and SPOT
- structured reference docs from
docs.omnivoltaic.com/<doc-sites>
These are not only sources. They are also capability surfaces that need clear access skills so assistants can retrieve the right information consistently.