REMI Evolved: Beyond the Agentic Postgres Challenge

Introduction

REMI was originally submitted to the Agentic Postgres Challenge (DEV/Tiger, November 2025). Since then, the project has evolved significantly, surpassing its initial scope and becoming a fully auditable and secure patrimonial agent.

---

From Challenge Version to Evolved Agent

• Challenge version (2025-11-09):
  • Basic patrimonial tables
  • Initial technical view
  • Event insertion
• Evolved version (current):
  • Automatic auditing with functions and triggers
  • Encrypted and signed patrimonial backups
  • Clear roles and ACLs (remi_reader, remi_writer)
  • Active patrimonial memory and filtered views
  • Master key and auditable rotation
  • Repository integrity seal

---

Automatic Auditing

Trigger example:

CREATE TRIGGER log_publicacion_auditoria
AFTER INSERT ON publicaciones_remi
FOR EACH ROW
EXECUTE FUNCTION log_publicacion_auditoria();

Patrimonial Security

GPG-encrypted dumps

Verifiable SHA256 hashes

Signed commits and tags

Live Demo

Coming soon on Tiger Cloud:

/publicaciones

/auditoria

/estado

Contribution and Feedback

We invite the community to explore the evolved version of REMI, test the demo, and share suggestions.

Conclusion

REMI not only fulfilled the challenge, but surpassed it — continuing to grow as a secure, auditable patrimonial agent.

---

REMI has evolved beyond its original submission to the Agentic Postgres Challenge. This post documents its transformation into a fully auditable, secure, and operationally transparent agent.

Comments

[Jramone3]

🔗 Official complement to the Agentic Postgres Challenge submission:

This post documents the evolution of REMI beyond the challenge, featuring automatic auditing, extended patrimonial security, and a repository integrity seal.

👉 Read the full article here: REMI Evolved: Beyond the Agentic Postgres Challenge

A public sandbox for live testing will be available soon.