n.V4-6.07 | THE TOOL CARRIES THE METHOD
01| Training that stops before the tool is unfinished. A Maveriq who understands project design and has no instrument for producing a design will produce nothing — and will reasonably conclude the training was talk.
02| So tools are part of the curriculum, not something the technology division delivers afterwards. The method lives inside the instrument. The MM360 planning tool is not a convenience for applying the MM360 framework; for most Maveriqs it is where the framework is actually learned, one prompt at a time, while doing real work.
WHAT THEY HAVE TO BE
03| Four constraints, none negotiable. Usable by someone with limited technical background. Mobile first, because the phone is the primary device and often the only one. Functional offline, because connectivity in a barrio is not a given. Multilingual, because the barrios we intend to serve do not share a language.
04| A fifth is cultural rather than technical: friendliness beats power. Where a more capable tool exists and a simpler one will do the job, we take the simpler one. This costs capability at the top end and buys participation at the bottom. Participation is what the system runs on.
THE SET
05| The Maveriq Toolkit is the core: planning templates, budget tools, coordination, progress tracking, quality checklists, documentation. Built in-house for an unglamorous reason — no existing toolkit is designed for inexperienced changemakers executing real community projects under professional oversight. That gap is the whole product.
06| Local flavour customization lets each CITI adapt language, currency, local resources and templates on top of a standard core. The tension is permanent: standardize too hard and the tool feels foreign; localize too far and nothing transfers between barrios, which kills the knowledge commons.
07| The mobile app is the actual interface for most Maveriqs — dashboard, marketplace, training, communication, data collection, offline.
08| Learning games teach through consequence rather than instruction: a barrio simulation for strategic thinking, a project filter game for evaluation, a financial literacy simulation, a pitch platform. Games also recruit. Someone who will never sign up for a course will play something a friend showed them.
09| The track record system records completions, verifications, peer ratings and impact — the asset described in 6.02.
10| The learner marketplaces are where choice sits: communities of practice, curated life-admin apps, mentors, and a Basic Task Marketplace of small paid tasks with clear acceptance criteria. A person can find a group, install one tool that clears an hour out of her week, take a small task and meet a mentor, all inside the same week. Short loops build momentum, and momentum is what keeps people.
BUILD OR BUY
11| We build where the tool encodes IkoCiti's method — toolkit, MM360, quality assessment, track record, games, the apps. We curate third-party where standard functionality is already good — messaging, video, document collaboration. Rebuilding a messaging app would be an expensive way to demonstrate seriousness.
12| The AI layer is the one we are least able to promise. Automated quality assessment, matching, translation, pattern recognition across barrios, a reliable assistant beside every user — all of it would substantially change our cost structure, and none of it is proven at the reliability we would need. Our position on AI throughout this book is the same: not if, but when. That is a forecast, not a plan, and anything depending on it needs a version that works without it.
STATUS
13| Phase one is the toolkit, MM360, basic data collection and the mobile app. Everything else waits. A platform that ships nine tools badly is worse than one that ships four that work, because the Maveriq who abandons a broken tool in her first month rarely comes back to try the next one.
