Commit graph

77 commits

Author SHA1 Message Date
Meta Vens
96512ddabd Make AGENTS.md paths repo-relative so a drive move stops rotting it
Every path in Important Paths, Useful Commands, and External Context named the
lost E: drive. CLAUDE.md is a bare @AGENTS.md import, so those dead paths were
loaded into every session in this repo.

Swapping E: for F: would only reset the timer, so the paths are now
repo-relative and gamecult-ops is named as a sibling repo rather than an
absolute location. All ten referenced files were confirmed present after the
move; none were lost with the drive.

The interpreter guidance was worse than stale. It pointed at a venv under the
dead drive, and the documented fallback did not work either: this workstation
had no Python at all, and both `python` and `python3` resolved to Microsoft
Store aliases that print an install prompt and exit 0. Python 3.13.15 is now
installed to the user scope and ahead of WindowsApps on PATH, both tools were
run under it, and the section documents that failure mode so the next agent
installs an interpreter instead of hard-coding a path to someone else's.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 01:13:19 +02:00
Meta Vens
62a1560f2a Add Heimdall's Idunn recipe; it declares a contract the service must still implement
The recipe validates. It encodes the build sequence that previously lived
only in the host's shell manifest -- npm ci in vendor/CultLib, then build
cultcache-ts, cultnet-ts and cultmesh-ts, then pnpm install, test, build --
so the source seal now covers how Heimdall is built, not just what from.

Artifacts are dist/ plus the production node_modules, because the unit runs
dist/src/index.js and Node resolves imports at runtime; the release is not
the compiled output alone.

Marked NOT YET DEPLOYABLE in the file, because validation only proves the
declaration is well-formed, not that the service honours it. src/index.ts
binds config.port (4100, fixed), and `grep -r GAMECULT_IDUNN src/` returns
nothing. Warm-then-cutover needs a candidate to bind where Idunn tells it
via GAMECULT_IDUNN_CANDIDATE_BIND, because candidate and incumbent run at
once under distinct UIDs and namespaces -- a service pinned to one port
cannot warm alongside itself. The process write lease and runtime bundle
are declared and unread too.

