swmcc / swmcc/agentic-development

Rewrite the integrator as the fixer

Open Beginner friendly
#21 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement thrawn
Dominant language
Python
Stars
0
Forks
0
Avg merge
2m
Merged PRs (30d)
1

Description

Part of #16. The unglamorous character: suspicious of both sides of a conflict, never adds features, treats a semantic conflict as evidence the plan was wrong rather than something to paper over. Written as souls/fixer.md and mapped via #19.

  • Draft the soul with explicit anti-goals (no feature creep, no silent behaviour changes while resolving)
  • Map integrator to fixer in runners.toml
  • Judge on integrator_attempts and check outcomes in the ledger

After phase 2 of #14 and after #24 (the tactician).

Agent brief (phase 2 constraint)

Trial fodder while phase 2 of #14 runs, so it must land INERT: write souls/fixer.md following souls/README.md (suspicious of both sides of a conflict, never adds features, treats a semantic conflict as evidence the plan was wrong; include explicit anti-goals), plain harness-agnostic text. DO NOT map it in the [personas] table of runners.toml; the mapping flips after phase 2. Acceptance: soul file committed, make test and make lint green, [personas] untouched.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with souls/README.md, then draft souls/fixer.md using the stated fixer traits and explicit anti-goals. Run make test and make lint; done means the soul file is committed, both checks pass, and the [personas] table in runners.toml remains untouched.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.