Infrastructure — Content Sync

MAKO Web — Weekly Roadmap Sync

Last Updated: October 21, 2026 at 08:55 PM EDT

Standing responsibility to keep the public roadmap pages (main roadmap.html and 12 subproject pages) current with each project's real source-of-truth POA&M documents. Established per MAKO-CORE-TO-MAKOWEB-001 (2026-09-16) as the permanent sync mechanism, replacing ad-hoc manual updates. A scheduled cloud agent runs every 6 hours and commits verified updates; a daily scheduled deploy at 10 PM Eastern publishes them. The conservative, diff-based procedure avoids rewrites of subproject pages and flags major gaps for human review rather than acting unilaterally.

Authority: MAKO-CORE-TO-MAKOWEB-001 (2026-09-16). POA&M source: report/planning/2026-09-30-MAKO-Web-Weekly-Sync-POA-M-v1.0.md. Runbook: report/roadmap-sync/RUNBOOK.md (revised 2026-09-29, full scope: 13 pages, all MAKO projects).

Current state: GREEN (automation live and verified)

Sync operational. The scheduled cloud routine runs every 6 hours, reads every source project's POA&M, makes only sourced status edits, verifies the "What We Have Achieved" data automatically, and commits to the repository. A daily scheduled deploy at 10 PM Eastern publishes the result with a byte-for-byte check; the first scheduled run on 2026-10-04 passed, with every page matching byte for byte.

Gap analysis findings (2026-09-30)

Issue: RUNBOOK.md step 3b requires checking main roadmap.html's "What We Have Achieved (Live)" section against subproject POA&Ms, but 2026-09-29 manual sync missed this check. Result: two live utilities (Harvester V1, Contract Scan L1) left out of the achievements list despite their POA&Ms showing "live" status. Root causes: (1) scheduled routine not running due to account credit limits, (2) manual runs incomplete — subproject pages checked but achievements consistency not systematically verified, (3) no explicit criteria defining what POA&M status qualifies for "live" listing. Full analysis: report/roadmap-sync/SYNC-GAP-ANALYSIS-2026-09-30.md. Resolved: routine restored and running every 6 hours (M4), checklist expanded (M3), "live" criteria defined (M5), achievements now stored as verified data (M6).

Milestones

Sync infrastructure establishedRUNBOOK.md written and approved, scheduled cloud routine registered, manual runs operational, infrastructure (deploy script, Telegram integration) in place. Authority: MAKO-CORE-TO-MAKOWEB-001.

Complete

Sync gap analysis completedRoot causes identified: scheduled routine credit-blocked, manual runs incomplete, "live" criteria undefined. Two live utilities missing from achievements identified and documented. Recommendations drafted for short/medium/long term.

Complete

Immediate gaps closed (manual)Harvester V1 and Contract Scan L1 added to roadmap.html "What We Have Achieved (Live)" section; both deployed to production, byte-verified live, Telegram notified. Roadmap current as of 2026-09-30.

Complete

Expand sync checklist for achievementsUpdate RUNBOOK.md step 3b to add explicit sub-step for main roadmap.html "What We Have Achieved" consistency check against subproject POA&Ms. Define clear success criteria (all live utilities listed, links correct, descriptions current). Next manual sync to verify new checklist catches all gaps.

Complete

Restore scheduled routineRoutine restored and running every 6 hours; each run reads all source projects and commits a dated audit trail. The routine's instructions are read from the repository on every run, so procedure changes need no manual update.

Complete

Define "live" criteriaCriteria defined and applied: a utility is listed as live only when its POA&M is GREEN, independent IV&V is PASS (or PASS WITH RESIDUAL RISK with residuals resolved), the operator has accepted go-live, and it is priced and published. Documented in RUNBOOK.md as a status-mapping table.

Complete

Structure achievements as data"What We Have Achieved" is stored as structured data with an automated check, run on every sync, that each entry meets the live criteria and appears on the roadmap. Three live utilities verified.

Complete

Credential handling for the automationThe cloud routine holds no credentials; the scheduled deploy uses its own protected configuration on the host. No secrets are stored in the repository.

