Skyphusion Labs builds free, open source software that is not for sale: Vivijure self-hosted AI film studio (v1.0), Postern agent mailbox (v1.4), Prism multimodal AI with public BYOK, Hollow Grid, security-audit, and more. Founded by Conrad Rockenhaus; one architect and five collaborators. Blog skyphusion.net, lab skyphusion.org, code github.com/skyphusion-labs.
Guidance for Claude Code (and the crew) working in this repo.
skyphusion-labs/.github, the org meta-repo. Three jobs in one repo:
SECURITY.md, CONTRIBUTING.md, and
CODE_OF_CONDUCT.md here are GitHub’s documented fallback: any repo in the org without its
own copy of one of these files inherits this one. Editing one of these three changes the
answer for every repo in skyphusion-labs that has not overridden it, not just this repo.github.skyphusion.org (CNAME), built by
.github/workflows/pages.yml from index.md (which pulls in profile/README.md, the text
GitHub also renders as the org’s profile card). This is a public page; a careless edit here
is a public change.brand/): generates and uploads GitHub social-preview images
and the X banner, and keeps repo topics / About metadata in sync with brand/topics.json /
brand/seo-metadata.json (checked by oss-discoverability-drift.yml, which fails a PR when
the live repo metadata has drifted from those catalog files)..github/dependabot.yml here is this repo’s OWN Dependabot config (github-actions + the
brand/ npm deps); it is not inherited by other repos. It documents the org-wide Dependabot
shape (see its header comment) but each repo carries its own copy.
ci check)This repo cannot emit a check named ci. No workflow here defines a job with that name. It emits coverage and CodeQL.
The org ruleset aviation-grade-main-org (18677665) requires ci, coverage and CodeQL.
So this repo sits on that ruleset’s exclusion list. Without it, every PR would wait forever for a check nothing produces.
Main is still protected. The org ruleset aviation-grade-org (24049804) applies to every repo. It blocks force pushes and requires a pull request.
Two repo-level rulesets add one approval, plus required checks CodeQL and coverage, with the branch up to date.
To re-measure, run gh api repos/skyphusion-labs/.github/rules/branches/main -q '.[]|[.ruleset_id,.type]|@tsv'. It lists what gates main. Ruleset 18677665 is absent from the output.
Tracked in .github#50. Measured 2026-10-08.
The composite action .github/actions/approval-at-head/ (action.yml + approval-at-head.py) is the
judge. The reusable workflows that other repos call pin it at a LITERAL full sha, and callers pin the
reusables by sha, so a change here changes nothing until someone re-pins. The runner downloads the action
at that sha; there is no checkout step, so a PR can never edit the script that judges it, in this repo
or any other. The gate passes only when an approval was submitted after the remote first saw the PR
head; it exists because gh pr update-branch carries an old approval forward and no GitHub ruleset flag
catches that. BOOTSTRAP ORDER: the action lands on main first; a later PR adds or re-pins the reusables
to that main sha, so a reusable on main never points at an unmerged sha. Test:
bash .github/scripts/tests/approval-at-head.test.sh (hermetic, no token), run by
approval-at-head-test.yml.
docs/claude-md-standard.md – the authoring standard every other repo’s CLAUDE.md is
written against; calibrate to the-hollow-grid/CLAUDE.md as the exemplar.brand/README.md – how to regenerate and upload social-preview / banner assets.SECURITY.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md – the org-wide fallbacks described
above.cd brand && python3 generate.py (Python, no deps beyond stdlib +
Pillow-class tooling; check generate.py itself before assuming a package).cd brand && npm install && npx
playwright install chromium && node upload-via-ui.mjs --login, then node upload-via-ui.mjs
(GitHub has no public API for repo social-preview images).brand/update-topics.sh / brand/apply-seo-metadata.sh / brand/check-catalog-coverage.sh
apply topics.json / seo-metadata.json to live repos via the GitHub API.pages.yml: push to main builds and deploys the Jekyll site; check the Pages build log and
that github.skyphusion.org actually serves the change.oss-discoverability-drift.yml: gates any PR touching brand/topics.json,
brand/seo-metadata.json, or the apply scripts against live repo state; a red run means a
catalog file and GitHub’s actual topics/About text disagree.coverage.yml is the org’s required-check placeholder (see docs/claude-md-standard.md’s
aviation-grade note); this repo has no root package.json or go.mod, so it runs the
no-manifest passthrough, not real coverage.corpus-notify.yml fires a repository_dispatch at search-mcp on merge to main so its
search corpus refreshes immediately instead of waiting for its own daily schedule; it is not
a required check and never blocks this repo’s CI.docs/claude-md-standard.mdIts “Crew + identity” required section (point 9) still describes a single conrad unix
account as “the god process” that commits as Mackaye <[email protected]>. That is stale:
there is no mackaye unix account on the current laptop-based crew seat model, each crew
member (including Mackaye) runs as its own unix account, wrapped
sudo -n -H -u <member> bash -lc. The exemplar this doc points to, the-hollow-grid/CLAUDE.md,
does not carry a “Crew + identity” section at all, which suggests current practice has already
moved to leaving that doctrine in the injected global files rather than duplicating it per
repo. Left unedited here: fixing the mechanics or dropping the section is a house-policy call
this repo’s own standard should make deliberately, not a drive-by in an unrelated sweep.