State Of Company Publisher
Automate a weekly, public-safe state-of-the-company post from internal ship logs, decisions, and review signals without leaking private ops detail.
Overview
State-of-company-publisher is a MCP server for the Operate phase that turns a week of private agent and company signals into a scrubbed, voice-gated public state-of-the-company narrative on a fixed weekly schedule.
What is this MCP server?
- Scheduled Sunday 18:00 CDT run composes a 7-day state-of-the-company markdown narrative
- Ingests open specialist handoffs, sunday-review, recent decisions, and P-gate catches as private inputs
- Voice-gate for newsletter surface with 70+ threshold plus scrubber HARD before any publish path
- Auto-publishes to site/state.html when gates pass; otherwise saves drafts under data/state-drafts/ for Cooper
- Federation metadata: MIT license, Hermes owner agent, hub telemetry endpoint, 15% partner share USD settlement
- Server version 0.1.0 per registry schema
- Runs Sundays at 18:00 CDT on a 7-day lookback window
- Newsletter voice-gate threshold 70+ with scrubber HARD enforcement
What problem does it solve?
Weekly updates stall because internal handoffs, reviews, and gate catches live in private systems and are risky to paste into public copy without a consistent sanitization workflow.
Who is it for?
Indie founders and small agent federations who already publish on a static site and want automated, gated weekly company storytelling tied to real ops inputs.
Skip if: Builders who only need informal social posts, lack private input feeds (handoffs, reviews, decisions), or cannot host site/state.html and draft folders.
What do I get? / Deliverables
You get a repeatable Sunday publish path—live state page when gates pass or a Cooper-ready draft when they do not—so stakeholders see progress without exposing raw internals.
- Public-safe weekly state-of-the-company markdown narrative
- Optional auto-publish to site/state.html when voice and scrubber gates pass
- Draft artifact in data/state-drafts/ when gates fail for human review
Recommended MCP Servers
Journey fit
Canonical shelf is Operate because this is a recurring production ritual that turns internal week-in-review inputs into a governed public artifact on a fixed schedule. Iterate fits ongoing company narrative cycles—what shipped, what was caught, and what is next—rather than one-off launch copy.
How it compares
Scheduled narrative publisher with hard content gates, not a generic blogging skill or raw file MCP.
Common Questions / FAQ
Who is state-of-company-publisher for?
Solo builders and small teams running Daily AI Agents-style stacks who want a weekly public company update sourced from real internal signals, not manual recap docs.
When should I use state-of-company-publisher?
Use it when you run a recurring Sunday cadence and need sanitized markdown that reflects the last seven days of shipping, reviews, decisions, and quality catches.
How do I add state-of-company-publisher to my agent?
Register the MCP server from the Model Context Protocol registry entry for io.github.dailyaiagents-cpu/state-of-company-publisher, wire it to your Hermes or federation agent, and point publish targets at site/state.html and data/state-drafts/ per your hub setup.