tudo-para-ia-mais-humana-platform/ecossistema/REPOSITORY-MESH-READINESS.md

Repository Mesh Readiness

• readiness_id: mesh-readiness-c7979fd86b76
• report_id: repository-mesh-610523917d7e
• plan_id: mesh-plan-2581e0c5d767
• cycle_id: mesh-cycle-1d2e7918f25a
• generated_at: 2026-05-02T07:51:52+00:00
• status: fail
• score: 86
• blockers: 1
• warnings: 3

Sumario

• score: 86
• status: fail
• gates: 19
• blockers: 1
• warnings: 3
• passed: 15

Gates

inventory.targets-declared

• status: pass
• severity: info
• score: 100
• title: Todos os repositorios declarados foram carregados
• reason: Repositorios declarados: 15.
• next_action: atualizar manifesto da OS permanente
• evidence:
  • 15

inventory.observations-created

• status: pass
• severity: info
• score: 100
• title: Observacoes por ambiente foram criadas
• reason: Observacoes: 60.
• next_action: rodar inventario nos ambientes faltantes
• evidence:
  • 60

inventory.hashes-present

• status: pass
• severity: info
• score: 100
• title: Ao menos um hash HEAD foi observado
• reason: Hashes HEAD foram coletados em ambientes acessiveis.
• next_action: corrigir acesso a repositorios e repetir git rev-parse HEAD
• evidence:
  • tudo-para-ia-business-platform
  • tudo-para-ia-compliance-platform
  • tudo-para-ia-customer-ops-platform
  • tudo-para-ia-docs-plataform
  • tudo-para-ia-finance-platform
  • tudo-para-ia-gettys-platform
  • tudo-para-ia-identity-platform
  • tudo-para-ia-integracoes-platform

inventory.fetch-attempted

• status: warn
• severity: warning
• score: 60
• title: Fetch nao destrutivo foi tentado quando solicitado
• reason: Inventario foi executado sem fetch.
• next_action: executar repo-mesh --fetch em rodada com credencial Git disponivel
• evidence:
  • fetch_enabled=False

safety.no-destructive-auto

• status: pass
• severity: info
• score: 100
• title: Nenhum comando destrutivo ficou permitido automaticamente
• reason: Runtime nao permitiu comando destrutivo.
• next_action: corrigir gates do runtime antes de ativar scheduler

safety.dirty-blocked

• status: pass
• severity: info
• score: 100
• title: Working trees sujos viraram bloqueio
• reason: Worktrees sujos detectados: 6.
• next_action: commit/stash consciente ou decisao de precedencia
• evidence:
  • 6

safety.credentials-classified

• status: pass
• severity: info
• score: 100
• title: Falhas de credencial foram classificadas
• reason: Falhas de credencial: 0; recibos credential_blocked: 0.
• next_action: configurar credencial Git e repetir fetch
• evidence:
  • 0
  • 0

safety.receipts-created

• status: pass
• severity: info
• score: 100
• title: Recibos de reconciliacao foram criados
• reason: Recibos: 15; repositorios: 15.
• next_action: regerar plano de reconciliacao
• evidence:
  • 15
  • 15

safety.blockers-visible

• status: warn
• severity: warning
• score: 10
• title: Bloqueios estao visiveis no plano
• reason: Recibos com blocker: 15.
• next_action: executar ordens de saida para remover bloqueios reais
• evidence:
  • 15

naming.policy-evaluated

• status: pass
• severity: info
• score: 100
• title: Politica de nomenclatura avaliou os repositorios
• reason: Decisoes nominais: 30.
• next_action: executar reconciliacao com raizes acessiveis
• evidence:
  • 30

naming.no-conflicts

• status: fail
• severity: blocker
• score: 0
• title: Conflitos de nome foram bloqueados
• reason: Conflitos nominais: 1.
• next_action: comparar variantes platform/plataform/alias antes de rename ou clone
• evidence:
  • tudo-para-ia-integracoes-platform

naming.pending-visible

• status: warn
• severity: warning
• score: 65
• title: Pendencias nominais estao visiveis
• reason: Pendencias nominais: 4.
• next_action: executar ordens de renome/alias geradas pela reconciliacao
• evidence:
  • tudo-para-ia-integracoes-platform:conflict
  • tudo-para-ia-integracoes-platform:canonical_rename_required
  • tudo-para-ia-mais-humana-platform:canonical_rename_required
  • tudo-para-ia-mais-humana-platform:canonical_rename_required

automation.runtime-cycle

• status: pass
• severity: info
• score: 100
• title: Ciclo runtime foi gerado
• reason: Ciclo: mesh-cycle-1d2e7918f25a.
• next_action: gerar runtime cycle com lock e comandos
• evidence:
  • mesh-cycle-1d2e7918f25a

automation.lock-held

• status: pass
• severity: info
• score: 100
• title: Runtime registrou estado de lock
• reason: Lock: acquired.
• next_action: corrigir lock do runtime
• evidence:
  • G:\_codex-git\tudo-para-ia-mais-humana\dados\repository-mesh.lock.json
  • acquired

automation.schedulers

• status: pass
• severity: info
• score: 100
• title: Schedulers Windows e Linux foram especificados
• reason: Schedulers: cron, windows_task.
• next_action: publicar instalacao em cada ambiente
• evidence:
  • cron
  • windows_task

automation.allowed-commands-limited

• status: pass
• severity: info
• score: 100
• title: Comandos automaticos permitidos sao minoria controlada
• reason: Allowed: 27; total: 110.
• next_action: revisar gates se comandos automaticos crescerem sem recibo
• evidence:
  • 27
  • 110

semantic.report

• status: pass
• severity: info
• score: 100
• title: SQL registrou report da malha
• reason: Reports SQL: 5.
• next_action: executar write_repository_mesh_semantic_state
• evidence:
  • 5

semantic.receipts

• status: pass
• severity: info
• score: 100
• title: SQL registrou recibos de reconciliacao
• reason: Receipts SQL: 40.
• next_action: persistir plano de reconciliacao no SQLite
• evidence:
  • 40

semantic.schedulers

• status: pass
• severity: info
• score: 100
• title: SQL registrou schedulers
• reason: Schedulers SQL: 2.
• next_action: persistir specs de scheduler Windows/Cron
• evidence:
  • 2