diff --git a/.github/workflows/actions.lock b/.github/workflows/actions.lock
index 6d8ead9..0f99644 100644
--- a/.github/workflows/actions.lock
+++ b/.github/workflows/actions.lock
@@ -119,7 +119,7 @@ dependencies:
         repo_id: 1275649586
     'hyperpolymath/cicd-suite@main':
         ref: 'main'
-        commit: 'sha1-b25f613c860823372a7ff2cb75c23f3606bee81f'
+        commit: 'sha1-5a10b72e574ef63855fafd4568a4c178657f3294'
         owner_id: 6759885
         repo_id: 1326697643
         uses:
diff --git a/MAINTAINERS b/MAINTAINERS
index 37f6411..7d7a0cc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1,43 +1,15 @@
-# Maintainers
-
-This file lists the current maintainers of this project.
-
-## Active Maintainers
-
-| Name | GitHub | Role | Since |
-|------|--------|------|-------|
-| Metadatastician | @metadatastician | Primary | Project Start |
-
-## Emeritus Maintainers
-
-None at this time.
-
-## Becoming a Maintainer
-
-To become a maintainer:
-
-1. Demonstrate consistent, high-quality contributions
-2. Show understanding of the project's goals and architecture
-3. Be active in code reviews and community discussions
-4. Be nominated by an existing maintainer
-5. Be approved by consensus of existing maintainers
-
-## Maintainer Responsibilities
-
-- Reviewing and merging pull requests
-- Managing releases
-- Triaging issues
-- Enforcing code standards
-- Mentoring new contributors
-- Participating in decision-making
-
-## Maintainer Expectations
-
-- Respond to issues and PRs in a timely manner
-- Follow the code of conduct
-- Be transparent in decision-making
-- Communicate clearly and respectfully
-
----
-
-*Last updated: 2026-07-18*
+= MAINTAINERS
+
+Owner and maintainer of januskey
+--------------------------------------------------
+
+* Jonathan D.A. Jewell (@hyperpolymath) — repository owner and lead maintainer.
+* Every change to this repository is reviewed and merged by @hyperpolymath,
+  including dependency bumps and CI workflow edits.
+* Direct pushes to the default branch are limited to the owner; all other
+  changes arrive through pull requests and land via squash merge.
+* Security-relevant reports go to the owner account above rather than a
+  public issue.
+* This repository is part of the hyperpolymath estate and follows the
+  estate-wide governance, document-format and CI conventions enforced by
+  hyperpolymath/cicd-suite (the Central Estate CI/CD Audit).