hasarak

Make sure no critical system depends on one person.

hasarak finds the code only one engineer has touched, weighs it by how critical it is, and suggests the next issue where someone else can pair in. Over a quarter, each critical module gets a second owner.

Goal12 weeks
Every critical module has two active owners
Week 1Week 12
Start14
Now6
Target0
Critical modules with one active owner
Along the way

From 14 single-owner modules to none.

Week 1
Risk·Infra

Only Priya has changed the auth middleware in 12 months

94% of commits and every review. It handles sessions for all internal tools.

Suggest pairing issueMessage PriyaCritical · 1 owner
Week 5
Follow-up·Infra

ENG-1342 touches the auth middleware and is unassigned

A good first change for Jonas, who asked about session refresh in #platform last month.

Assign to JonasDraft introSecond owner
Week 11
Drift·Payments

The ledger reconciliation job has no docs and its owner is leaving

Omar's last day is Dec 20. He wrote 88% of reconcile.ts and there is no README or runbook.

Draft handover docEmail OmarHandover needed
How it works

One goal, a steady stream of next steps.

You set the goal and how it's measured. hasarak keeps reading, re-ranks what's left every week, and sends each step to the people who own that part of the system. Nothing is posted, opened or moved until someone approves it.

What hasarak reads
  • Commit and review history per module
  • Upcoming issues in that code
  • Questions and answers about it in Slack
01

Map who knows what

Uses commits, reviews and discussions to see who can actually change each module.

02

Pick the next pairing

Finds upcoming issues in that code and suggests who should take them, and with whom.

03

Watch for new gaps

Flags when an owner leaves or changes team, or a new critical module has one author.

Bring your own subscription

Runs on the Claude or ChatGPT plan you already pay for.

Mapping ownership and drafting handover docs runs on the Claude or ChatGPT accounts you connect, with no separate AI plan to buy.

  • No second AI billAnalysis and drafts use the Claude or ChatGPT plan you already have.
  • Pool several accountsConnect work and team accounts. hasarak spreads the load and moves on when one hits its limit.
  • The models you already useSuggestions come from the same models your team uses in Claude Code and Codex.
Connected accounts5-hour window

When Claude · Work runs low, hasarak moves to ChatGPT · Acme team.

FAQ

Questions about ownership

How does hasarak decide what's critical?

You mark the modules, or hasarak suggests them from deploy frequency, incident history and how many services depend on them.

Does it assign work?

It suggests assignments. A team lead approves them.

Does it write documentation?

It drafts handover docs from the code, commits and threads. The owner reviews them.

Which AI model does the work?

The one you connect. hasarak runs on your own Claude or ChatGPT subscription and can use several accounts at once.

More use cases

Cut CI time in halfFind what makes builds slow, fix it, keep it fastReduce on-call loadFewer pages and fewer repeat incidentsFinish a migrationTrack every call site until the old system can be deletedFaster code reviewShorter wait for first review, spread across the team

Find the code only one person knows.