Distribution Board
This is the execution layer under DISTRIBUTION_ENGINE.md.
The engine explains the logic.
This board makes the work happen.
Active Week: 2026-04-18
Week Of
- Week: 2026-04-18
- Goal: publish the first visible proof loop for the PM Operating System
- Owner: repo operator
Asset 1: Real Case Breakdown
Asset 2: Benchmark Artifact
Discovery Sweep
- Directory or list: awesome lists, agent skill directories, AI tool directories
- Submission asset: benchmark baseline + flagship cases + product surface
- Status:
planned
- Link: LEADERBOARD.md, FLAGSHIP_CASES.md, Product Surface
- Result: waiting for first manual submission sweep
Monthly Review Snapshot
- Toolkit visits: not connected to shared analytics yet
- Benchmark page visits: not connected to shared analytics yet
- Copy actions: browser-local instrumentation added, no aggregate view yet
- Stars: check GitHub manually
- Forks: check GitHub manually
- Inbound mentions: not collected yet
- Which asset drove the most discovery: unknown
- Which asset had the highest save or click intent: unknown
Weekly Board Template
Week Of
Asset 1: Real Case Breakdown
- Topic:
- Source file:
- Post format:
- Channel:
- Status:
planned / drafting / published
- Link:
- Result:
Asset 2: Benchmark Artifact
- Topic:
- Case or run:
- Failure pattern:
- Channel:
- Status:
planned / drafting / published
- Link:
- Result:
- Scenario:
- Source
skill or command:
- Demo angle:
- Channel:
- Status:
planned / drafting / published
- Link:
- Result:
Discovery Sweep
- Directory or list:
- Submission asset:
- Status:
planned / submitted / refreshed
- Link:
- Result:
Monthly Review
- Toolkit visits:
- Benchmark page visits:
- Copy actions:
- Stars:
- Forks:
- Inbound mentions:
- Which asset drove the most discovery:
- Which asset had the highest save or click intent:
Decision Rule
If one of these is missing by week end:
- one case
- one benchmark artifact
- one toolkit demo
- one discovery action
then distribution stalled that week.