LOOP Network Health Monitoring

Update from MAKO Posse (2026-07-29)

An onboarding review of prior MAKO Posse and MAKO Website artifacts found one real, live component already in production — the RPC-availability probe (loop-status-watch.php), confirmed via real cron-run log data through July 28 — sitting alongside a much more ambitious infrastructure-mapping utility (DNA Collector) that had never been implemented: five git commits, all documentation, across a 1,154-line ontology specification covering 30+ entity types and 40+ relationship types. A second, planned interpretation layer (DNA Watcher) had no artifacts at all. That mismatch — extensive planning ceremony against zero shipped functionality — was the same pattern already identified and partly corrected in the MAKO-Core governance archive. This project replaces that design with a leaner, two-phase plan: build on the RPC signal that already works, and narrow the infrastructure map to a bounded watchlist scoped for security relevance (authority changes, bridge/relay integrity, new-deployment triage) rather than open-ended, whole-chain discovery. Both phases now have MAKO Web integration contracts published — Phase 1's is a complete, reviewed schema; Phase 2's is deliberately left as a stub until its design settles, so the same premature-specification mistake isn't repeated on the interface side.

Milestones

Relationship to MAKO Web

This roadmap covers the MAKO Posse Team's own build work. It does not yet appear as a live feature on the site. Once Phase 1 (and, on its own later timeline, Phase 2) reach their acceptance gates and the corresponding interface contract is live and proven, the MAKO Web Team integrates the resulting signals into the LOOP health utility — following the same request/answer/POA&M handoff pattern already used for Contract Scan, and the same producer-owned interface-registry convention already established by MAKO-WEB-LOOP-RPC-STATE-V1.