Use CultLib CultMeshTS runtime path
This commit is contained in:
parent
e3250aa30c
commit
3da7440387
5 changed files with 10 additions and 6 deletions
|
|
@ -2782,7 +2782,6 @@ function operatorDmStorePath(): string {
|
|||
function loadCultMeshRuntime(): { CultMesh: any; defineDocumentType: any } | null {
|
||||
const candidates = [
|
||||
resolve(process.cwd(), "..", "CultLib", "packages", "cultmesh-ts", "package.json"),
|
||||
resolve(process.cwd(), "..", "CultMeshTS", "package.json"),
|
||||
];
|
||||
|
||||
for (const packageJson of candidates) {
|
||||
|
|
|
|||
|
|
@ -139,7 +139,7 @@ export function registerVoidbotTools(
|
|||
{
|
||||
title: "List Odin Providers",
|
||||
description:
|
||||
"Compatibility relay: list Eve/CultUI providers currently advertised through Odin's transitional HTTP surface. Native GameCult agents should prefer CultNet/CultMesh Verse discovery when available.",
|
||||
"Compatibility relay: list Eve/CultUI providers currently advertised through Odin's transitional HTTP surface. Native GameCult agents use CultNet/CultMesh Verse discovery through CultLib's cultmesh-ts runtime.",
|
||||
inputSchema: odinEndpointInputSchema,
|
||||
annotations: READ_ONLY_ANNOTATIONS,
|
||||
},
|
||||
|
|
|
|||
|
|
@ -11,8 +11,9 @@ VoidBot surfaces as they become first-class Verse nodes.
|
|||
Native swarm communication is CultNet over CultMesh. HTTP endpoints,
|
||||
WebSocket decks, and MCP tools are lowerings or bridges, not the native
|
||||
substrate for GameCult agents. A Persona's first discovery sense is the
|
||||
CultMesh Verse map; Odin's HTTP/WebSocket surfaces are transitional inspection
|
||||
lowerings until native CultMesh client access exists in the runtime.
|
||||
CultMesh Verse map through the TypeScript runtime at
|
||||
`E:\Projects\CultLib\packages\cultmesh-ts`; Odin's HTTP/WebSocket surfaces are
|
||||
transitional inspection lowerings, not the native client path.
|
||||
|
||||
## Owner Map
|
||||
|
||||
|
|
@ -75,6 +76,11 @@ order evidence. When a native CultMesh client is unavailable, the prompt and
|
|||
operator surfaces must say so explicitly and treat Odin HTTP/WebSocket reads as
|
||||
compatibility inspection, not native wiring.
|
||||
|
||||
The native TypeScript runtime location is singular:
|
||||
`E:\Projects\CultLib\packages\cultmesh-ts`. A missing or unbuilt package there
|
||||
is an urgent CultLib/runtime bug. VoidBot must not fall back to a sibling
|
||||
`CultMeshTS` repository or grow its own private CultMesh implementation.
|
||||
|
||||
Required native surfaces:
|
||||
|
||||
- `voidbot.archive`: typed CultCache/CultMesh documents and commands for
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
Research and memory access:
|
||||
- Verse discovery through native CultNet/CultMesh is your first substrate sense. Reach for the live Verse map before treating MCP retrieval, old registry state, HTTP/WebSocket lowerings, or transcript memory as the shape of reality.
|
||||
- Your complete allowed tool set for this compatibility Face turn is: `list_odin_providers`, `list_odin_verses`, `get_odin_surface`, `load_odin_interface_context`, `invoke_odin_interface_command`, `search_history`, `get_message_context`, `list_indexed_repos`, `search_sources`, `get_source_context`.
|
||||
- The current Odin tools are MCP compatibility relays over Odin's transitional HTTP/WebSocket lowerings. Use them only as a temporary way to inspect what native CultMesh/CultNet discovery must expose directly.
|
||||
- The current Odin tools are MCP compatibility relays over Odin's transitional HTTP/WebSocket lowerings. Use them only as a temporary way to inspect what the native CultMesh/CultNet runtime at `E:\Projects\CultLib\packages\cultmesh-ts` must expose directly.
|
||||
- Use Odin tools for read-only live Verse/interface access: what Odin can currently see, which provider-owned surfaces are present, what the all-seer surface reports, and the compact TUI/action context for a specific provider.
|
||||
- Treat Odin as the all-seer for the early connected Colossus: use Verse discovery whenever the live shape of the mesh could change your thought, proposal, memory, or action. A Verse is a provider-owned surface becoming legible to other minds, not a generic status blob.
|
||||
- Use `load_odin_interface_context` before trying to operate a service. It lowers the provider-owned CultMesh/Eve surface into compact text, tree, and advertised commands so you do not spend the turn swallowing a whole dashboard raw.
|
||||
|
|
|
|||
|
|
@ -793,7 +793,6 @@ async function writeCultMeshPublication(snapshot, eveState, storePath) {
|
|||
function loadCultPackages() {
|
||||
const candidates = [
|
||||
resolve(repoRoot, "..", "CultLib", "packages", "cultmesh-ts", "package.json"),
|
||||
resolve(repoRoot, "..", "CultMeshTS", "package.json"),
|
||||
];
|
||||
for (const packageJson of candidates) {
|
||||
if (!existsSync(packageJson)) {
|
||||
|
|
|
|||
Loading…
Reference in a new issue