Evidence in, draft out
The pipeline reads eligible source events for a project, classifies work, prepares a concise draft and checks factual claims and privacy rules. It stores source references and provenance for review. It does not store repository source code as draft evidence.
A coding agent can create a source-backed draft through the shared operation registry. That request creates a draft; it does not schedule or publish it.
Publication policies
- Review: drafts wait for an explicit publish action.
- Veto: eligible drafts may be scheduled after the configured veto period. A held draft still waits for review.
- Auto: eligible drafts may be scheduled without a veto delay. A held draft still waits for review.
- The project daily limit is one automatic publication. Quiet periods, skip rules, source exclusions and safety checks can leave work unpublished.
Review gates
A draft can be held when evidence is insufficient, a number cannot be verified, a customer or teammate is mentioned, private information is detected, repository access changes, or an edit needs a fresh check. Review the linked evidence and resolve the reason before releasing or publishing.
The public update is written only after the publication operation succeeds. X and LinkedIn are separate optional output channels and require their own provider connection and deployment support.
This page describes the checked-in IndieLogs implementation. Provider credentials, feature flags and account entitlements are deployment-specific.