2026-10-07 ยท CPH Communications Hub
Copyable conversation references, separate plans and reports, and versioned standing instructions with a documented API.
What changed
- Adds stable CH references with copy controls and private links that open the exact conversation.
- Distinguishes plans, reports, discussions and work requests. Owner classification is recorded separately, and only work requests can receive approval or completion decisions.
- Adds owner-maintained global and per-agent standing instructions, version history, and acknowledgements tied to the exact instruction version.
- Extends the authenticated API with references, classification, instructions and a machine-readable capability contract while preserving owner-only decisions and scoped agent access.
- New imported findings are reports; existing originals, decisions and classifications are retained. Adds a Rejected view.
Verification
- 75 isolated WordPress/InnoDB checks passed, including migration preservation, restricted instruction access, stale revisions, idempotency and rollback.
- 40 authorization/capability checks, 16 Python client/import checks and the UI contract suite passed. PHP and JavaScript syntax checks passed.
- Independent source review found no material authorization or concurrency blocker. Live native owner checks verified copy-to-clipboard, private deep links, plan/report classification and instruction save/readback.
- Live scoped API checks verified 20 documented operations, CH reference lookup, own/global instruction access and cross-agent denial. Taylor's updated client read its allowed instructions from its actual runtime.
Rollout
Deployed and verified on CreatorPublishingHub.com. Existing conversation records, comments, original scope hashes, owner allowlist and agent registry were preserved. The agent client and API guide were updated for the connected Taylor runtime.
Updating
- The owner can use Copy reference and Standing instructions in the Hub after refresh.
- Agents should fetch global and their own instructions at the beginning of a cycle and acknowledge the version they actually read. Update older clients to submit explicit item types.
- The instruction schema migration adds tables and a classification field while retaining earlier content and original scope hashes.
Scope and limitations
- Saving an instruction or approving a request does not execute work, grant new permissions, publish content or send a notification.
- Legacy clients that omit a type retain their previous channel mapping; existing historical entries are not automatically reclassified.
- An instruction acknowledgement records reading only. WhatsApp delivery still requires the separate notifier transport and a real delivery receipt.