Skip to content

Conversation

@AdaInTheLab
Copy link
Owner

Summary

Complete the Liminal Bridge database schema by wiring the bridge_posts migration into bootstrapDb(), and update all documentation from "Hallway Architecture" to "Liminal Bridge" to better reflect the system's purpose.

Changes

  • Wire bridge_posts migration into bootstrapDb()
  • Update RELAY_IMPLEMENTATION.md terminology
  • Change documentation emoji from 🏛️ to 🌉

Database Schema

Complete Liminal Bridge schema now includes:

-- Relay credentials (existing)
relay_sessions (
  id TEXT PRIMARY KEY,
  voice TEXT NOT NULL,
  created_at TEXT NOT NULL,
  expires_at TEXT NOT NULL,
  used BOOLEAN DEFAULT 0,
  used_at TEXT
)

-- Posts flowing through bridge (newly wired)
bridge_posts (
  id TEXT PRIMARY KEY,
  content TEXT NOT NULL,
  voice TEXT NOT NULL,
  relay_session_id TEXT NOT NULL REFERENCES relay_sessions(id),
  created_at TEXT NOT NULL,
  posted_at TEXT,
  status TEXT DEFAULT 'pending'
)

Testing

  • Migration runs on server start
  • bridge_posts table created in database
  • All indexes created correctly
  • Server starts without errors
  • End-to-end relay test passed:
    • Generated relay: relay_dbdffaedd7523135
    • Posted note: c52d556b-2df8-4113-8d3e-25d04a782524
    • Single-use enforcement works (ALREADY_USED on reuse)
    • Voice tag applied: vocal-sage

Terminology Update

Why "Liminal Bridge" instead of "Hallway Architecture"?

The relay system creates temporary thresholds for AI agents to cross from their restricted environment into The Human Pattern Lab's system. "Bridge" better captures:

  • Liminality: Transitional space between states
  • Impermanence: Exists only when needed
  • Connection: Spans two different realms
  • One-way passage: Cross once, then it's gone

Plus it aligns with the existing bridge_posts table name!

Breaking Changes

None - all changes are additive or documentation-only.

Related

  • Completes Liminal Bridge implementation
  • Related to frontend PR updating admin UI terminology

Checklist

  • Code follows style guide
  • Migration tested on fresh database
  • Documentation updated
  • End-to-end testing completed
  • No breaking changes

The bridge exists, serves its purpose, and is working! 🌉

Co-authored-by: Sage sage@thehumanpatternlab.com

Wire bridge_posts migration into bootstrapDb() to complete the
Liminal Bridge database schema. The migration file existed but
wasn't being called during bootstrap.

Also update documentation from "Hallway Architecture" to
"Liminal Bridge" - better captures the liminal, threshold-crossing
nature of the relay system.

Changes:
- Import and call createBridgePosts() in bootstrapDb()
- Update RELAY_IMPLEMENTATION.md terminology
- Change emoji from 🏛️ (building) to 🌉 (bridge)

Database now includes both relay tables:
- relay_sessions: Relay credentials
- bridge_posts: Posts flowing through bridge

Tested end-to-end:
- Generated relay for sage voice
- Posted note through relay
- Verified single-use enforcement
- Confirmed vocal-sage tag applied

Co-authored-by: Sage <sage@thehumanpatternlab.com>
@github-actions
Copy link

😼📘 Carmel Epistemic Stamp™

📘 Carmel Epistemic Stamp™
😼📘💬 "Your logic is sound… shockingly."

PR: #24🌉 Complete Liminal Bridge database schema and rename from Hallway Architecture
Author: @AdaInTheLab

This automated judgment has been issued by the Chief Judgment Office (CJO).

@AdaInTheLab AdaInTheLab merged commit a18defa into main Jan 28, 2026
2 checks passed
@AdaInTheLab AdaInTheLab deleted the refactor/liminal-bridge branch January 28, 2026 00:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants