How soheylebrahimzadeh/linkedin-content-engine works
linkedin-content-engine is a privacy-first LinkedIn content workflow: an owner provides identity and verified stories, develops strategy and research, prepares and checks a post, decides on imagery, and explicitly approves it before publication. The CLI and scheduler support preparation; publishing can be owner-triggered or scheduled through the Cloudflare Worker. Results and readiness are surfaced through analytics and a read-only dashboard. The graph combines documented workflow links with source-index references; several unsampled capabilities are represented at their exact directories, and their internal call paths are not inferred.
Main entry points: cli.py CLI workflow · scheduler.py Preparation scheduler · store.py Private data files · qa.py Content audit
Components 24
Identity and authoring
- CLI workflow
src/lce/cli.py - Identity interview
src/lce/interview.py - Brand strategy
src/lce/brand.py - Research candidates
src/lce/research.py - Content planning
src/lce/planning.py - Post lifecycle
src/lce/posts.py
Checks and approval
- Privacy safeguards
src/lce/privacy - Content audit
src/lce/qa.py - Image decision
src/lce/images.py - Human approval
src/lce/approval.py
Scheduling and publishing
- Preparation scheduler
src/lce/scheduler.py - Cadence and slots
src/lce/schedule.py - Provider publishing
src/lce/publishing.py - LinkedIn publisher
src/lce/publish/linkedin.py
Cloud publishing
- Cloud API
cloud/src/api.ts - Consent-based runner
cloud/src/runner.ts - Cloud D1 state
cloud/src/db.ts - Cloud LinkedIn
cloud/src/linkedin.ts
Results and visibility
- Performance learning
src/lce/analytics.py - Workflow readiness
src/lce/readiness.py - Read-only dashboard
src/lce/dashboard
Other components
- Content owner
- LinkedIn API
- Private data files
src/lce/store.py
Connections 36
- Content owner → CLI workflow: runs workflow
- CLI workflow → Identity interview: supports interview
src/lce/cli.py - CLI workflow → Research candidates: invokes research
src/lce/cli.py - CLI workflow → Content planning: invokes planning
src/lce/cli.py - CLI workflow → Brand strategy: invokes strategy
src/lce/cli.py - CLI workflow → Content audit: runs checks
src/lce/cli.py - CLI workflow → Human approval: records approval
src/lce/cli.py - CLI workflow → Preparation scheduler: runs automation
src/lce/cli.py - CLI workflow → Provider publishing: publishes approved
src/lce/cli.py - Identity interview → Private data files: stores profile
- Research candidates → Private data files: stores candidates
src/lce/research.py - Content planning → Post lifecycle: selects topics
- Post lifecycle → Private data files: persists lifecycle
src/lce/posts.py - Privacy safeguards → Private data files: scans private data
src/lce/privacy/scan.py - Content audit → Post lifecycle: checks post
src/lce/qa.py - Content audit → Privacy safeguards: checks exposure
src/lce/qa.py - Human approval → Post lifecycle: updates state
src/lce/approval.py - Human approval → Image decision: binds image hash
src/lce/approval.py - Preparation scheduler → Content audit: runs audit
src/lce/scheduler.py - Preparation scheduler → Human approval: handles approval
src/lce/scheduler.py - Preparation scheduler → Image decision: handles imagery
src/lce/scheduler.py - Preparation scheduler → Cadence and slots: loads cadence
src/lce/scheduler.py - Preparation scheduler → Private data files: reads state
src/lce/scheduler.py - Provider publishing → LinkedIn publisher: dispatches provider
- LinkedIn publisher → LinkedIn API: publishes post
src/lce/publish/linkedin.py - CLI workflow → Performance learning: invokes analytics
src/lce/cli.py - CLI workflow → Workflow readiness: checks readiness
src/lce/cli.py - CLI workflow → Read-only dashboard: serves dashboard
src/lce/cli.py - Performance learning → Private data files: reads history
src/lce/analytics.py - Read-only dashboard → Private data files: reads snapshot
src/lce/dashboard/server.py - Content owner → Cloud API: manages consent
- Cloud API → Cloud D1 state: reads and writes
cloud/src/api.ts - Cloud API → Consent-based runner: registers routes
cloud/src/api.ts - Consent-based runner → Cloud D1 state: loads due consent
cloud/src/runner.ts - Consent-based runner → Cloud LinkedIn: publishes due post
cloud/src/runner.ts - Cloud LinkedIn → LinkedIn API: publishes post