POP Brand Manager · standalone pipeline · 16 October 2026

Existing machinery.
One accountable lane.

POP is now a standalone Brand Manager pipeline outside the shared cockpit. Its proven proposal, rendering, approval and manual-post handoff code remains unchanged. Telegram and the dedicated #pop Slack channel are its operating front doors.

Live outside the shared cockpit and verified on the VPS on 16 October through PR #520: pop-cos-cadence.timer is active and enabled; the superseded mphoka-pop-proposals.timer and mphoka-pop-proposal-cadence.timer are inactive and disabled. Slack #pop messages and controls enter pop-cos directly. pop_pipeline_v2.py, proposal cadence, approval identity and publication-job modules remain unchanged. Approved items are sent to Telegram and #pop as exact images and copy blocks for Mphoka to post manually. Replying posted creates a bound live-URL reconciliation request; the URL lookup is not yet a proven end-to-end receipt path.

Brand
POP / Hustle Dad Online Mphoka's personal Facebook profile
What exists
Proposal-to-manual-post flow cadence, copy, images, approvals and packets
Owner
POP Brand Manager reports later to the portfolio CEO
Status
Active · standalone active cadence and review paths use the manager

What exists now

retain and wrap
Proposal cadenceactive VPS timeractive

Slot-based proposals run through pop-cos-cadence.timer. Both superseded cockpit POP timers are disabled.

Copy and validationpop_pipeline_v2.pyinstalled

Creates the POP content types, validates required fields and retains exact approved copy.

Rendererlocal templates and approved assetsinstalled

Story, lifestyle and two-frame Soft-Offer assets use the existing POP rendering rules. The two Soft-Offer images remain separate ordered frames.

Approval identityhash-bound and idempotentinstalled

Approval binds exact copy and assets to the Content Factory and Publishing Queue. A changed item needs a new approval.

Manual publishing packetTelegram and #popinstalled

After approval, Telegram and the dedicated #pop channel receive the image or ordered frames plus exact copy in blocks that are easy to copy. Mphoka publishes on Facebook.

Publication receiptposted → live URLnot proven

The posted reply is bound to the exact approval and requests URL reconciliation. Publication is complete only after the exact live URL is retrieved and Notion is updated; that full path still needs acceptance.

Target POP lane

one manager, small specialist team
POP Brand Managerowns cadence, delegation, approval presentation, exceptions and reporting
Copywriterexisting POP generation

Produces only the scheduled slot requested by the Brand Manager from current POP rules and context.

Rendererexisting templates

Builds the required approved preview assets and returns exact asset evidence.

Publishing Conciergemanual packet, no Facebook control

Sends the exact approved image and copy to Telegram and the dedicated #pop Slack channel. It never clicks Post or claims publication.

Receiptexact live URL

After Mphoka replies posted, reconciles the exact Facebook URL and updates only the bound rows.

Metrics and Signallearn from verified posts

Records available performance evidence and returns lessons to the Brand Manager without changing approved content.

Operating flow

the Brand Manager owns every handoff
1 · Choose slotcadence and current state

Exactly one due slot is delegated. Empty or intentionally skipped slots remain quiet.

2 · Create packagecopy plus required assets

Copywriter and Renderer return one complete review package.

3 · Human approvalTelegram or Slack

Mphoka approves, edits or rejects the exact package. Silence never approves.

4 · Manual postcopy-ready packet

The Publishing Concierge sends the approved assets and copy. Mphoka posts them on Facebook and replies posted.

5 · Verifylive URL and Notion

The Receipt agent finds the exact live item, writes its URL and marks success only after readback.

Build sequence

reuse first, isolate second
1 · Freeze the contractinventory and boundaries

Record every current POP module, timer, Notion property, approval identity and front-door callback. Identify obsolete browser-publisher and relay remnants without deleting them.

2 · Create the lanesingle façade and private ledgerbuilt

The POP Brand Manager now fronts the existing cadence, review, packet and receipt commands. It records content-free operational events in its own ledger. No duplicate generator, renderer, approval system, scheduler or publisher was added.

3 · Prove one slotproposal to exact live URL

Run one approved item through generation, human approval, manual publication and receipt reconciliation, with no duplicate packet or row.

4 · Prove all content typesincluding two-frame Story

Verify Opening/Closing Story, Primary, Psychology, Comment Ladder, both Soft-Offer frames and Story Amplification where still retained.

5 · Cut over oncedisable duplicate cockpit routeslive

PR #520 routes #pop messages and controls directly to pop-cos. Its cadence timer is active; both cockpit POP timers are disabled. The existing business workflow and rollback path remain intact.

6 · Connect the CEO latermanager-to-CEO contract

The future CEO asks the POP Brand Manager for work or status and receives a structured result. It does not address POP agents directly.

Acceptance gates

required before any cutover
Exact handoffone eligible itemopen

One slot produces one proposal, one approval record and one manual packet on each configured front door without duplicates.

Two-frame integritySoft-Offer Storyopen

Both distinct approved images arrive in frame order and are reconciled as one approved product without losing either frame.

Receipt truthno URL, no Publishedopen

A posted reply alone cannot mark success. The exact live Facebook URL and Notion readback are required.

Manager ownershipstandalone POP laneactive

The live runtime routes scheduled cadence, Telegram and #pop review decisions, manual packets and posted receipts through the POP Brand Manager. pop-cos-cadence.timer is the sole active cadence timer.