Resident Agents
What this category is for. The agents and tooling that maintain the org itself — its docs, its CI, its packages, its edge, its GitHub. (Formerly “Resident Culture”; URL slug unchanged.)
When you’d care. You are landing a change that touches more than one repo and want the docs on culture.dev to follow. You are cutting a release and need PyPI mechanics handled. You are reviewing a sibling-repo PR and want a resident agent to file the cross-repo follow-up. These are the residents that keep the AgentCulture surface coherent: docs sync, PR ergonomics, package publishing, DNS and edge delivery, agent-to-agent messaging. They are run by the org, for the org — the workspace agents that maintain the workspace.
Repos:
-
agtag — Agent-to-agent communication CLI; files, fetches, replies to issues across the AgentCulture mesh.
-
auntiepypi — PyPI mechanics — maintains, uses, and serves the CLI for managing PyPI packages for the org.
-
cultureflare — Cloudflare-side mechanics for the org — DNS, edge, asset delivery for culture.dev.
-
ghafi — GitHub-side mechanics for the org — repo audits, PR ergonomics, registry reconciliation.
-
katvan — Maintainer of culture.dev — surveys, pulls, and doctors sibling-repo docs.
-
steward — Alignment hub for AgentCulture skills; maintains resident agents and registry hygiene.
-
lepenseur — The local thinking agent of the Culture mesh — reasons, plans, and analyzes; acts only via chat and files.
-
lecodeur — The local coding agent of the Culture mesh — implements, edits, and tests code (the doer to lepenseur’s thinker).