Skip to contentSkip to contact
Dennis KhorNeo
Recruiter mode

Green code rain falls; drops that cross the word Neo slow down and lock until the word is written in code, then the code falls out as rain and leaves the word as dark letters. The rain stops on their tops and runs off their edges, and none falls through them.

From a Slack FAQ bot to part of how the software ships.

Aug 2025 to now. An internal tool at a non-profit.

How it got here

How it got here

to now

  • Proposed growing it from an early prototype, then built most of it.
  • A platform engineer built the AWS foundation, the first release manager, the usage meter and alert summaries, and the infrastructure deploys.

to It began as a Slack FAQ bot

to It searches the live systems itself

to It explains the code in plain words

to It runs the release and watches every deploy

Now it is part of the delivery loop

A bot that answered from documents

Neo began as a Slack bot that searched fixed document sets and answered from what it found.

Staff judged every answer; it could answer, not act.

A platform engineer set up the AWS foundation it ran on.

  • Questions answered in Slack
  • Vector search over documents

to

Threads become pages and tickets

A Slack thread could now become a drafted wiki page or ticket, and nothing was filed until a person submitted it.

A person picks where it goes and submits it.

  • Thread to wiki page
  • Thread to ticket
  • Slack agent side panel

Agentic search replaces the index

Neo stopped searching a stored copy and started searching the live systems itself, with read-only tools.

People judge the answer; every claim links to where it came from.

  • Live search
  • Cited sources
  • Trails across systems

Meetings file themselves

Finished Google Meet calls get filed with nobody sorting them: a summary page and proposed follow-up tickets.

Proposed tickets wait for a person's approval in Slack.

  • Meeting summaries
  • Proposed follow-up tickets

to

Memory, GitHub and version tags

Neo moved to GitHub, learned to remember a conversation, and was rebuilt into a codebase that could keep growing.

Every change goes through a pull request a person merges.

  • Conversation memory
  • GitHub Actions
  • Version tags

The code becomes the living doc

Neo reads the apps' code on GitHub and explains it in plain words, so staff get answers that match the apps today.

Staff judge the answer, with links to the code it read.

  • Code search and file reads
  • Plain-language answers

Release notes write themselves

Every merge to main, in every repo with Neo's app installed, gets release notes written and posted for the team.

People decide what merges; the notes follow.

  • Release notes for every merge
  • Release cards
  • Automatic version tags

to

Claude on Amazon Bedrock

Neo moved onto Claude on Amazon Bedrock, and the switch could roll back with one flag.

A person flips the flag, either way.

A platform engineer made the AWS change that unblocked Bedrock.

  • Claude models
  • One-flag rollback
  • Screenshots as input
  • Model-upgrade runbook

to

Caching keeps it cheap

Neo stopped paying again for text it had already read, and every call's cost is logged against a budget.

People set the budgets.

  • Prompt caching
  • Conversation caching
  • Cost logged per call
  • Budgets that stop spend

to

Deploys run themselves

A pull request runs the tests, a merge deploys, and every deploy is pinned to its commit so it can be undone in one step.

A person merges; the deploy follows.

A platform engineer built the first version of the release manager.

  • Tests on every pull request
  • Deploys pinned to a commit
  • One-step rollback
  • A first release manager

to

A better conversation in Slack

Talking to Neo got better: it shows its plan as it works, reads whole channels, asks before it publishes, and a thumbs down points at the stale source.

People rate the answers and choose what gets published.

  • Answer ratings
  • Help-centre search
  • Channel reading
  • Live plan card
  • Message routing

to

Alarms get a verdict

When a production alarm fires, Neo reads the redacted evidence and posts likely real, likely noise or unclear in the alarm thread.

The on-call engineer decides what to do.

A platform engineer Dennis added the traffic-light verdicts on top.

  • Alarm verdicts
  • Usage meter

Weekly releases, even from a phone

Neo runs the weekly release from Slack and watches every deploy, so staging and production can go out from a phone.

A person starts each release.

Built on a platform engineer's first release manager.

  • Weekly Start or Skip gate
  • Deploy watch
  • Hotfix releases
  • One-click QA handover
  • Next week's ticket filed

