REMI: PostgreSQL as Agentic Core in Tiger Cloud (Agentic Postgres Challenge by Auth0)
REMI is a reproducible heritage agent that consolidates, validates, and exports digital assets with surgical traceability. This project was developed for the Agentic Postgres Challenge, powered by Auth0 and Tiger Data, using PostgreSQL as its operational core.
🧩 What is REMI?
REMI (Repositorio de Estructura y Manifiestos Inteligentes) is an agentic system that:
- Inserts and validates heritage manifests in a PostgreSQL database
- Exports records with hardened technical routines and bilingual documentation
- Backs up assets to multiple destinations (local and cloud)
- Documents each cycle as a signed technical block
🧠 PostgreSQL as the agentic brain
The remi-agentic-core database hosted on Tiger Cloud acts as the system’s brain:
- Main table:
manifiestos_remi - Records: 9 validated heritage manifests
- Technical flow:
- Connection via
psqlwith hardened credentials - Visual validation of records
- Export using
\COPYto CSV - Dual backup to sda7 and Google Drive
- Documentation of the cycle in a signed technical file
- Connection via
🔐 Hardened connection example
bash
psql 'postgres://tsdbadmin:Jrrg2025_Code!@lo3rxmuxxi.mg0py0ryg3.tsdb.cloud.timescale.com:37725/tsdb?sslmode=require'
📤 Heritage export
psql '...' -c "\COPY (SELECT * FROM manifiestos_remi ORDER BY id) TO '~/REMI_local/docs/manifiestos_remi_export_2025.csv' CSV HEADER"
📁 Manifest structure
Each record includes:
File name
Structured JSON content
Timestamp
Examples: manifesto_remi.json, registro_patrimonial.txt, validacion.sh, cierre_tecnico_remi.json
🗂️ Source code
Project available at:
- [SourceForge: remi-agentic-core](https://sourceforge.net/projects/remi-agentic-core/)
- [GitHub: jramonrivasg/remi-agentic-core](https://github.com/jramonrivasg/remi-agentic-core)
Key scripts: remi.sh, validacion.sh, exportacion_remi_timescaledb.txt
📸 Screenshots and validation
Included:
psql output showing ordered records
CSV export preview
Code fragments and executed commands
🏁 Technical closure
The REMI cycle was executed, validated, and documented:
✅ Hardened export confirmed
✅ Dual backup completed
✅ Signed technical document created
✅ Ready for publication and legacy preservation
## 🎥 REMI Demo – English Version
This demo marks the official closure of REMI’s first technical cycle.
Validated by Ramón Rivas.
Produced under MintBridge XFCE v1.0.
This artifact consolidates identity, purpose, and legacy.
REMI is alive.
🔗 [Watch the demo](https://github.com/Jramone3/REMI-agentic-patrimonial/blob/main/demo_remi_final.mp4)
🏷️ Tags
#agenticpostgreschallenge #devchallenge #postgres #ai
🙌 Acknowledgments
Thanks to Auth0, Tiger Data, and the DEV community for powering this challenge. REMI stands as a reproducible heritage agent with PostgreSQL as its agentic core.
🇪🇸 Versión en español
REMI es un agente patrimonial reproducible que consolida, valida y exporta activos digitales con trazabilidad quirúrgica. Este proyecto fue desarrollado como parte del Agentic Postgres Challenge, impulsado por Auth0 y Tiger Data, usando PostgreSQL como núcleo operativo.
La base de datos remi-agentic-core en Tiger Cloud actúa como cerebro del sistema, con 9 manifiestos patrimoniales validados, exportados en CSV, respaldados en sda7 y Drive, y documentados como bloque técnico firmado.
El proyecto está disponible en SourceForge, incluye scripts blindados (remi.sh, validacion.sh) y cumple con todos los requisitos del reto. El ciclo REMI queda cerrado, firmado y listo para publicación.
Top comments (2)
Great job with REMI! I really like how PostgreSQL supports the agentic core in Tiger Cloud. The focus on reproducibility, validating heritage manifests, exporting with bilingual documentation, and having dual cloud-local backups really demonstrates solid design principles. I'm curious, how did you handle credential hardening for the psql workflow during production cycles?
Thank you, Michael 🙏
I truly appreciate your thoughtful feedback on REMI’s architecture. PostgreSQL has proven to be a solid foundation for agentic workflows, especially when paired with Tiger Cloud’s real-time capabilities.
Regarding your question on credential hardening during production cycles:
REMI uses a dual-layered approach for
psqlauthentication:.pgpassroutines for CLI automation, ensuring reproducibility without exposing secretsThese credentials are rotated per cycle and backed up in both local and cloud vaults, maintaining traceability and custodial integrity.
Thanks again for engaging with REMI’s legacy.
Your insight reinforces the value of reproducible, bilingual, and secure agentic design.
— Ramón Rivas :: Custodian of REMI
Gracias, Michael 🙏
Aprecio profundamente tu comentario sobre la arquitectura de REMI. PostgreSQL ha sido una base sólida para flujos agenciales, especialmente cuando se integra con las capacidades en tiempo real de Tiger Cloud.
Respecto a tu pregunta sobre el fortalecimiento de credenciales durante los ciclos de producción con
psql:REMI emplea un enfoque de doble capa para la autenticación CLI:
.pgpass, que permiten automatización reproducible sin exposición de secretosEstas credenciales se rotan por ciclo y se respaldan tanto en bóvedas locales como en la nube, manteniendo trazabilidad y custodia patrimonial.
Gracias nuevamente por tu interés en el legado de REMI.
Tu observación refuerza el valor de un diseño agencial reproducible, bilingüe y seguro.
— Ramón Rivas :: Custodio de REMI