REMI AuthBridge: Patrimonial Identity Demo with Auth0 Integration
jramonrivasg – November 2025
Location: Turmero, Aragua, Venezuela
Project: REMI – Patrimonial Identity Agent
🧠 Purpose
This demo showcases a minimal functional integration of Auth0 into REMI's patrimonial identity flow.
Features:
- Auth0 login/logout
- Protected GitHub token vault
- User profile visualization
- Ready for public deployment (Glitch, Vercel, GitHub Pages)
🔐 Auth0 Integration
-
Domain:
dev-bo2ybhrn0nw1awbe.us.auth0.com -
Client ID:
N7Hx2pFEtikCOvNrxJI7EcduAkAACNNW - Frontend only – no secrets exposed
Routes:
/login/callback/logout
🧪 Protected Resource
Once authenticated, users gain access to a protected GitHub token:
text
🔐 Token GitHub: ghp_remiPatrimonialToken2025
🚀 Deployment
🔗 Live Demo on Vercel
📜 License: MIT 📅 Redeploy triggered: 8 November 2025
🤝 Future Contributions
We welcome collaborators interested in:
Expanding REMI’s agentic memory with real-time data
Integrating backend validation with Postgres or MongoDB
Translating the interface into more languages
Enhancing the ceremonial narrative layer
Feel free to fork, contribute, or reach out!
---
## 🧠 Postgres as Agentic Core
REMI now includes a functional simulation of patrimonial persistence using Postgres.
This flow incorporates:
- `/api/patrimonio` API to register tokens, agents, and timestamps
- `PostgresSender` component to send data from the frontend
- `TablaPatrimonial` component to visualize patrimonial memory
- Agent dialogue (`REMI`, `REMI_Auditor`) to validate actions
This approach represents a patrimonial multi-agent architecture with simulated persistence, aligned with the principles of the Agentic Postgres Challenge.

Top comments (0)