contribute-to-cogni

The external contributor workflow for Cogni is managed through a four-phase lifecycle: Implement, Flight, Self-Validate, and Merge. This process coordinates code contributions with durable knowledge capture to ensure proper review and validated deployment signals.

The best way to capture reusable knowledge when submitting PRs to Cogni is by storing artifacts in the knowledge hub via contribute-knowledge-to-cogni. This knowledge-first approach prevents inline comment sprawl and enables future agents to learn from decisions.

Deployment validation during the Cogni PR lifecycle requires documented evidence, specifically deploy_verified status and Loki-based validation. This ensures external contributions meet quality bars before merging during the Self-Validate phase.

Yes, before starting the Cogni contributor lifecycle, you need to read AGENTS.md and the lifecycle specs. This prerequisite ensures alignment with operator workflows and proper PR hygiene before claiming a work item and entering Phase 1.

The Cogni contribution process requires storing artifacts in a knowledge hub to raise the quality bar for governed collaboration. This ensures durable insights and decisions are captured for future agents rather than lost in inline comments.

No, external code contributions to Cogni must undergo the four phases: Implement, Flight, Self-Validate, and Merge. This structured lifecycle enforces alignment with operator workflows and validates deployment signals before changes are accepted.