Contribution Lifecycle

Purpose

This lifecycle keeps contributor work, AI-generated work, and founder intent reviewable without turning the repository into a raw prompt archive.

Flow

Idea / prompt / issue
  -> curated brief
  -> RFC / ADR when needed
  -> task graph
  -> scoped implementation or docs change
  -> validation
  -> integration report
  -> release plan or roadmap update

Raw Prompt Policy

Raw prompt streams and long chat transcripts should not directly pollute the monorepo.

The repo stores:

• Curated summaries.
• Decisions.
• Templates.
• Reusable prompts.
• Task graphs.
• Run logs.
• Integration reports.

Raw conversations can live in external collaboration tools, private archives, or a separate knowledge repository. Only distilled outputs become ADRs, RFCs, AI decision records, issues, PRs, docs, or roadmap updates.

Contributor Intake

Every contributor task should define:

• Mission.
• Allowed paths.
• Forbidden paths.
• Required reading.
• Output expected.
• Validation commands.
• Reviewer or owner role.

Review Closure

A contribution is not done until the reviewer can answer:

• What changed?
• Which source of truth moved?
• Which docs or roadmap entries were updated?
• Which checks ran?
• What is still risky or deferred?