🦀 Gajae Code

Documentation

Receipts

How Gajae Code-oriented workflows preserve proof: checks, verdicts, summaries, and public-safe evidence trails.

Proof over vibes

Good agent work needs receipts: what was attempted, what passed, what failed, what changed, and what remains blocked. Gajae Code workflows are designed to end with evidence rather than a vague status update.

What counts as evidence?

  • CI run names, conclusions, and links.
  • Local verification commands and summarized results.
  • PR review verdicts such as MERGE_READY or REQUEST_CHANGES.
  • Session state summaries and terminal outcomes.
  • Public-safe artifacts that avoid raw secrets, logs, or private payloads.

Completion contract

A task is not truly done until the result is observable and repeatable: code committed, docs published, tests passed or blockers recorded, and the next operator can understand the state.