Publish to IndieLogs
- Review the draft title, body, evidence, fact checks, image and publication date.
- Resolve held checks and recheck after editing.
- Publish explicitly from the desk, API or MCP. A publication call does not guarantee any separately configured external output succeeded.
External output channels
X and LinkedIn delivery require an owner connection, valid provider permissions, channel selection and outbound delivery enabled by the operator. The weekly edition email path requires email configuration and a confirmed subscriber. A changelog embed reads public project content; hiding IndieLogs branding is a plan-gated display option.
Provider connection state, tokens and delivery receipts are independent. A successful IndieLogs publication is not proof of a public X/LinkedIn post or email delivery.
Deployment controls
- Database writes are guarded by DATABASE_WRITES_ENABLED.
- Provider and AI calls are guarded by OUTBOUND_ENABLED.
- If either gate or a provider prerequisite is missing, the relevant action can fail even when the control is visible.
This page describes the checked-in IndieLogs implementation. Provider credentials, feature flags and account entitlements are deployment-specific.