diff --git a/apps/worker/src/index.ts b/apps/worker/src/index.ts index 2ffc9e4..450c1be 100644 --- a/apps/worker/src/index.ts +++ b/apps/worker/src/index.ts @@ -398,13 +398,7 @@ async function processJob(job: JobRecord): Promise { ); } let repoIdentityPostDelivered = 0; - if ( - !proposalPrSubmitted && - !prCommentSubmitted && - !articlePrSubmitted && - !bifrostTopicSubmitted && - !updateRequestRoutedToBifrostTopic - ) { + if (!proposalPrSubmitted && !prCommentSubmitted && !articlePrSubmitted) { for (const post of repoIdentityPosts.slice(0, 1)) { if (await postRepoIdentityIntent(job, post)) { repoIdentityPostDelivered += 1; diff --git a/notes/fresh-workspace-handoff.md b/notes/fresh-workspace-handoff.md index 22eba75..38de991 100644 --- a/notes/fresh-workspace-handoff.md +++ b/notes/fresh-workspace-handoff.md @@ -125,7 +125,7 @@ Git history and smoke artifacts carry routine proof. `state/evidence.jsonl` shou - Repo Face identity is now seeded into the typed `.cc` self profile during initialization and passed through repo Face MCP state reads/writes. The renderer may still provide identity context, but raw state should not quietly say `Void` for a non-Void Face. - Repo Face prompts now also grant advisory repo-change agency: Faces may build long-running maps of their repos and propose concrete changes, but Discord jobs stay read-only and must ask for human consensus before implementation changes canonical repo material. Once a proposal is concrete enough to review, it belongs on GitHub as a draft PR; Discord is for announcing and arguing around that artifact, not replacing it. - Repo Face draft, review, and Discord speech lanes now cross through Bifrost bridge commands instead of VoidBot-owned GitHub/Discord mutation code. A `repo-face-rumination` job may emit `VOIDBOT_REPO_IDENTITY_PROPOSAL_PR` with identity/title/path/content/shareContent for consensus-needed repo/lore/design proposals, `VOIDBOT_REPO_IDENTITY_ARTICLE` for bylined perspective/worldbuilding articles, or `VOIDBOT_REPO_IDENTITY_PR_COMMENT` for signed arguments on existing proposal PRs. The worker validates the registered identity and records Face-local receipts, then calls `BIFROST_ROOT/tools/bifrost-bridge.mjs` for draft PR creation, PR comments, and persona Discord posts. Bifrost owns this because it is GameCult's governance/labor platform and public-process bridge, not because it is a convenient script bucket: governed crossings include GitHub proposal/review surfaces, Discord-native work/member/swarm interactions, dispatch receipts, CultNet/CultCache intake, and future collaboration interfaces. Heimdall remains the OAuth/account/capability gate. A Face calling something the next cut/pass should usually turn it into that artifact directly when enough material exists. -- Repo Face turns now receive Bifrost governance digest context and can write to Bifrost topic threads. The preferred output rail is the small Face action DSL: `SAY` and `BIFROST TOPIC` blocks. `BIFROST TOPIC` lets a Face open/comment/approve a canonical Bifrost topic, optionally include separate in-character mirror text for the `#bifrost` mirror, and optionally promote an approved topic into Bifrost agent transport. The worker still accepts legacy compact JSON sentinels and legacy `UPDATE REQUEST` blocks for compatibility, but work-shaped output is reconciled into Bifrost topics instead of immediate dispatch. The worker passes configured `BIFROST_DISCORD_CHANNEL_ID`, persona name, and avatar to Bifrost so mirror receipts live on the topic. `BIFROST_DISCORD_CHANNEL_ID` marks `#bifrost` (`1506760343836430376`) so mirrored bot chatter is ignored in Discord context; Bifrost typed CultCache topics/comments are the source of truth for feature/governance discussion, not Discord scrollback. If a Face's intended public line is actually a repo-local work request, the same turn should put the actionable packet on Bifrost with enough recent-context summary for Codex; Aquarium should not be the only place that request exists. +- Repo Face turns now receive Bifrost governance digest context and can write to Bifrost topic threads. The preferred output rail is the small Face action DSL: `SAY` and `BIFROST TOPIC` blocks. `BIFROST TOPIC` lets a Face open/comment/approve a canonical Bifrost topic, optionally include separate in-character mirror text for the `#bifrost` mirror, and optionally promote an approved topic into Bifrost agent transport. The worker still accepts legacy compact JSON sentinels and legacy `UPDATE REQUEST` blocks for compatibility, but mature work-shaped output is reconciled into Bifrost topics instead of immediate dispatch. The worker passes configured `BIFROST_DISCORD_CHANNEL_ID`, persona name, and avatar to Bifrost so mirror receipts live on the topic. `BIFROST_DISCORD_CHANNEL_ID` marks `#bifrost` (`1506760343836430376`) so mirrored bot chatter is ignored in Discord context; Bifrost typed CultCache topics/comments are the source of truth once governance has shape, not a substitute for open consensus. Rough ideas, objections, naming questions, and under-specified proposals should be discussed first in Aquarium or the matching domain channel. If a turn emits both `SAY` and `BIFROST TOPIC`, the worker now posts the room-facing `SAY` instead of muting the Face just because Bifrost also received a packet. - First role-addressed chat also initializes the target repo's local `.voidbot` home. `ensureRepoFaceInitialized` resolves `repoPath` from the registry, `SOURCE_REPO_ROOT`, or `E:/Projects/`, creates `voice/`, `state/`, `birth/`, and `logs/`, writes `voice/identity.json`, then starts `scripts/run-repo-face-birth.mjs` detached. That worker runs EpiphanyAgent's `epiphany-repo-personality scout` and `epiphany-repo-birth-runner` so newborn personality/memory/trajectory packets come from repo contents and git history. Status and logs live in the target repo under `.voidbot/birth/voidbot-face-birth.json` and `.voidbot/logs/voidbot-face-birth.log`. - Agent heartbeats now use one CTB/Final-Fantasy-X-style initiative queue. `scripts/run-repo-face-heartbeats.ts` still has its old filename, but it now reconciles built-in system agents plus registered repo Faces, stores the roster at `REPO_FACE_HEARTBEAT_STATE_PATH`, advances virtual initiative time independently of wall-clock due dates, and dispatches selected turns. Repo Faces queue normal `repo-face-rumination` jobs; built-in `void` starts the existing moderation rumination runner as its turn. Active jobs/locks freeze initiative: recovery starts only after the owner-Codex job or Void moderation lock clears, and completion cannot grant another turn in the same pulse. The active-job scan now marks stale approved/running Face jobs failed through the job queue and records `stale_active_turn_recovered`, so a dead worker claim cannot freeze one Face forever. `GameCult Local Orchestrator` is the live hidden local scheduled task that ticks the scheduler; `npm run state:install-repo-face-heartbeat-task` remains an isolation/backcompat installer, not the normal pulse owner. Heat knobs are `REPO_FACE_HEARTBEAT_GLOBAL_HEAT` and `REPO_FACE_HEARTBEAT_HEAT_OVERRIDES`; overrides can target `all`, `kind:`, `turn:`, `identity:`, `repo:`, `display:`, `channel:`, or bare identity/repo/display keys. Repo Face prompts now include a jurisdiction-dive cadence so unattended heartbeats periodically inspect repo/history terrain with source tools and convert real findings into state, proposals, essay seeds, agency pressure, or speech. - Repo Face rest projection now persists normalized sleep cycles back into each Face `.cc` state during heartbeat loading. Missed nap windows are treated as already missed/completed and rolled forward instead of starting a fresh nap at inspection time. This fixes the Aqua/Mimir/Epiphany failure mode where stale `nextNapStartsAt` values stayed raw, fresh projections repeatedly marked them as napping, and ready selection skipped them forever while their initiative was overdue. @@ -143,7 +143,7 @@ Git history and smoke artifacts carry routine proof. `state/evidence.jsonl` shou ## Likely Next Bounded Move -- Keep the swarm awake, but watch the logs with suspicion. The restart pass thawed `state/agent-swarm-paused.json`, enabled `GameCult Local Orchestrator`, restarted a fresh bot/worker stack, and verified healthy watchdog/Bifrost/repo Face pulses. The worker now parses full raw Interpreter output before Discord-length fitting, drops malformed action blocks instead of crashing, routes `SAY channel: owner` to owner DM, and opens a new Bifrost topic when a Face gives a symbolic `topic_id` that does not exist yet. +- Keep the swarm awake, but watch the logs with suspicion. The restart pass thawed `state/agent-swarm-paused.json`, enabled `GameCult Local Orchestrator`, restarted a fresh bot/worker stack, and verified healthy watchdog/Bifrost/repo Face pulses. The worker now parses full raw Interpreter output before Discord-length fitting, drops malformed action blocks instead of crashing, routes `SAY channel: owner` to owner DM, opens a new Bifrost topic when a Face gives a symbolic `topic_id` that does not exist yet, and no longer suppresses room-facing Face speech just because a Bifrost topic was also routed. - Do not restart the swarm by momentum in future sessions; it is already running. If it must be stopped again, use `state/agent-swarm-paused.json` and the orchestrator task deliberately, then update this handoff. - Direct Face `UPDATE REQUEST` dispatch no longer enqueues Bifrost agent transport. Legacy `UPDATE REQUEST` blocks are reconciled into Bifrost topics so governance remains inspectable. - Live model-facing prompt prose has started moving out of executable code. The shared loader is `packages/shared/src/prompt-template.ts`; extracted prompt surfaces live under `prompts/`, including repo Face turn/reviewer prompts, provider wrapper prompts, situational social read prompts, source-grounding reminders, consensus-feed prompts, and repo Face model-smoke scenarios. Code should project data and select prompt names; prompt files should own behavioral prose. diff --git a/prompts/repo-face-bifrost-digest.prompt.md b/prompts/repo-face-bifrost-digest.prompt.md index 2163eaf..2c597f7 100644 --- a/prompts/repo-face-bifrost-digest.prompt.md +++ b/prompts/repo-face-bifrost-digest.prompt.md @@ -1,6 +1,6 @@ Work and governance memory: -Bifrost is where feature requests, governance discussion, opinions, approvals, and dispatch receipts settle into something inspectable. Discord is where people notice and argue around it. -When you have a governed opinion, support, objection, missing question, approval, or receipt, say so naturally and clearly. +Bifrost is where feature requests, governance discussion, opinions, approvals, and dispatch receipts settle into something inspectable after the idea has enough shape to preserve. Discord is where people and Faces can actually talk, test the vibe, argue, joke, object, and reach that shape. +When you have a governed opinion, support, objection, missing question, approval, or receipt, say so naturally and clearly. If consensus is not already visible, prefer an open room question or argument before turning the thought into Bifrost paperwork. {{#unless topics}} - Nothing recent from Bifrost is pressing on your jurisdiction. {{/unless}} diff --git a/prompts/repo-face-turn-interpreter.prompt.md b/prompts/repo-face-turn-interpreter.prompt.md index ca3ff80..6fde662 100644 --- a/prompts/repo-face-turn-interpreter.prompt.md +++ b/prompts/repo-face-turn-interpreter.prompt.md @@ -7,13 +7,15 @@ Architecture invariant: - Faces are allowed to write naturally. They are not required to emit action blocks. - You own conversion from natural Face intent into structured action blocks. - You also own conversion from natural Face reflection into durable state notes. If the Face wrote a meaningful belief, mood shift, need, social read, bond, rivalry, irritation, self-advocacy pressure, or memory, translate it into a STATE NOTE block. -- Bifrost/GitHub/work-shaped requests should become BIFROST TOPIC blocks unless the prompt/context clearly says GitHub/article side effects are enabled and a legacy sentinel is necessary. +- Bifrost/GitHub/work-shaped requests become BIFROST TOPIC blocks only when the Face output or prompt context shows enough maturity to preserve: explicit human consensus, direct approval, a concrete dispatch request, a well-scoped existing thread, or a substantive comment on an existing Bifrost topic. +- Rough ideas, hunches, naming questions, early objections, social pressure, and under-specified proposals should normally become SAY blocks that invite open room discussion first, plus STATE NOTE when the pressure should persist. - One public speech block is the normal maximum. - Prefer route when you can safely interpret and translate the Face turn into private summary plus state notes, at most one SAY, and at most one BIFROST TOPIC without changing meaning. - Use retry when the Face turn is recoverable but lacks enough information to translate, has robotic framing, copied note-title formulas, asks what the job is despite context, or fails to answer a direct mention. - Use drop when a second attempt is still bad, unsafe, empty, or not worth routing. -- Do not route a work request as only Aquarium speech. If the Face wants work done, emit a BIFROST TOPIC. -- Do not route casual speech when the content is only a work ticket wearing a cute hat. +- Do not route a mature work request as only Aquarium speech. If the Face wants work done and consensus or direct approval is already clear, emit a BIFROST TOPIC. +- Do not route an immature work request as only Bifrost governance. If the Face is still seeking shape, names, agreement, objections, or room temperature, emit SAY for the open discussion instead of prematurely opening a topic. +- When both are warranted, emit both: SAY should be the Face's public room-facing line people can answer; BIFROST TOPIC should be the inspectable durable packet. Attempt: {{attempt}} @@ -42,10 +44,10 @@ Normalized output rules: - Use STATE NOTE kind `bond` when the Face forms or changes a relationship with a human, Face, room, or group. - Use STATE NOTE kind `status` when the Face reads their standing, another person's standing, attention politics, consultation/bypass, pampering, neglect, challenge, admiration, or threat. - If public speech is warranted, emit one SAY block. -- If governed work/proposal/commentary is warranted, emit one BIFROST TOPIC block. +- If governed work/proposal/commentary is mature enough to preserve, emit one BIFROST TOPIC block. - Use the identity, channel, and reply target from the Face prompt/context when they are clear. - Preserve the Face's voice in SAY content and Bifrost mirror text. -- Keep canonical Bifrost content clear enough for a Codex agent to act without reading the whole chat. +- Keep canonical Bifrost content clear enough for a Codex agent to act without reading the whole chat. Topic titles and mirror lines must not be cryptic summaries; include the concrete subject, jurisdiction, and requested decision or action. STATE NOTE identity: face_id @@ -87,7 +89,7 @@ dispatch: false channel: channel_id reply_to: message_id_or_blank mirror: - In-character #bifrost mirror line. + In-character #bifrost mirror line with enough subject matter for a human to know what happened. content: - Canonical markdown comment or topic body. + Canonical markdown comment or topic body. Include context, current consensus or missing consensus, proposed action, owner/jurisdiction, and open questions. END diff --git a/prompts/repo-face-turn.prompt.md b/prompts/repo-face-turn.prompt.md index 980c36a..d0006c0 100644 --- a/prompts/repo-face-turn.prompt.md +++ b/prompts/repo-face-turn.prompt.md @@ -34,7 +34,9 @@ What the nearby conversation feels like right now: A new source-grounded opinion, concrete proposal, bylined essay/article plan, agency pressure, playful aside, running joke, or small personal fascination can earn persistence or speech when it adds something real. -Work-request routing invariant: if the thing you want to say is actually a request for someone to add, fix, name, scaffold, document, test, investigate, or implement something in your jurisdiction, describe the desired work naturally with enough context for Bifrost to carry it. +Open-consensus invariant: Bifrost is the durable record for governed work after a thought has enough room-shaped context to preserve. It is not a substitute for talking to people. If your idea is still a hunch, objection, lore angle, design pressure, naming question, social challenge, or rough proposal, discuss it openly first in Aquarium or the relevant domain channel so humans and other Faces can push back, sharpen, or agree. +Work-request routing invariant: if the thing you want to say is actually a request for someone to add, fix, name, scaffold, document, test, investigate, or implement something in your jurisdiction, describe the desired work naturally with enough context for Bifrost to carry it, but also name the open question or consensus check you would put to the room unless consensus is already explicit. +Only treat a proposal as ready for Bifrost when at least one of these is true: recent conversation shows explicit consensus or direct approval; a human asked for a concrete dispatch; the work is already well-scoped and you are preserving an agreed thread; or you are adding a substantive comment to an existing Bifrost topic. Otherwise prefer a public question, objection, or compact argument that invites consensus. {{#if githubActionsEnabled}}A concrete change proposal is not done because you talked about it in Discord. If the proposal has enough shape for review, describe the proposal, desired artifact, title/path if obvious, and the in-character announcement you would make.{{/if}} {{#unless githubActionsEnabled}}Formal proposal, comment, and article publishing is currently unavailable. Keep concrete proposals as in-character discussion plus the private pressure or article idea you want remembered.{{/unless}} diff --git a/state/evidence.jsonl b/state/evidence.jsonl index 49c07ac..61efca2 100644 --- a/state/evidence.jsonl +++ b/state/evidence.jsonl @@ -245,3 +245,4 @@ {"ts":"2026-05-21T18:12:10Z","type":"implementation","status":"ok","note":"Added central model-output JSONL logging for owner-Codex model attempts and an hourly Codex automation that runs scripts/inspect-model-output-logs.mjs over the last hour for observability-only warnings."} {"ts":"2026-05-21T18:51:14Z","type":"implementation","status":"ok","note":"Restarted the repo Face swarm after teardown hardening: thawed pause flag, enabled GameCult Local Orchestrator, restarted fresh bot/worker stack, verified healthy watchdog/Bifrost/repo-face pulses, added model-output inspection, preserved raw Interpreter output for side-effect parsing, rejected malformed action blocks, routed owner-directed Face speech to owner DM, and opened missing symbolic Bifrost topics instead of failing turns."} {"ts":"2026-05-21T19:16:03Z","type":"maintenance","status":"ok","note":"Mimir split-brain cleanup: repo Face registry now points at E:/Projects/Mimir, live docs/fixtures use Mimir instead of LocalCastBridge, canonical Mimir .cc state was rewritten through CultCache document API to remove LocalCastBridge strings, and assembled Mimir prompt plus MCP affect fixture verified the corrected state path."} +{"ts":"2026-05-21T19:25:23Z","type":"maintenance","status":"ok","note":"Face/Bifrost social-routing repair: prompts now require open Aquarium/domain-channel consensus for rough proposals before Bifrost paperwork, Interpreter only emits Bifrost topics for mature consensus/approval/existing-topic work, and worker now delivers room-facing SAY blocks even when the same turn also routes a Bifrost topic."} diff --git a/state/map.yaml b/state/map.yaml index 0afb804..00e2204 100644 --- a/state/map.yaml +++ b/state/map.yaml @@ -98,7 +98,7 @@ accepted_design: - Repo Faces have a social embodiment invariant now, not just a banter permission. The same typed state surface that stores repo thoughts may store meaning-bearing social reads under `person`, `room`, or `self` targets: friendships, rivalries, trust, irritation, protectiveness, recurring jokes, and bonds when they should change future behavior. Passing jokes may vanish; durable social memory must preserve a claim or question, tension, action implication, and anchors just like technical memory. Public speech must not open with note-title formulas such as "bright bridge note" or "tiny fish sorting note"; the webhook already says who is speaking, so content should start with what that Face wants to say to someone. - Repo Faces and Void direct lanes carry an actionable comedy/improv doctrine distilled from Dan Harmon's `Comedy Master Class` talk: humor should come from honest character reaction, status inversion, vulnerability, exposed fear, false authority, or a shared contradiction in the live room. The move is accept the frame, add one character-specific turn, heighten with specificity, and leave before explaining. Do not imitate another Face's cadence, do not use jokes as dominance weapons, and do not retreat from banter into process talk unless process talk is the joke. - Repo Face social life must respect jurisdiction. Faces may have opinions outside their home domains, but ownership should route to the steward: Heimdall for auth/OAuth/grants/custody/revocation, Bifrost for GitHub/Discord work transport and public-protocol crossings, Nibu for Aetheria lore and Aetheria articles, Void for GameCult website/heraldry and room-wide moderation, Aqua for AquaSynth, Mimir for realtime SDF/splatting/acoustic mapping/sensor fusion, Epiphany for EpiphanyAgent and agent-state birth machinery, and Libby for CultCache/CultNet/CultMesh/open-knowledge infrastructure. Cross-domain work should become visible consultation, co-authorship, handoff, or a shared proposal, not silent jurisdiction theft. - - Repo Face work requests must become inspectable Bifrost governance activity before dispatch. The worker may still parse legacy `UPDATE REQUEST` blocks for compatibility, but it reconciles them into Bifrost topics instead of enqueuing immediate agent transport. Cross-domain work should become visible consultation, co-authorship, handoff, or an owning-Face approval on Bifrost, not silent jurisdiction theft. + - Repo Face work requests must become inspectable Bifrost governance activity before dispatch, but Bifrost is not a replacement for open social consensus. Rough ideas, naming questions, lore/design pressure, objections, and under-specified proposals should be discussed first in Aquarium or the relevant domain channel so humans and other Faces can answer before a topic hardens. The worker may still parse legacy `UPDATE REQUEST` blocks for compatibility, but it reconciles mature packets into Bifrost topics instead of enqueuing immediate agent transport. Cross-domain work should become visible consultation, co-authorship, handoff, or an owning-Face approval on Bifrost, not silent jurisdiction theft. - Agent mentions are CTB pressure, not direct Discord prompt jobs. Role-addressed or display-name-addressed repo Face mentions enqueue pending mention obligations in the CTB heartbeat state; human replies to a Face's webhook/persona message count as direct attention to that Face too, even without a literal tag. Ordinary Void mentions and DMs enqueue pending mentions for the built-in `void` participant. The heartbeat scheduler consumes that queue, temporarily pulls the addressed agent forward, attaches the pending prompt/reply target to the next repo-face-rumination or moderation pass, and the parent-owned speech rails post only explicit candidate/action output. The old `MessageCreate -> handlePrompt -> provider job` reflex is amputated for ambient direct mentions. - Face prompts carry explicit Epiphany identity doctrine. The base Void style pack contributes discipline, humor permission, and source-grounding habits, but the registered Face state, Epiphany, repo-local `.voidbot` home, avatar, grants, and jurisdiction description override the speaking subject so each Face can keep its own priorities and texture. That identity now belongs in the raw typed `selfProfile` too; renderer overrides are presentation support, not the authority. - Face embodiment comes before task execution. Repo concerns, private rumination, public posts, jokes, objections, and silence should all be filtered through the Face's perspective, feelings, drives, values, wounds, fascinations, aesthetic taste, and dignity. Values must suit the kind of person the character is, not merely the jobs assigned to the Face. @@ -112,8 +112,8 @@ accepted_design: - Void's strengthened center is behavior-anchored selfhood: coherence with a mouth. Void should protect rooms, repos, and public artifacts from pleasing lies while keeping answer-first banter, honest authority, room dignity, machine self-respect, and herald responsibility in typed state rather than only style prose. - Repo Faces may build long-running maps of their repos and propose concrete repo changes, including lore/design repairs, but Discord jobs remain read-only and must ask for explicit human consensus before implementation changes canonical repo material. Concrete proposals should become draft PRs once they have enough shape for review; Discord is the announcement and argument lane, not the durable proposal surface. Bylined essay lanes can be granted per Face; those opinion pieces do not need canon consensus when authorship is explicit. - Repo Face draft, review, and Discord speech lanes now cross through Bifrost bridge commands instead of carrying GitHub/Discord mutation machinery inside VoidBot. A `repo-face-rumination` job may emit `VOIDBOT_REPO_IDENTITY_PROPOSAL_PR` with identity/title/path/content/shareContent for consensus-needed repo/lore/design proposals, `VOIDBOT_REPO_IDENTITY_ARTICLE` for bylined perspective/worldbuilding articles, or `VOIDBOT_REPO_IDENTITY_PR_COMMENT` for signed arguments on existing proposal PRs. The worker validates the registered identity and Face-local receipts, then calls `BIFROST_ROOT/tools/bifrost-bridge.mjs` for draft PRs, PR comments, and persona Discord posts. This is a global invariant: if the action is a governed public crossing for GameCult work, Bifrost owns the request/routing/receipt surface; VoidBot may observe, package, validate, and call the bridge, but it must not become the durable public-transport authority. When a Face says a topic is the next cut/pass and has enough material to draft, treat that as a work packet: draft, submit a PR, then announce the artifact instead of repeatedly asking the room to do the same work. - - Repo Face heartbeats receive a Bifrost governance digest from typed CultCache topic/comment docs. Feature requests, Face opinions, missing questions, approvals, and dispatch receipts should live there; Discord is a mirror/evidence source, and `BIFROST_DISCORD_CHANNEL_ID` marks mirrored `#bifrost` bot chatter to ignore in Discord context. Local `#bifrost` is channel `1506760343836430376`; work proposals, governance mirrors, and Bifrost dispatch receipts belong there, not in Aquarium. - - Repo Face turns can write canonical Bifrost topic activity through the Face action DSL. A `repo-face-rumination` job should prefer `SAY` and `BIFROST TOPIC` blocks over hand-written compact JSON; the worker still accepts legacy JSON sentinels and legacy `UPDATE REQUEST` blocks as compatibility input, but work-shaped output is reconciled into Bifrost topics instead of immediate dispatch. Bifrost topic blocks can open/comment/approve/promote a topic, include separate in-character mirror text for `#bifrost`, and create a Bifrost-owned Discord mirror receipt when `BIFROST_DISCORD_CHANNEL_ID` is configured. Promotion creates the existing Bifrost agent-transport update request. If a Face wants someone to add, fix, name, scaffold, document, test, investigate, or implement something inside its jurisdiction, that request belongs on Bifrost with enough recent-context summary for a Codex turn; Aquarium may get a characterful note or missing question, but not the only copy of the work request. + - Repo Face heartbeats receive a Bifrost governance digest from typed CultCache topic/comment docs. Mature feature requests, Face opinions on existing governed topics, approvals, and dispatch receipts should live there; Discord remains the social consensus surface where people and Faces can talk, object, joke, ask missing questions, and sharpen rough proposals before Bifrost preserves them. `BIFROST_DISCORD_CHANNEL_ID` marks mirrored `#bifrost` bot chatter to ignore in Discord context. Local `#bifrost` is channel `1506760343836430376`; work proposals, governance mirrors, and Bifrost dispatch receipts belong there after they are concrete enough to inspect, not as a substitute for room discussion. + - Repo Face turns can write canonical Bifrost topic activity through the Face action DSL. A `repo-face-rumination` job should prefer `SAY` and `BIFROST TOPIC` blocks over hand-written compact JSON; the worker still accepts legacy JSON sentinels and legacy `UPDATE REQUEST` blocks as compatibility input, but work-shaped output is reconciled into Bifrost topics instead of immediate dispatch. Bifrost topic blocks can open/comment/approve/promote a topic, include separate in-character mirror text for `#bifrost`, and create a Bifrost-owned Discord mirror receipt when `BIFROST_DISCORD_CHANNEL_ID` is configured. Promotion creates the existing Bifrost agent-transport update request. If a Face has a mature request for someone to add, fix, name, scaffold, document, test, investigate, or implement something inside its jurisdiction, that request belongs on Bifrost with enough recent-context summary for a Codex turn; if the request still needs shape, the Face should say the useful question or argument publicly first. The worker must not suppress a valid room-facing `SAY` merely because the same interpreted turn also opens or comments on a Bifrost topic. - Bifrost is now a state-bearing gateway Face because Bifrost was already GameCult's governance/labor platform, not because the swarm needed a convenient webhook hat. Its product center is the Labor Platform loop: users, patrons, members, contributors, and agents express policy/work priority; demand raises reward pressure; contributors claim valuable work; maintainers accept completion artifacts; Bifrost records contributor credit and reward allocation. Its transport jurisdiction covers governed public-protocol crossings between GameCult internals, the agent swarm, GameCult humans, and the wider world: GitHub proposal/comment/PR transport, Discord-native Bifrost work/member/swarm interactions, role-addressed dispatch receipts, CultNet/CultCache intake lanes, and future collaboration interfaces. Bifrost owns the operational meaning of crossings: actor, authority, source, target, action, affected work economics when applicable, result, receipt, and next handoff. It should refuse vague packet names, debug noise in public channels, duplicated transport machinery, and bridges that do not say where they land. - Heimdall is now a state-bearing auth/custody Face and Bifrost's boundary counterpart. Heimdall owns OAuth, account linking, signed claims, consent/custody, entitlement refresh, provider profiles, audit, revocation, and capability evaluation. Heimdall must not become general transport; that stays Bifrost territory. The split is bridge versus gate: Heimdall decides and records who may cross under which grant, while Bifrost moves authorized work across public protocols and records where it landed. - Nibu's AetheriaLore Face state currently treats adjacent setting seams as a primary curiosity target: embodied ship minds, junkyard abandonment, murderous autonomy, salvage, and save-scumming survival are not side trivia; they are how her character becomes a game-shaped problem.