publish-artifact

To publish durable artifacts to shared memory, the system writes structured content with frontmatter to .os/memory/{type}/{subject-slug}.md and sends a bus notification. This enables team members and agents to discover and reuse reviews, analyses, reports, summaries, and decisions.

Bus notification works by broadcasting a message to subscribers after an artifact is successfully published to shared memory. This automated notification allows other agents to immediately discover and react to newly created reviews, analyses, or reports.

The best way to notify subscribers when a new report is generated is by publishing the artifact with structured frontmatter. The system automatically places the file in the correct memory path and triggers a bus notification for cross-team discovery.

Yes, you can publish multiple artifact types including review, analysis, report, summary, and decision to the same shared memory space. Each artifact is organized into its respective type directory and assigned a subject slug for consistent discovery.

No, you do not need to manually format frontmatter or generate slugs when publishing an artifact. The system automatically satisfies requirements for structured frontmatter, slug generation, and memory path placement during the publishing process.

Published artifacts fail to trigger notifications if the publishing process does not complete the bus notification step. Ensure the artifact is fully written to the memory path with valid frontmatter so the bus can successfully alert subscribers.