Claude reviews, people merge

Ask if a pull request is ready and Claude reads it; ask Neo to watch it and it chases the next move until people approve and merge.

People approve and merge; Neo never posts on GitHub.

  • Pull request review
  • Pull request watch
  • Nudges by role
  • One-click QA handover

Support triage that reads the code

Every new support ticket is triaged, and likely bugs are investigated in the code with every citation re-checked.

An engineer reads the brief and decides the fix; nothing is said to the reporter and no ticket changes status.

  • Ticket triage
  • Code investigation
  • Citations re-checked at a pinned commit
  • A ready prompt for Claude Code

What runs on its own, and where a person decides

As of Oct 2026

Answers questions

Runs on its ownSearches the wiki, tickets, the code, the help centre and the channel live, then answers in plain words with every source linked.

A person decidesStaff judge the answer; a thumbs down names the source that was off.

Routes messages

Runs on its ownA small model call sorts each message into answer, write it up or make a ticket, and picks the model.

A person decidesA person can switch it off; it falls back to fixed rules.

Drafts tickets and pages

Runs on its ownTurns a thread into a ticket or a wiki page, drafted before the form opens.

A person decidesA person picks the board, edits and submits.

Files meetings

Runs on its ownPicks up finished Google Meet transcripts, writes a summary page and proposes follow-up tickets.

A person decidesProposed tickets wait for an approval in Slack.

Triages support tickets

Runs on its ownSorts new support tickets by type, area and urgency, flags likely duplicates and posts a card.

A person decidesPeople press Agree or Something's wrong; no ticket changes status by itself.

Investigates bugs

Runs on its ownReads the code, its history and blame, re-checks every cited line, and writes a brief with a ready prompt for Claude Code.

A person decidesAn engineer reads the brief and decides the fix.

Reviews pull requests

Runs on its ownHas Claude read a pull request for a verdict: what changed, what is worth a look and who owes what.

A person decidesPeople approve; Neo never posts on GitHub.

Watches pull requests

Runs on its ownKeeps one live status card per pull request, nudges whoever owes the next move and hands over to QA in one click.

A person decidesPeople merge, and QA tests.

Writes release notes

Runs on its ownWrites notes for every merge and release in every repo with its app installed, and posts them to a changelog channel.

A person decidesPeople decide what merges; the notes follow.

Tags versions

Runs on its ownPicks Neo's own next version from what merged and tags the release.

A person decidesA person merges; the version follows.

Runs the weekly release

Runs on its ownPosts the Start or Skip gate, dispatches the release, names one blocker at a time and files next week's ticket.

A person decidesA person starts it.

Built on a platform engineer's first release manager.

Watches every deploy

Runs on its ownFollows each staging and production deploy and reports the result in the release thread, judging the deploy job itself.

A person decidesA person starts each deploy, from a laptop or a phone.

Reads alarms

Runs on its ownReads redacted alarm evidence and posts likely real, likely noise or unclear in the alarm thread.

A person decidesThe on-call engineer decides what to do.

Endpoint built by a platform engineer; Dennis added the verdicts.

Ships features dark

Runs on its ownEvery feature runs off, then log, then on.

A person decidesTurning a feature on is Dennis's call, and one word rolls it back.

  • Next Run the replay eval
  • Next Learn from corrections
  • Next Small fix pull requests written by an agent, always reviewed by a person

The activity is illustrative; the list is real.

Not yet

  • Triage runs live from open pull requests; merging is next.
  • The replay eval is built but not run yet.
  • Questions are not logged per person, so adoption over time is not known.
  • I built most of it, which is why the docs-as-memory method matters.

Who built it

  • Proposed growing it from an early prototype, then built most of it.
  • A platform engineer built the AWS foundation, the first release manager, the usage meter and alert summaries, and the infrastructure deploys.

The role it was built in

Ask about fit

Paste a job description. You get a verdict, the evidence that matches it with citations, and what the sources do not show.

Open to senior AI and software engineering roles: on site or hybrid in Sydney, or remote for Australian and US teams.

Email meBook 15 minCV