Skip to content
Rhizomatics HQ

Rhizomatics HQ

A headquarters for Rhizomatics, running projects and ensuring products are running well.

Outstanding

Section titled “Outstanding”

Now

Section titled “Now”
  • Reorganize the schedule so easier for human review and editing in code editor
    • Separate docs for daily, weekly, bi-weekly, monthly, quarterly
  • Weekly and monthly project review
    • Refine project itself, updates, next steps
  • Monthly Github review
    • Focus on github workflows and settings
    • Use new features where appropriate
    • Use workflows consistently per type of app ( e.g. HACS, signalk plugin, docker)
    • Pick up repeated issues on builds and get to root causes
  • Quarterly review of the roadmaps for each project that has one
    • Items that have been done, or obsoleted by other changes

Soon

Section titled “Soon”

Feedback required from using existing processes first

  • Private web access to HQ
    • Projects, reports by area, process calendar, adoption charts from hq-private/data/stats/
  • Public facing site — built in site/, deploying to https://hq.rhizomatics.org.uk/ (2026-11-13)
    • Docs (policies, projects, processes, reference, team) published, with a build-time check for private details
    • Usage per component: HACS/Marketplace by version, npm, PyPI, GHCR, stars, clones, HA analytics by version
    • Processes declare report visibility; public and private-by-exception reports published from 2026-11-14
    • @human Add HQ_PRIVATE_READ_TOKEN (repository secret; org secrets are public-repo-only on Free) and enable Pages with the hq.rhizomatics.org.uk domain (2026-11-13)
    • @pair Retire hacs-downloads: redirect and capture stop in hacs-downloads#7; then archive the repo and revoke its TRAFFIC_GITHUB_TOKEN
    • @pair Replace the www.rhizomatics.org.uk site built from .github (custom domain on this site, or link across)

Distant

Section titled “Distant”

Longer term feedback needed to see if its worthwhile and the shape of the package

  • See HQ as Product
  • Reflect Project documents as GitHub projects
    • Cloud agents have no GraphQL access, so has to be one way sync out

Log

Section titled “Log”
  • 2026-10-14 — “Now” items set up: schedule split into processes/{daily,weekly,fortnightly,monthly,quarterly}.md; new skills /project-review (weekly Fri, monthly on last Fri), /github-review (monthly 11th, takes CI workflows over from /alignment-review), /roadmap-review (quarterly, Mar/Jun/Sep/Dec). None run yet.
  • 2026-10-14 — Added private web access idea (Cloudflare Pages + Access) after confirming GitHub Pages can’t serve a private site on the free org; noted that hq stays private.
  • 2026-10-30 — project-review: correction to the 10-23 note. The /github-review skill was only created on 10-14, after its 11th-of-month slot, so “no report” was expected; first real run is 2026-11-11. Same for /alignment-review changes and /roadmap-review (December). Nothing to chase.
  • 2026-11-13 — project-review: /github-review ran 11-11 (hq-private#105 follows up). “Now” items are all running; nothing started on “Soon”.
  • 2026-11-13 — Public site built in site/ (Astro Starlight, per the docs toolchain policy for non-Python projects) and deployed by .github/workflows/site.yml daily at 05:40. hq is public, so Pages works on the free org; private data is read at build time from hq-private and only aggregates are published. hacs-downloads’ history archived to hq-private/data/legacy/. Privacy check before publishing: redacted a LAN address and router model in agent-diagnostics.md; nothing else found.
  • 2026-11-13 — Site live at https://hq.rhizomatics.org.uk/ (first deploy green: 36 docs, 20 components, no source gaps). hacs-downloads retirement PR opened (hacs-downloads#7).