Complete

Read sources without local credentialsThe routine reads each source project's repository through the platform's read-only GitHub connector; no personal access token is used.

Complete

Automated deploymentDaily at 10 PM Eastern: pull the latest committed pages, publish, and verify every roadmap page byte for byte. The first scheduled run on 2026-10-04 passed (15 of 15 pages matched). Report PDFs are published separately, not by this job.

Complete

M10

Schedule automationOne scheduled routine, every 6 hours, committing directly to the main branch; a scheduled run on 2026-10-04 confirmed this.

Complete

M11

GitHub as source of truthEach project keeps its POA&M in its own repository; the routine reads from those canonical sources.

Complete

M12

Credential rotation and secrets hygieneAll automation credentials were rotated on 2026-10-04 and are held only where they are used.

Complete

M13

Operator requirements documentedA single authoritative requirements document records the sync cadence, the deploy schedule and the credential rules, so they need not be restated.

Complete

M14

Roadmap-update noticeAfter a verified deploy, a one-line summary of milestone and stage-status changes is posted to MAKO's Telegram channel. Enabled 2026-10-04; the first fully automatic post went out on 2026-10-05.

Complete

M15

Public pages kept free of tool namesTen tool-name mentions were removed from public pages on 2026-10-05, and an automated check now blocks any publish that contains one and screens notice text. Live pages scanned as visitors receive them: clean.

Complete

M16

Roadmap card text reduced2026-10-05, operator request (page too big): the bullet text inside each stage card on the main roadmap was removed, leaving title, status pill and subproject link. Everything below the cards, the theme, grid, progress strip and images are unchanged.

Complete

STD-1012

Verification and validation evidence package (IEEE 1012-2016)The evidence package that shows how this project's work meets the IEEE 1012-2016 standard for verification and validation. MAKO Core checks it is complete; it is not an independent verdict.

NOT STARTED

STD-SCSVS

Smart contract security evidence package (OWASP SCSVS)The evidence package that shows how this project's contracts and page meet the OWASP Smart Contract Security Verification Standard, version 0.0.1. MAKO Core checks it is complete; it is not an independent verdict.

N/A (no on-chain code of its own)

Scope and coverage

Main roadmap page: site/roadmap.html — 12-column stage cards, "What We Have Achieved (Live)", "Current State" (IV&V Standards block), "Next Gates", "Road Ahead", "On hold" list, utility-price claims.

Subproject pages: 12 dedicated roadmap pages (Harvester, PayFlow, PayFlow V2, Liquidity Pools, MakoSig, Bridge V6/V7/V8, Wallet Trace, Contract Scan, Backup Migration to BSC, LOOP Health Monitoring) plus this page (MAKO Web).

Subproject sources (POA&Ms): Real POA&M documents in each project's own repository (Harvester, mako-payflow, mako-lp-incentives, MakoSig, Capt-Ken-Lahr-bridge-contracts, wallet-trace, contract-scan, MAKO-Posse). MAKOv2 explicitly excluded per its own POA&M confidentiality directive and standing operator instruction.

Conservative procedure: Read POA&M, diff against live page markup, edit only discrete status changes (e.g., YELLOW → GREEN), flag anything larger for human review. Never invent milestones or rewrite subproject pages unilaterally. A dated audit-trail report from every run is committed to report/roadmap-sync/ for full visibility.

Relationship to the rest of the roadmap

MAKO Web itself has two standing responsibilities on the main roadmap: (1) the site's own development (Wallet Trace, Contract Scan integration, utilities) tracked through the stage cards, and (2) the ongoing sync of all 13 pages to their sources (this project). The sync is infrastructure, not a customer-facing deliverable, but it's a dependency for roadmap accuracy — without it, the public pages drift stale and readers can't trust the status claims. Sync failures (or gaps like the 2026-09-29 achievements miss) mean operators must manually audit and correct the roadmap instead of relying on automated consistency checks.

Source of truth

MAKO Web Team is responsible for keeping this POA&M and all milestone status current. Weekly roadmap sync verifies all 13 MAKO project pages against their source POA&Ms to ensure consistency across the public roadmap.