Add mitchella to the fleet - #174
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
cpitzi
enabled auto-merge (squash)
August 28, 2026 03:40
Contributor
terraform plan (success) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
mitchellato the fleet: a corpus-backed front desk for an infrastructureestate. It answers operator questions from curated markdown documentation,
checks live state before it answers, and drafts a ticket for a human when it
cannot answer. Slack is the first frontend; a CLI ships alongside it so the
UI-agnostic boundary has more than one implementation behind it.
Since repo existence is Terraform-managed here, this is the change that creates
the repository:
fleet-ops/repos.json— the repo entry.template_sourceisnullrather than
repo-template, because the working tree already exists locallyand will be pushed; scaffolding from the template would create a conflicting
initial commit.
fleet-ops/required-checks.json—docs-check / docs-checkplustests / pytest. The test suite runs against a fake API client and makes nonetwork calls, so it needs no secret and costs nothing to gate on. Neither
workflow is path-filtered, so both report on every pull request.
brand/fleet.jsonand the regeneratedbrand/generated/mitchella/—banner, badges, and README header. It reuses the
lentagomark, as everyrepo since
betulahas.Topics are
chatops,service-desk,slack,incident-response, andretrieval, unioned with the fleet spine.ci/validate.pypasses. It caught a bespokemitchellamark that had nocorresponding SVG on the first attempt, which is the check doing its job.
The repository contents are pushed separately once this merges and the apply
creates the remote.