Agent activity
Every action Current has taken on this plan, with the actor, tool, records touched, checks that ran and whether it can be undone. This is the log, not a summary of it.
Data Platform capacity gap
The plan has not been approved, so nothing has run yet. Every action below is prepared and waiting.
- Verify plan permissionsPermission engineL1
Re-checked every grant this plan depends on at execution time, not at planning time. One grant had changed since the plan was drafted and was re-confirmed.
Data accessed- Role grants — Priya RaghunathanIAM-2211
- Cost-centre viewer grant — R&DIAM-0043
Policy checkEvery action in this plan falls inside the approver’s authority.Permission checkApprover holds plan-owner and hiring-manager grants.ReversibleYes — Read-only check. Nothing written. - Identify internal capability matchEmployee Graph · skill adjacencyL1
Compared the migration workstream’s capability requirements against delivered work and learning records across 96 in-family engineers. Two profiles cleared the adjacency threshold.
Data accessed- Skill graph — Data Platform adjacencySKILL-ADJ-0912
- Migration workstream scopePLAN-FY26-Q4 · ws-3
Policy checkProtected attributes and performance ratings are excluded from adjacency at the feature layer.Permission checkInternal mobility search, granted by an approved position in the job family.ReversibleYes — Read-only. No record was written and nobody was contacted.Depends on: plan-permissions
- Draft development planPerformance · development plansL2
A 6-week plan against the one material gap: schema translation fundamentals, backfill validation, and two shadowing sessions before the departing engineer leaves.
Data accessed- Skill profile — Maya ChenEMP-5120 · skills
Policy checkDraft only. A development plan is not binding until the manager shares it.Permission checkDrafted to Tomas Lindqvist, her manager of record. Not published.ReversibleYes — Draft can be deleted with no record change.Depends on: build-match
- Hold learning seatsLearning · enrollmentL3
Reserved two seats on the Sep 14 Warehouse Migration Fundamentals cohort. A hold costs nothing and expires by itself — it exists so the cohort is still available if the answer is yes.
Data accessed- Learning path LP-214LP-214 · Sep 14 cohort
Policy checkReservation carries no cost and no obligation until activated.Permission checkLearning admin grant, delegated by the plan approval.ReversibleYes — Expires automatically after 14 days if not activated.Depends on: build-dev-plan
- Prepare the manager conversationPerformance · 1:1sL2
Talking points for Tomas: the assignment, what changes for six weeks, what does not change (level, title, pay), and how to record a decline without consequence.
Data accessed- Next scheduled 1:1MTG-77120 · Sep 4
Policy checkRedeployment must be offered by the manager and may be declined.Permission checkAgenda visible to Tomas Lindqvist only.ReversibleYes — A draft attached to a meeting. Deleting it changes nothing else.Depends on: build-dev-plan
- Manager offers the assignmentHuman decisionL2
Everything Current can prepare is prepared. The offer is a conversation between Maya and her manager, and the answer is hers.
Data accessed- Development plan DEV-8841DEV-8841
Policy checkPeople policy §7.2 — internal mobility requires manager offer and employee consent.Permission checkCurrent cannot make or communicate this offer under any delegation.ReversibleYes — Nothing is written until an answer is recorded.Depends on: build-agenda, build-reserve-seat
- Activate learning enrollmentLearning · enrollmentL3
Converted the seat hold into a real enrollment on the Sep 14 cohort, and scheduled the two shadowing sessions before Sep 26.
Data accessed- Learning path LP-214LP-214 · Sep 14 cohort
- Calendar — Arun PatelCAL-4417
Policy checkActivation permitted only after a recorded acceptance.Permission checkLearning admin grant, delegated by the plan approval.ReversibleYes — Enrollment can be withdrawn before the cohort starts.Depends on: build-offer
- Record the workstream assignmentHeadcount Planning · allocationsL3
Moved Maya onto the migration workstream in the delivery plan and reduced her billing-pipeline allocation. No change to level, title or compensation, and nothing written to her performance record.
Data accessed- Q4 delivery planPLAN-FY26-Q4 · ws-3
Policy checkAllocation change only. Compensation policy §5.4 is not engaged.Permission checkPlan-owner grant on the Q4 delivery plan.ReversibleYes — Allocation is an editable field with full history.Depends on: build-offer
- Confirm requisition and reset the briefRecruiting · requisitionsL3
Position 2291 stays open, unchanged in scope, level and band. Target start moves to Nov 30 to match the pipeline. Because the contractor covers the near-term work, this search now optimizes for durable capability rather than speed.
Data accessed- Position 2291REQ-2291
Policy checkNo change to approved budget or compensation band.Permission checkHiring-manager grant on REQ-2291.ReversibleYes — Target date is an editable field with full history.Depends on: plan-permissions
- Build the success profileRecruiting · success profilesL2
Combined the requisition, the job architecture, the migration’s capability requirements, the approved band and the hiring manager’s criteria — plus one hypothesis drawn from seven comparable hires, labeled as a hypothesis.
Data accessed- Position 2291REQ-2291
- Job architecture — Data Engineering L5JOB-DE-L5
- Ramp outcomes, de-identifiedCOHORT-DE-24M · n=7
Policy checkCohort outcomes are aggregated and de-identified. No individual performance record is an input.Permission checkHiring-manager grant plus aggregate-outcomes read.ReversibleYes — A draft profile. Every criterion is editable and sourced.Depends on: buy-requisition
- Derive targeting criteriaRecruiting · targetingL2
Turned the success profile into the only fields sourcing may read. Protected attributes and their proxies are not passed to the evaluator — they are absent from the candidate record shape, not filtered out downstream.
Data accessed- Success profileSP-2291 · v3
Policy checkResponsible-use policy §3 — enforced by the candidate record shape.Permission checkTargeting criteria are visible to the recruiting team before use.ReversibleYes — Criteria are versioned; v3 supersedes v2 and both are retained.Depends on: buy-success-profile
- Discover candidate poolRecruiting · sourcingL1
Searched the talent pool and prior applicants against criteria v3. Six profiles carry evidence against the required criteria; one is held because the approved band does not reach their current level.
Data accessed- Talent pool — Data EngineeringPOOL-DE
- Prior applicants, consentedAPP-ARCHIVE · opt-in only
Policy checkRead-only discovery. No candidate is ranked, scored or dispositioned.Permission checkSourcing read granted by an approved, open requisition.ReversibleYes — Discovery writes nothing to a candidate record.Depends on: buy-targeting
- Draft the outreach campaignRecruiting · campaignsL2
One message, written from the requisition and the workstream — what the work is, what the band is, and who to talk to. The draft goes to the recruiter, not to candidates.
Data accessed- Position 2291REQ-2291
Policy checkNothing leaves the company until a recruiter authorizes the campaign.Permission checkCampaign drafting delegated by the plan approval.ReversibleYes — An unsent draft has no external effect.Depends on: buy-discover
- Recruiter authorizes the campaignHuman decisionL2
The criteria and the message both need a recruiter’s name on them before anyone outside the company hears from Northstar.
Data accessed- Campaign CMP-118CMP-118 · draft
Policy checkRecruiting policy §2.6 — external outreach requires named recruiter authorization.Permission checkCurrent cannot authorize outreach on a recruiter’s behalf.ReversibleYes — Nothing has been sent.Depends on: buy-campaign-draft
- Send outreachRecruiting · outreachL3
Sent the authorized message to the five eligible profiles, each from Janine’s address with a one-click opt out.
Data accessed- Campaign CMP-118CMP-118 · authorized
Policy checkSent only to profiles the authorized criteria cover. Opt-out honored immediately.Permission checkSend authority delegated by the recruiter’s campaign authorization.ReversibleNo — A sent message cannot be unsent. Follow-ups can be stopped.Depends on: buy-campaign-auth
- Triage repliesRecruiting · reply triageL3
Three replies. One interested, one asking a question the campaign is authorized to answer, one carrying a judgment call Current will not make.
Data accessed- Campaign repliesCMP-118 · inbox
Policy checkTriage classifies logistics only. No reply is used to advance, rank or reject anyone.Permission checkReply handling delegated within the authorized campaign scope.ReversibleYes — Classifications are editable and every reply stays in full.Depends on: buy-outreach
- Schedule the recruiter screenRecruiting · schedulingL3
Sent a self-scheduling link to the interested candidate and put the conversation on Janine’s calendar. Current stops here: everything past this point is an employment decision.
Data accessed- Calendar — Janine OkaforCAL-6602
Policy checkScheduling is logistics. Current does not advance, screen out or evaluate a candidate.Permission checkCalendar write granted by the recruiting owner.ReversibleYes — A scheduled conversation can be moved or cancelled.Depends on: buy-triage
- Draft the statement of workProcurement · contingent requestsL2
A bounded package covering schema translation and backfill validation: 12 weeks, fixed scope, two-week termination clause, vendor-managed supervision.
Data accessed- Migration workstream scopePLAN-FY26-Q4 · ws-3
- MSA vendor registerVEND-0031, VEND-0044
Policy checkDraft only. Nothing is sent to a vendor at this stage.Permission checkContingent request drafting delegated by the plan approval.ReversibleYes — Discarding an unsent request has no external effect.Depends on: plan-permissions
- Run the worker-classification screenLegal · classification screenL1
Checked the drafted scope for co-employment triggers: deliverable-based package, vendor-managed supervision, no performance management by Northstar, defined end date.
Data accessed- Legal policy §11POL-LEGAL-11
Policy checkLegal policy §11 — no co-employment triggers found in the drafted scope.Permission checkPolicy read. No legal advice is generated or relied on.ReversibleYes — A screen result, not a filing.Depends on: borrow-sow
- Route contingent spend to FinanceApprovals · routingL2
Contract value exceeds the $100K threshold. Current assembled the packet — scope, cost band, classification screen and the alternatives that were rejected — and stopped.
Data accessed- R&D contingent budgetCC-R&D-01 · FY26
- Procurement policy §4.3POL-PROC-43
Policy checkProcurement policy §4.3 requires named Finance approval above $100K.Permission checkCurrent cannot approve spend on behalf of Finance under any delegation.ReversibleYes — The request can be withdrawn before Finance acts.Depends on: borrow-classification
- Submit the vendor requestProcurement · vendor requestsL3
Sent the approved package to both MSA vendors with the bounded scope and the two-week termination clause intact.
Data accessed- MSA vendor registerVEND-0031, VEND-0044
Policy checkSent only after named Finance approval, at the approved value.Permission checkSend authority delegated by the Finance approval.ReversibleWith cost — Withdrawing after submission is possible but costs vendor goodwill.Depends on: borrow-finance
- Prepare contractor onboardingIT · access provisioningL2
Staged the access package, scoped repository permissions to the migration workstream, and prepared the handoff brief from the departing engineer’s runbooks.
Data accessed- Access template — contingent engineerIAM-TPL-09
Policy checkLeast-privilege template. Access activates on the confirmed start date.Permission checkProvisioning staged, not granted, until a person is named.ReversibleYes — Staged access grants nothing until activated.Depends on: borrow-vendor-request