Krisztián at Toloka

Engagement scope proposal · pre-read for the team

For Ksenia, Roman, Borodetskiy · 2026-05-01 · v0.1

Section I of VI

Executive summary

I. Executive summary

Engagement overview: hours, working model, project snapshots, immediate asks.

Overview

II. Working arrangement

Coworking + AI-first ops. No solo product or dev work. Sessions, AI-recorded, team-witnessed.

Established

III. VC Migration

Migrate the built dashboard into Toloka infra; hand it to a future VC-team owner.

Active weeks 2–3

IV. Solver Future State

Workshop with Alejandro; identify owner; capture transferable learnings with Renaud.

Bookend wks 1 + 4

V. Ant Consulting

Co-build the consulting product line with PO + dev. The daily anchor of the engagement.

FOCUS · daily

VI. Master next steps

Living view — every project's next step, owner, deadline, in one place.

Living

This slide reappears at every section divider. The highlighted box is what comes next. · Source: brain/specs/engagement.md · brain/specs/timeline.md · nextsteps.md

About this deck

A living document — updated as the engagement evolves.

What it is

A pre-read on the engagement: the working model, the three concurrent projects, the timeline, and the immediate asks of the team.

Pre-read

How it stays current

Each slide is mapped to source files in the engagement's brain/. When those change, the deck re-renders. Manual edits welcome too.

Auto + manual

Source of truth

The brain/ files are canonical; this deck is the latest snapshot. Reactions in chat fold back into the next render.

Snapshot

Source: AGENTS.md · brain/specs/engagement.md

How this deck was built

An orchestrator + three project sub-agents — the same Claude pattern we'll deploy on Ant Consulting.

The Toloka Orchestrator

A Claude agent dedicated to this engagement. Holds the working model, the timeline, and the master next-steps. Wrote this deck from brain/ notes.

This repo's AGENTS.md

Three project sub-agents

One per project: VC Migration, Solver, Ant Consulting. Each holds its own brain — decisions, scope, people. Their content feeds the deck through a sources: manifest.

projects/<sub>/AGENTS.md

Why this matters. The agentic-colleague pattern is the deliverable, not just the medium. On Ant Consulting we'll set up the same shape — a Claude-built assistant, owned by Toloka internals, that lives on after my engagement ends.

Source: AGENTS.md · projects/<sub>/AGENTS.md

Availability

Up to 4 hours/day until end of May. Not available over the summer.

Hours envelope

  • 4 hr/day, every weekday
  • Roughly 20 hr/week × 4 weeks = ~80 hr through end of May
  • After that: summer gap — no Krisztián

Implication

  • Future owners must be onboarded by end of May
  • All sub-project assistants must be functional and trusted before the gap
  • Decisions parked over the summer need to be documented for clean autumn resume

Source: brain/specs/engagement.md · brain/specs/timeline.md

Working model — top line

No product or dev work alone. Admin and planning, yes — alone is fine.

Product work

Only with the product owner in the session. Decisions land in the room, with witnesses.

PO required

Dev work

Only with the developer (and/or PO) in the session. Same rule, same reason.

Dev required

Admin / planning

Done alone in async blocks — calendar, decks, brain refreshes. That's what solo time is for.

Solo OK

Pre-scheduled

All meetings booked ahead — I always know which session I'm joining.

No drop-ins

AI-first ops

Every session has a Claude agent — notes, drafts, decisions. We co-build with it on Miro and slides.

Always-on

The non-negotiable part: meaningful product / code decisions never land alone in my head. · Source: brain/specs/engagement.md

Project 1 / 3

VC Dashboard Migration — handover from me to a future VC-team owner.

Working model

  • Migration sessions: me + future VC-team owner (TBD)
  • Documenting setup well enough for a clean handover
  • Reusing the migration knowledge as a template for Ant Consulting

Key next steps

  • Identify the future owner
  • Document existing setup for handover
  • Draft migration plan with Toloka infra constraints

Active weeks 2–3 of May · Source: projects/vc-dashboard-migration/

Project 2 / 3

Solver Future State (Zaphod) — workshop + handover, no implementation by me.

Working model

  • Workshop sessions with Alejandro
  • I find a future PO + eng owner; they do the implementation
  • I capture transferable learnings with Renaud Delaguerronnière

