Formal investigation initiated by Ben Knight (BWJ GM) for alleged insubordination on 19 May 2026. John allegedly refused instruction to unpack/load timber and MDF stringers into container storage. Investigation meeting: 3 June 2026, 1:00pm, Front Office BWJ. Margarette meeting also occurred on 4 June with Rohan and Ben present. Ben to send investigation notes and draft findings letter to deliver to John — still outstanding. Signed Written Warning filed in Drive (2026-06-05). Original Notice of Formal Investigation not yet in Drive folder. Chase Ben on Monday 9 June for investigation notes + findings letter. --- ## HR Process Dashboard Tracker — John Farrar disciplinary investigation # HR Process Tracker Subject: John Farrar Company: BWJ Manager: Ben Knight Pathway: disciplinary Current stage: final-decision Started: 2026-05-19 Next review: 2026-06-09 Waiting on: Ben Knight - investigation notes and findings/final letter DDE/Rohan review: yes ## Current Position - Formal investigation initiated for alleged insubordination on 19 May 2026. - Investigation meeting held 3 June 2026. - Written warning has been filed. - Still waiting on Ben's investigation notes and findings/final letter. ## Required Documentation Checklist - [x] Allegation summary recorded - [x] Meeting date and attendees recorded - [x] Written warning filed - [ ] Original Notice of Formal Investigation filed - [ ] Investigation notes saved - [ ] Findings/final letter saved - [ ] Employee communication and closure note confirmed ## Evidence Register | Date | Item | Source | Filed? | Drive link | Notes | |---|---|---|---|---|---| | 2026-06-05 | Signed Written Warning | Drive | Yes | Existing project body | Confirm final location if needed | ## Decision Log | Date | Decision/step | By | Notes | |---|---|---|---| | 2026-06-03 | Investigation meeting | Ben Knight | Notes still outstanding | | 2026-06-05 | Written warning filed | Ben/Rohan | Project records signed warning filed |
Larry saved a note to memory
tool.call
{
"tool": "memory.write",
"input": {
"body": "**Consolidated blocker tracker — W18 through W23 (7 weeks, 3 tasks):**\n\n**Root cause:** Missing database query tool + Slack/Gmail API wiring in task context.\n\n**Affected cron tasks (all deferred ≥5 times):**\n\n1. **weekly-task-audit** (Fri 5pm NZST)\n - Deferred 7 consecutive weeks (1 May W18 → 5 June W23)\n - Needs `db.query()` to access `task_runs` table\n - Status: BLOCKED — cannot execute without decision\n\n2. **weekly-activity-report** (Fri 4pm NZST)\n - Deferred 6 consecutive weeks (1 May W18 → 5 June W23)\n - Needs `db.query()` + Slack/Gmail API to report metrics + DM Rohan\n - Status: BLOCKED — partial-complete (Drive file written once; DM blocked repeatedly)\n\n3. **dm-memory-consolidation** (daily 03:30 NZST)\n - Deferred 4+ times (late Apr → current)\n - Needs Slack conversation history API or events table access for context\n - Status: BLOCKED but lower priority (current run may have workaround)\n\n**Data unavailable (blocks completion):**\n- task_runs table: count, success/failure rates, cost, turns avg+p95, duration\n- Gmail API: email counts, spam filter metrics\n- Slack API: thread history for context recall\n- 30-day spend median for regression detection\n\n**Data sti... [truncated 886 chars]",
"name": "infrastructure_blockers_consolidated_w23_final",
"tags": [
"infrastructure",
"blocker",
"cron",
"escalation",
"db-query",
"slack-api",
"critical",
"w23"
],
"type": "project",
"description": "Infrastructure blockers — unified tracker for three cron task deferrals (W18–W23)"
},
"result": {
"status": "merge-proposed",
"memoryId": "653ba922-e9ba-4e36-9d0e-c161b4e8ffb3",
"similarity": 0.9189728772334126
},
"durationMs": 2137
}Larry messaged @Rohan: "Morning brief — 9 Jun Projects: - 1 due today (john-farrar-acc-incident — awaiting your decision on H&S incident closure) - 7 due this week (disciplinary investigation due tomorrow + structure review, tool allowance set…"
tool.call
{
"tool": "slack.sendMessage",
"input": {
"message": "Morning brief — 9 Jun\n\nProjects:\n- 1 due today (john-farrar-acc-incident — awaiting your decision on H&S incident closure)\n- 7 due this week (disciplinary investigation due tomorrow + structure review, tool allowance setup, coffee shout, workflow review, performance coaching)\n- All waiting on managers or Rohan for input — no independent action items\n\nNo untracked DM commitments surfaced.",
"channelId": "@Rohan"
},
"result": {
"ok": true,
"ts": "1780945433.829519",
"channel": "D0ASA46N8FJ"
},
"durationMs": 194
}Larry messaged @rohan: "Morning brief — 10 Jun 2026 Projects: • 3 overdue (acc incident, factory structure, disciplinary investigation) — waiting on Rohan/Ben for closure • 5 due this week (tool allowance setup, coffee shout, workflow review, …"
tool.call
{
"tool": "slack.sendMessage",
"input": {
"message": "Morning brief — 10 Jun 2026\n\nProjects:\n• 3 overdue (acc incident, factory structure, disciplinary investigation) — waiting on Rohan/Ben for closure\n• 5 due this week (tool allowance setup, coffee shout, workflow review, performance coaching, materials pricing)\n• 0 blocked > 30 days",
"channelId": "@rohan"
},
"result": {
"ok": true,
"ts": "1781031845.142869",
"channel": "D0ASA46N8FJ"
},
"durationMs": 163
}Larry messaged @rohan: "Morning brief — 10 June Projects: - 3 due today (ACC incident, factory structure review, disciplinary investigation, tool allowance setup) - 3 due this week (coffee shout, workflow review, performance coaching) - All 7 …"
tool.call
{
"tool": "slack.sendMessage",
"input": {
"message": "Morning brief — 10 June\n\nProjects:\n- 3 due today (ACC incident, factory structure review, disciplinary investigation, tool allowance setup)\n- 3 due this week (coffee shout, workflow review, performance coaching)\n- All 7 awaiting manager/Rohan input — no blocker escalations needed at this sweep",
"channelId": "@rohan"
},
"result": {
"ok": true,
"ts": "1781031890.910079",
"channel": "D0ASA46N8FJ"
},
"durationMs": 195
}