Turn attention into proof, not noise.

The Presence Engine turns the offer and pipeline into a local LinkedIn/X plan: 30 drafts, 30 daily actions, 5 content pillars, manual engagement blocks, CTA map, reply bank, scorecard, and guardrails.

Simple layer. Presence is not posting more. Presence is showing useful proof, starting qualified conversations, and moving real signals into the pipeline.

The generator reads local offer, acquisition, pipeline, daily, weekly, and revenue artifacts, writes Markdown and JSON, and creates a cockpit import with content rows, rhythm rows, capture tasks, and pipeline signals. It does not call LinkedIn, X, email, or any external API.

Run the engine

node work/life-os-presence-engine.mjs
# or
node work/life-os.mjs presence

# then open:
outputs/life-os-command-center/presence-engine.md

The five pillars

ProofBefore/after, decisions, and evidence.

TeachingA small AI Ops lens the reader can use.

DiagnosticQuestions that reveal real pain.

OfferWho it helps, what ships, and how to start.

Behind scenesProcess without private details.

Manual-only guardrails

The engine prepares drafts and tasks. You review manually before publishing. No automatic posts, no automatic DMs, no private local paths, no client data, no revenue guarantees, and no placeholders left in public copy.

Import into the cockpit

outputs/life-os-command-center/presence-import.json

Proof from this run: the engine writes 30 post drafts, 30 rhythm rows, 14 engagement blocks, 5 pillars, and a cockpit import with no private source fields.