Key next steps

  • Schedule workshop with Alejandro
  • Identify future PO + eng owner
  • Co-write learnings doc with Renaud

Active weeks 1 and 4 of May · Source: projects/automated-solver/

Project 3 / 3 — primary focus

Ant Consulting — co-built product solutioning with PO + dev. Daily anchor.

Working model

  • I product-manage but co-own with PO + dev — never single owner
  • Focus areas: backlog · data model · dashboarding (level 2)
  • Automation = high-level direction (level 1) with Renaud
  • We build a project-specific AI assistant alongside delivery

Key next steps

  • Confirm Monday meeting with you three
  • Send this deck (you're reading it)
  • Identify candidate PO + dev
  • Run scope-agreement workshop next week

Active daily, primary focus · Source: projects/ant-consulting/

This week — what I need from you

Five immediate asks.

# Ask Owner
1 Move today's noon meeting to Monday (45 min, all 4 of us) Ksenia / Roman
2 Send responses + comments on this deck Team
3 Start thinking about names for the 5 role categories Team
4 Identify candidate PO for Ant Consulting Krisztián + leadership
5 Identify candidate dev for Ant Consulting Krisztián + leadership

Master next-steps in Section VI · Source: nextsteps.md

Section II of VI

Working arrangement

I. Executive summary

Engagement overview: hours, working model, project snapshots, immediate asks.

Overview

II. Working arrangement

Coworking + AI-first ops. No solo product or dev work. Sessions, AI-recorded, team-witnessed.

Established

III. VC Migration

Migrate the built dashboard into Toloka infra; hand it to a future VC-team owner.

Active weeks 2–3

IV. Solver Future State

Workshop with Alejandro; identify owner; capture transferable learnings with Renaud.

Bookend wks 1 + 4

V. Ant Consulting

Co-build the consulting product line with PO + dev. The daily anchor of the engagement.

FOCUS · daily

VI. Master next steps

Living view — every project's next step, owner, deadline, in one place.

Living

Deep-dive on availability + the coworking + AI-first model. · Source: brain/specs/engagement.md

Coworking is our model

Intentional coworking — for product and dev, always with someone in the room.

What this means practically

  • Product / dev sessions are live and pre-scheduled
  • For product: PO + me, on a call
  • For dev: dev (and/or PO) + me, on a call
  • An AI assistant joins every session, takes notes, and helps us do the work
  • Admin, planning, deck refreshes I handle alone in my async blocks — those don't need the team

What I'm NOT doing

  • Making product or code decisions alone — those land in sessions, with witnesses
  • Producing product or code artifacts the team didn't see come into existence
  • Putting myself in single-owner positions on anything substantive
  • Asking the team to chase me asynchronously on product topics

Trade-off: less of my raw hours land as solo product output. Gain: zero orphan decisions, full continuity for the team after my engagement. · Source: brain/specs/engagement.md

Why we chose this model

Two big wins from coworking.

1. AI-first governance

  • Every session is observed and documented by an AI assistant in real time
  • Decisions are captured as they happen, with full context
  • The team gets transparency into what was decided, why, and by whom
  • Auditability comes for free — and so does institutional memory

2. Team ownership of the product

  • The PO and dev are co-builders, not recipients of artifacts
  • Every artifact has a Toloka-internal owner from day one
  • When my engagement ends, the team owns the product fully — no orphan code, no stranded decisions
  • The AI assistant continues with the team — a colleague that doesn't leave

Source: brain/brain-dumps/2026-05-01-deck-outline-and-multi-agent-architecture.md

How sessions actually run

Screenshare → talk to the assistant together → it co-builds with us.

Who's in the room

Me + at least one of (PO, dev). Others as needed: users, experts, stakeholders.

Min. 2 humans

How we drive

One person drives the conversation with the assistant; the others contribute and steer.

Round-robin OK

What comes out

Real artifacts: slides, Miro boards, code drafts, decision logs. Produced live, with the team.

In-session

What gets kept

Both the outcome (the artifact) and the trace (the conversation, captured to brain/).

Outcome + trace

Pattern: this deck itself is the artifact of an AI-assisted session. The trace is in brain/brain-dumps/. · Source: brain/brain-dumps/2026-05-01-deck-outline-and-multi-agent-architecture.md

The longer-term win

This leads to product continuity past my engagement.

  • Each Toloka product gets a dedicated assistant repository with full decision logs and comprehensive documentation.
  • Repositories are owned by Toloka internals — a PO and (where applicable) a developer.
  • Onboarding to the assistant repo is itself a deliverable — by the time I leave, the future PO and dev are comfortable working with the assistant.
  • After my engagement: the assistant remains; the team has a colleague that doesn't churn out.

This repo (`krisztian-at-toloka`) is the engagement-level instance of this pattern. · Source: brain/specs/engagement.md · brain/brain-dumps/2026-05-01-deck-outline-and-multi-agent-architecture.md

Hours allocation

Project timeline — May 2026 (placeholder hours).

Project / area Week 1 Week 2 Week 3 Week 4
Admin ~2h ~2h ~2h ~2h
VC Dashboard Migration low 8h focus 8h focus low
Solver Future State 6h focus low low 6h focus
Ant Consulting residual residual residual residual
Total ~20h ~20h ~20h ~20h

⚠️ Krisztián is not available over the summer. All handovers must complete by end of May.

Hours are placeholders — Krisztián replaces with calendar-derived numbers. · Source: brain/specs/timeline.md

Section III of VI

VC Dashboard Migration

I. Executive summary

Engagement overview: hours, working model, project snapshots, immediate asks.

Overview

II. Working arrangement

Coworking + AI-first ops. No solo product or dev work. Sessions, AI-recorded, team-witnessed.

Established

III. VC Migration

Migrate the built dashboard into Toloka infra; hand it to a future VC-team owner.

Active weeks 2–3

IV. Solver Future State

Workshop with Alejandro; identify owner; capture transferable learnings with Renaud.

Bookend wks 1 + 4

V. Ant Consulting

Co-build the consulting product line with PO + dev. The daily anchor of the engagement.

FOCUS · daily

VI. Master next steps

Living view — every project's next step, owner, deadline, in one place.

Living

Migrate the built dashboard into Toloka infra; hand to a future VC-team owner. · Source: projects/vc-dashboard-migration/

Project 1 — summary

Migrate the built VC dashboard into Toloka infra. Hand it to a VC-team owner.

  • Status: active, weeks 2–3 of May 2026 dedicated focus.
  • Krisztián's role: owner-temporary. Migrating + handing over, not owning long-term.
  • Audience: the future VC-team owner (TBD), Ksenia / Roman / Borodetskiy for visibility.
  • Reuse: the migration playbook becomes a reusable template for the Ant Consulting work.

Source: projects/vc-dashboard-migration/AGENTS.md

Project 1 — scope & completion

Built dashboard exists. The work is moving it + writing the handover doc.

In scope

  • Migration of existing codebase + data into Toloka infra
  • Knowledge-transfer documentation
  • Onboarding the future VC-team owner

Out of scope

  • New features beyond what's already shipped
  • Long-term ownership — Krisztián is migrating + handing over only
  • Re-platforming to a different stack

Source: projects/vc-dashboard-migration/AGENTS.md

Project 1 — timeline

Two-week dedicated window: May 12–25.

  • Week 2 (May 12-18): migration work + handover doc started
  • Week 3 (May 19-25): future owner onboarded; co-driving final cuts of the migration; handover doc finalized
  • Weeks 1 and 4: light support only — focus is elsewhere

Source: projects/vc-dashboard-migration/brain/specs/timeline.md (TBD by sub-agent)

Project 1 — open questions & next steps

Three open questions, three immediate next steps.

Open

  • Who's the future VC-team owner?
  • What's Toloka's infra position — own cluster, shared, hosted?
  • Is there existing dashboard documentation to reuse, or do we capture from scratch?

Next

  • Identify the future owner
  • Document existing setup
  • Draft migration plan w/ Toloka infra constraints

Source: projects/vc-dashboard-migration/nextsteps.md

Project 1 — decision log

Decisions captured in the project's decision log.

No decisions logged yet — project is just starting.

The decision log lives at projects/vc-dashboard-migration/brain/decisions/. Numbered ADRs (Context / Decision / Consequences). Maintained by the Virtual Companies Migration Assistant.

Backup slides per decision are added when a decision warrants its own page.

Source: projects/vc-dashboard-migration/brain/decisions/

Section IV of VI

Solver Future State

I. Executive summary

Engagement overview: hours, working model, project snapshots, immediate asks.

Overview

II. Working arrangement

Coworking + AI-first ops. No solo product or dev work. Sessions, AI-recorded, team-witnessed.

Established

III. VC Migration

Migrate the built dashboard into Toloka infra; hand it to a future VC-team owner.

Active weeks 2–3

IV. Solver Future State

Workshop with Alejandro; identify owner; capture transferable learnings with Renaud.

Bookend wks 1 + 4

V. Ant Consulting

Co-build the consulting product line with PO + dev. The daily anchor of the engagement.

FOCUS · daily

VI. Master next steps

Living view — every project's next step, owner, deadline, in one place.

Living

Workshop with Alejandro; identify owner; capture learnings with Renaud. · Source: projects/automated-solver/

Project 2 — summary

Workshop with Alejandro on Zaphod's future. I roadmap; the future owner builds.

  • Status: active, weeks 1 and 4 of May 2026 dedicated focus.
  • Krisztián's role: roadmap-only — workshops, identifies future owner, captures learnings for reuse.
  • Audience: Alejandro, future PO/eng owner (TBD), Renaud Delaguerronnière, Ksenia / Roman.
  • Background: Zaphod was functional but never scaled. The engagement productizes it under a new owner.

Source: projects/automated-solver/AGENTS.md

Project 2 — scope & completion

Workshop, identify owner, hand over. Capture learnings for the consulting work.

In scope

  • Workshop with Alejandro on his ideas + needs
  • Identifying + onboarding a future PO/eng owner
  • Co-writing transferable-learnings doc with Renaud

Out of scope

  • Krisztián implementing the future state himself
  • Scaling the existing Zaphod
  • Going beyond roadmap — implementation is the future owner's

Source: projects/automated-solver/AGENTS.md

Project 2 — timeline

Bookend the month — workshop in week 1, learnings in week 4.

  • Week 1 (May 5-11): workshop with Alejandro + future-state design output
  • Weeks 2-3: light support; primary attention is elsewhere
  • Week 4 (May 26-31): transferable-learnings doc co-written with Renaud

Source: projects/automated-solver/brain/specs/timeline.md (TBD by sub-agent)

Project 2 — open questions & next steps

Three opens, three next.

Open

  • Does Alejandro have a target architecture in mind?
  • Is the future owner internal or a new hire?
  • How does the AI-assistant pattern land in Alejandro's project?

Next

  • Schedule workshop with Alejandro (week 1)
  • Identify future PO + eng owner
  • Co-write learnings doc with Renaud (week 4)

Source: projects/automated-solver/nextsteps.md

Project 2 — decision log

Decisions captured in the project's decision log.

No decisions logged yet — project is just starting.

The decision log lives at projects/automated-solver/brain/decisions/. Numbered ADRs. Maintained by the Solver Future State Assistant.

Source: projects/automated-solver/brain/decisions/

Section V of VI

Ant Consulting

I. Executive summary

Engagement overview: hours, working model, project snapshots, immediate asks.

Overview

II. Working arrangement

Coworking + AI-first ops. No solo product or dev work. Sessions, AI-recorded, team-witnessed.

Established

III. VC Migration

Migrate the built dashboard into Toloka infra; hand it to a future VC-team owner.

Active weeks 2–3

IV. Solver Future State

Workshop with Alejandro; identify owner; capture transferable learnings with Renaud.

Bookend wks 1 + 4

V. Ant Consulting

Co-build the consulting product line with PO + dev. The daily anchor of the engagement.

FOCUS · daily

VI. Master next steps

Living view — every project's next step, owner, deadline, in one place.

Living

Co-build the consulting product line with PO + dev. The daily anchor. · Source: projects/ant-consulting/

Project 3 — summary (primary focus)

Co-build the consulting product line with PO + dev. Daily anchor of the engagement.

  • Status: active, daily, primary focus item.
  • Krisztián's role: product-management + co-implementation. Co-owned with PO + dev — never single owner.
  • Audience: Ksenia, Roman, Borodetskiy, Renaud Delaguerronnière, future PO + dev.
  • The pattern: while delivering, we also build a project-specific AI assistant for the team — coworking + vibe-coding capability that survives my engagement.

Source: projects/ant-consulting/AGENTS.md

Project 3 — scope & working areas

Four working areas. Two are level-2 (focus). Two are level-1 (direction).

Area Level What I do
Backlog 2 (focus) Product-manage with PO; we shape the backlog together
Data model 2 (focus) Co-design with PO + dev; sessions land decisions in the assistant repo
Dashboarding 2 (focus) Co-design; reuse the VC migration playbook
Automation 1 (high-level direction) Align with Renaud on direction; realistic timeline; don't dive into delivery

Levels per the 0/1/2 scope framework — see Section II.1. · Source: projects/ant-consulting/AGENTS.md

Project 3 — timeline

Daily anchor; week 1 is scope + team setup; weeks 2-4 are delivery.

  • Week 1 (May 5-11): scope agreement, role allocation (PO + dev identified), AI-enabled repo setup, product decisions (backlog, data model, dashboarding, automation direction)
  • Weeks 2-3: delivery on focus items, paired with PO + dev (residual hours after VC migration block)
  • Week 4: continued delivery + summer-handover prep so the team can run without me

Source: projects/ant-consulting/brain/specs/timeline.md (TBD by sub-agent)

Project 3 — open questions & next steps

Five immediate, five for next week.

This week

  • Confirm Monday meeting (all 4 of us)
  • Send pre-read deck (this one)
  • Get team responses on role-category names
  • Identify candidate PO
  • Identify candidate dev

Next week (if Monday confirms)

  • Run scope-agreement workshop (0/1/2 every topic)
  • Resource-to-role allocation (PO + dev assigned)
  • Set up AI-enabled repo, onboard PO + dev
  • Product decisions: backlog · data model · dashboarding
  • Align with Renaud on automation direction

Source: projects/ant-consulting/nextsteps.md

Project 3 — decision log

Decisions captured in the project's decision log.

No decisions logged yet — project is just starting.

The decision log lives at projects/ant-consulting/brain/decisions/. Numbered ADRs. Maintained by the Ant Consulting Project Assistant with Krisztián, the PO, and the dev.

Source: projects/ant-consulting/brain/decisions/

Section VI of VI

Master next steps

I. Executive summary

Engagement overview: hours, working model, project snapshots, immediate asks.

Overview

II. Working arrangement

Coworking + AI-first ops. No solo product or dev work. Sessions, AI-recorded, team-witnessed.

Established

III. VC Migration

Migrate the built dashboard into Toloka infra; hand it to a future VC-team owner.

Active weeks 2–3

IV. Solver Future State

Workshop with Alejandro; identify owner; capture transferable learnings with Renaud.

Bookend wks 1 + 4

V. Ant Consulting

Co-build the consulting product line with PO + dev. The daily anchor of the engagement.

FOCUS · daily

VI. Master next steps

Living view — every project's next step, owner, deadline, in one place.

Living

Living view — every project's next step, owner, deadline. · Source: nextsteps.md

All projects + admin in one view (1/2)

What needs to happen, who owns it, by when.

Area Next step Owner Deadline
Admin Move today's noon meeting to Monday Ksenia / Roman This week
Admin Block 2-4hr Toloka work blocks on calendar Krisztián This week
VC Migration Identify future VC-team owner Krisztián + VC team TBD
VC Migration Document existing setup for handover Krisztián Weeks 2-3
Solver Schedule workshop with Alejandro Krisztián + Alejandro Week 1
Solver Identify future PO + eng owner Krisztián + leadership TBD
Solver Co-write learnings doc with Renaud Krisztián + Renaud Week 4

Continued on next slide. · Source: nextsteps.md (master)

All projects + admin in one view (2/2)

Ant Consulting next steps.

Area Next step Owner Deadline
Ant Consulting Confirm Monday meeting Ksenia / Roman This week
Ant Consulting Send pre-read deck (this one) Krisztián Late today / early tomorrow
Ant Consulting Read deck + send responses Team Before Monday
Ant Consulting Name the 5 role categories Team Before Monday
Ant Consulting Identify candidate PO Krisztián + leadership Before Monday if possible
Ant Consulting Identify candidate dev Krisztián + leadership Before Monday if possible

Living view — orchestrator updates from sub-agent nextsteps.md files. · Source: nextsteps.md (master) · projects/ant-consulting/nextsteps.md

Thank you.

Reactions, questions, and edits: reply in the chat — they fold back into the next deck render.

Krisztián · 2026-05-01 · engagement-scope pre-read