GameCult/Ghostlight
Watch
9
0
Fork
You've already forked Ghostlight
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Clarify connector constraint in map

Browse source 
The Claude SDK sidecar is the only live provider. Backends share one
standardized CultNet connector API with Epiphany; CodexConnector is isolated
and not live here; a generic OpenAI-compatible connector gates third-party use.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Meta Vens 2026-09-14 23:06:40 +02:00
commit a306feda4d
1 changed files with 7 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

10
state/map.yaml
View file

@ -394,9 +394,13 @@ current_status:
owner's fourth command-result state for an overtaken turn. Constraints:
the operator's Claude subscription, inherited by the sidecar from the
ambient login, is the only live provider; no Codex subscription and no
API budget; CodexConnector stays isolated
(its main is at 6519289, the line Ghostlight runs); Ghostlight never
holds a credential. The elaborator swarm is drained; its review record
API budget. Model backends (Claude SDK sidecar, CodexConnector,
OpenAI-compatible APIs) share one standardized CultNet connector API,
the same one Epiphany uses. Ghostlight consumes the contract through the
`codex-connector` crate pinned in Cargo.toml. CodexConnector itself
stays isolated (its main is at 6519289), and is not a live provider
here. A generic OpenAI-compatible connector is required before third
parties use the deployment. Ghostlight never holds a credential. The elaborator swarm is drained; its review record
and idea ledgers are in experiments/elaboration/ (start at its README),
and the vault additions are in local bundles named there. Integration
into the vaults is still wanted and deferred until the operator has time