MAKO enforces deterministic IV&V rigor: (1) Automated unit & integration test suites with 100% critical-path coverage, run before every commit. (2) Independent code review by external evaluators against both SCVS (source code vulnerability standards) and SWVS (secure web app vulnerability standards), with documented remediation and re-verification on every finding. (3) On-chain contract verification — all deployed contracts independently re-verified against their source commit; state consistency checked across live mainnet. (4) Live end-to-end acceptance testing with documented evidence trails: real transactions, real wallet signatures, operator-verified execution traces, before any green status is issued. (5) Evidence completeness gates — no milestone advances without reconstructable, hash-verified audit logs. (6) No security-gate bypass — findings block deployment; remediation and independent re-verification are mandatory before cutover. Multiple rounds per cycle are standard, not exceptional.
Current Rigor Principle
Green status requires: live + independently verified + operator acceptance + documented evidence
IV&V FAIL blocks production cutover; no workarounds or exceptions
Each remediation cycle includes independent re-verification before clearance
🧭 The Road Ahead (Scan Utilities)
See the milestone cards above for what's next in detail. This panel covers delivery mechanics that don't have their own milestone card:
Automate the deploy pipeline (still manual today)
On hold (2)
Cross-Chain Market Swap Bridge: BSC BNB → LRC MAKO — core swap engine proven live on-chain (Mar 2026); redesign required after a governance/custody review found the delivery mechanism needed rework before further real deployment
Gold links open the in-development subproject's own roadmap. Cross-project linking convention pending MAKO-Core standardization.
Our Web Principles
Target-Only EditsSmall, bounded changes
Source-Backed MetricsNo guessed values
Browser VerifiedUI checked visually
Protected Paths ExcludedNo unrelated staging
Local-First QAValidate before checkpoint
Checkpoint DisciplineCommit only verified work
Current IV&V in Work
Bridge V7/V8 — preparing a formal IV&V request (process issued by MAKO Core 2026-10-04)
Sub Project
MAKO Bridge (MAKOv2 Cross-Chain)
Milestone Being Tested
18b-18c: Final IV&V and Governance Cutover
Current Status
Round 9 FAIL (2026-10-02); the Round 10 candidate frozen 2026-10-03 was itself superseded the next day. MAKO Core's 2026-10-04 response withheld deploy approval pending ten findings; as of 2026-10-04 all ten are closed (including the Site5 bridge cron intervals, corrected 2026-10-05 to the required 15-minute minimum). The one batch commit (not yet started) and MAKO Core's blind pre-review remain ahead; not yet resubmitted for a new IV&V task order. Core design remains confirmed sound
Green: Complete — live + operator verifiedYellow: In development — active work in progressRed: Pending or not startedGOVERNED. DETERMINISTIC. IEEE 1012 Standards. SCWE Governance. Source of truth: report/planning/MAKO-WEB-POAM.md.