Skip to content
Merged
Show file tree
Hide file tree
Changes from 7 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
Binary file removed .agents/research/chatgpt-logged-out.png
Binary file not shown.
663 changes: 663 additions & 0 deletions .agents/research/url-content-fetching.md

Large diffs are not rendered by default.

64 changes: 64 additions & 0 deletions .agents/workflows/correctness-decision-workflow.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
# Workflow: Correctness-First Decision

Use this workflow for medium/high-risk tasks to prioritize robust, industry-standard solutions over quick fixes.

## Goal

- Preserve high implementation quality with explicit design decisions.
- Keep always-on context minimal by loading this workflow only when needed.

## Step 1: Risk Triage

Classify the task before coding:

- **Low risk:** localized refactor, copy changes, non-behavioral cleanup.
- **Medium risk:** behavior changes in one subsystem, moderate user impact.
- **High risk:** auth, schema/data model, API contracts, persistence, concurrency, migrations, billing/payments, security-critical paths.

If the task is medium/high risk, continue with this workflow.

## Step 2: Evaluate Approaches (Short ADR)

Document a brief decision note:

1. Problem and constraints.
2. Candidate approaches (2-3 options).
3. Chosen approach and why it is safer/clearer long-term.
4. Why alternatives were rejected.
5. Failure modes and rollback plan.

Keep it concise. This is for decision quality, not long-form documentation.

## Step 3: Industry-Standard Gate

Before introducing new patterns or dependencies, verify:

- Existing project pattern cannot reasonably solve the problem.
- Proposed approach is mature and actively maintained.
- Security and operational implications are acceptable.
- Migration and maintenance cost are understood.

If the new dependency is optional or convenience-only, prefer existing patterns.

## Step 4: Implementation Discipline

- Implement smallest change that satisfies the specification.
- Preserve existing architecture boundaries.
- Avoid speculative abstractions.
- Add concise comments only where logic is non-obvious.

## Step 5: Risk-Scaled Validation

- **Low risk:** targeted tests/checks for touched behavior.
- **Medium risk:** targeted + affected integration path tests.
- **High risk:** targeted + integration + regression/failure-mode checks.

Compilation, lint, and type checks are necessary but not sufficient for medium/high risk.

## Step 6: Final Review Checklist

- Chosen approach addresses root cause.
- Trade-offs were considered, not guessed.
- Changes match project patterns unless deviation is justified.
- Validation depth matches risk tier.
- Residual risks are explicitly noted in handoff/report.
3 changes: 3 additions & 0 deletions .env.example
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,9 @@ OPENAI_API_KEY=

# Anthropic (Claude) - https://console.anthropic.com/
ANTHROPIC_API_KEY=
# Set to "false" to disable the token-efficient-tools beta header for Anthropic.
# Used for A/B benchmarking tool token usage. Default: enabled.
# ANTHROPIC_TOKEN_EFFICIENT_TOOLS=false

# Google (Gemini) - https://aistudio.google.com/apikey
GOOGLE_GENERATIVE_AI_API_KEY=
Expand Down
Loading