portugalfuturista/replica-omnisciente
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 68
replica-omnisciente/research/pt-futurista-audit/brief.md
fabiorafaelcoutada 5a6296eaa4 chore(research): pt-futurista audit
2026-07-12 20:53:08 +01:00

2.2 KiB
Raw Permalink Blame History

Research Brief: Portugal Futurista Full Ecosystem Audit

Date: 2026-07-10 Depth: standard (3-5 sub-agents, 15+ sources target)

Refined Question

Comprehensive ecosystem audit of the Portugal Futurista IoT platform, covering two repositories:

  1. replica-omnisciente — centralized brain, agent orchestration, and monorepo of tools (dirac, tilth, toon)
  2. nervura-electrica — self-hosted infrastructure (Proxmox, Docker, Cloudflare) and AWS IoT CloudFormation

Research scope: architecture, tech stack, security posture, operational health, CI/CD reliability, sync infrastructure, dependencies, exposed secrets, permission issues, and recommendations.

Scope Boundaries

In scope:

  • Architecture analysis of both repos
  • Security audit: secrets in code, permissions, exposed attack surfaces
  • Operational health: resource overcommit, offline services, infrastructure drift
  • CI/CD pipeline reliability and security
  • Brain sync infrastructure integrity
  • Dependency audit and risk assessment
  • Cross-repo integration patterns

Out of scope:

  • Code-level bug hunting (this is a systems audit, not a code review)
  • Performance benchmarking
  • Feature completeness assessment

Assumptions

  • Both repos are local at /home/fabiorafaelcoutada/portugalfuturista/
  • The user has root access to the Proxmox host (192.168.0.38)
  • Self-hosted infra runs on Starlink CGNAT with Cloudflare Tunnel
  • Current date: 2026-07-10

Angles

  1. F1: replica-omnisciente architecture & tech stack — Map the monorepo structure, subprojects (dirac, tilth, toon, shared), MCP server ecosystem, and agent fleet coordination patterns
  2. F2: Security posture across both repos — Exposed secrets, .env handling, SSH key management, Cloudflare tunnel security, API key rotation, permission models
  3. F3: nervura-electrica infrastructure health — Proxmox resource overcommit, offline CTs, service duplication, disk/memory pressure, migration status
  4. F4: CI/CD & sync reliability — GitHub Actions + Forgejo workflows, brain sync integrity, Kimi import pipeline, deployment automation gaps
  5. F5: Dependency & operational risk — Package freshness, known vulnerabilities, single points of failure, backup strategy, disaster recovery readiness