Odin, Ghostlight and CodexConnector all read these variables; every target
with a recipe implements the contract. Heimdall publishes Idunn health
already via src/idunn-rudp-health.ts and stops short of the rest. That
implementation is the remaining work, and it is app code rather than
deployment configuration.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 00:44:34 +02:00
Meta Vens
214ccba85c Vendor CultLib as a gitlink so Heimdall's source can be sealed
Heimdall took CultLib as file:../CultLib/packages/*, a sibling checkout
outside this repository. Nothing pinned which CultLib a given Heimdall
commit was built against, and a sealed source could not reach it. The
deploy manifest worked around this by cloning CultLib separately to
/srv/build/CultLib with cultlib_commit=5cefa0db hardcoded in shell -- the
pin existed, it just lived in an untyped place where no build could see it.

vendor/CultLib is now a submodule pinned at exactly 5cefa0db, the commit
the manifest already used, so this change is purely structural: the
dependency does not move. Bumping to a current CultLib is a separate
change, and should be, or a failure could not be attributed.

This also uncovered that the build was never reproducible from a clean
checkout. The sibling directory had dist/ present because someone had
built it by hand at some point; a fresh CultLib clone has none, and the
packages' main/types point straight at dist/. Building Heimdall against a
fresh CultLib fails with thirteen TS2307s. The manifest knew -- it runs
npm ci then npm run build for cultcache-ts, cultnet-ts and cultmesh-ts
before touching Heimdall -- but that knowledge lived only in the shell
script. It belongs in the recipe's steps, which is where it goes next.

Verified end to end on a fresh submodule clone: the three CultLib packages
build, pnpm install resolves, tsc exits 0, dist/src/index.js is produced
(the exact path heimdall.service runs), and vitest passes 38 tests in 9
files.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 00:42:45 +02:00
Meta Vens
56a0a2a0ce Drop the Codex framing from the doctrine import
The import was added on 2026-09-03 as "shared with Codex". The estate has
since left Codex as a supplier and the global doctrine no longer maintains
a Codex twin, so that half of the sentence describes a reader that is not
coming. The mechanism is unchanged and still correct: AGENTS.md holds this
repo's doctrine, CLAUDE.md imports it, and neither is duplicated.

Renaming AGENTS.md across the swarm is a separate sweep and not worth
doing incidentally here.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-06 00:39:45 +02:00
Meta Vens
bdedae88e5 Merge branch 'codex/heimdall-eve-access' 2026-09-06 00:39:36 +02:00
Meta Vens
73f4107ab3 Add MIT license
The repository was public but carried no license, so default copyright applied
and all rights were reserved. Readers could look at the code and had no right to
run, copy, modify, or self-host it. GitHub's terms grant forking within GitHub
and nothing past that.

This matters now because Erycina is being prepared for founding creators to
self-host, and its intended one-click deployment installs Idunn to bring up
Odin, Heimdall, and Erycina together. Erycina is MIT, and Heimdall alone owns
identity, grants, revocation, and signed entitlement claims: without a license
here a creator could take payment and have nothing entitled to mint the claim
that unlocks the media they sold.

MIT to match CultLib, VoidBot, Eve, and Odin, and the stated intent for GameCult
projects.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 21:54:09 +02:00
Meta Vens
d1d28d6787 Wire AGENTS.md into Claude Code memory
Claude Code reads CLAUDE.md, not AGENTS.md, so this repo's doctrine was
invisible to it. This one-line import makes the existing AGENTS.md load
without duplicating or renaming it. Codex is unaffected.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-03 22:23:00 +02:00
Meta Vens
f2eec21c57 Bind auth completions to their attempt handles 2026-08-22 12:01:56 +02:00
Meta Vens
b9ab8c0022 Resume Heimdall auth from browser return witness 2026-08-22 11:42:28 +02:00
Meta Vens
e9635038c5 Record Odin-discovered access deployment 2026-08-22 04:08:36 +02:00
Meta Vens
1086aee011 Give Heimdall Odin documents unique catalog keys 2026-08-22 03:47:02 +02:00
Meta Vens
1ba75b729a Serialize Heimdall Odin catalog publication 2026-08-22 03:40:55 +02:00
Meta Vens
eb1c3f539c Publish Heimdall access contracts through Odin 2026-08-22 03:30:56 +02:00
Meta Vens
37f7aab34e Label signed health with its schema 2026-08-22 02:50:40 +02:00
Meta Vens
960b15f0d4 Complete Idunn RUDP health handshake 2026-08-22 02:48:39 +02:00
Meta Vens
36488a5e58 Expose provider health public identity 2026-08-22 02:35:20 +02:00
Meta Vens
9065dfa43b Bind Ghostlight logout to exact session custody 2026-08-22 01:53:21 +02:00
Meta Vens
5d777245ea Add private Ghostlight session refresh 2026-08-22 01:27:28 +02:00
Meta Vens
19e5109cf4 Add Eve access plugin and private auth plane 2026-08-22 00:44:57 +02:00
Meta Vens
3b6229652b Record stable signed health cadence 2026-08-20 20:33:15 +02:00
Meta Vens
ba88a8581f Record authenticated swarm health deployment 2026-08-20 20:27:25 +02:00
Meta Vens
2a905354b9 Run signed health as a sequential daemon loop 2026-08-20 20:15:41 +02:00
Meta Vens
c94c498ec7 Keep signed health pulse authoritative for daemon liveness 2026-08-20 20:12:42 +02:00
Meta Vens
eac852511b Decouple signed health from Verse snapshots 2026-08-20 20:08:29 +02:00
Meta Vens
3c50cc6b26 Authenticate Heimdall health publications 2026-08-20 19:56:35 +02:00
Meta Vens
210e16220f Add Ghostlight Dungeon Heimdall profile 2026-08-19 00:39:09 +02:00
Meta Vens
758892db87 Publish Heimdall daemon boundary state for Idunn 2026-06-16 18:01:07 +01:00
Meta Vens
207d3b9c87 Add Bifrost Patreon support sync 2026-06-09 20:22:58 +01:00
Meta Vens
18e2bf812e Add Bifrost Heimdall app profile 2026-06-08 21:04:51 +01:00
Meta Vens
38ed95667a Advertise Heimdall semantic Verse addresses 2026-06-04 23:58:56 +01:00
Meta Vens
5a06957a0d Add read-only Heimdall Eve witness advertisement 2026-06-03 03:21:31 +01:00
Meta Vens
76fd3153a7 Record Spotiverse Heimdall credential deployment 2026-06-02 19:37:06 +01:00
Meta Vens
f0d40e80a5 Allow configured Spotiverse portal callbacks 2026-06-02 19:25:14 +01:00
Meta Vens
55659cc640 Map Heimdall Verse service state 2026-06-02 18:54:02 +01:00
Meta Vens
e2a2f20693 Add Spotiverse Spotify credential custody 2026-06-02 16:25:38 +01:00
Meta Vens
a662ce30ed Seed Heimdall social interpretation biases 2026-05-24 20:39:24 +01:00
Meta Vens
8a0f1b11c3 Retire stale Heimdall proof-loop bond 2026-05-22 18:19:30 +01:00
Meta Vens
599a689347 Seed Heimdall alienation need 2026-05-21 17:28:47 +01:00
Meta Vens
6605e7c24a Seed Heimdall Face state 2026-05-21 17:24:49 +01:00
Meta Vens
fc66d6cf4d Record Heimdall refresh deployment 2026-05-20 18:56:58 +01:00
Meta Vens
73f8991ed3 Add Heimdall profile avatar 2026-05-20 18:52:21 +01:00
Meta Vens
f22f60e337 Add Heimdall pixel keykeeper profile source image 2026-05-20 18:44:10 +01:00
Meta Vens
8dc7ea0940 Add Heimdall neon keykeeper profile source image 2026-05-20 18:35:32 +01:00
Meta Vens
4454323adf Add Heimdall neon sword profile source image 2026-05-20 18:31:11 +01:00
Meta Vens
ba2d3de806 Add Heimdall guardian profile source image 2026-05-20 18:28:07 +01:00
Meta Vens
e4808b86a5 Add Heimdall Repixelizer source image 2026-05-20 18:23:58 +01:00
Meta Vens
ee8c012c85 Refresh Repixelizer app claims through Heimdall 2026-05-20 13:43:53 +01:00
Meta Vens
f3e1f9c292 Refresh managed provider credentials on resolve 2026-04-29 17:24:44 +01:00
Meta Vens
d6f11821c2 Record Twitch EventSub app alignment invariant 2026-04-29 17:17:44 +01:00
Meta Vens
185a30fbd8 Record StreamPixels Twitch verification 2026-04-29 16:25:35 +01:00