V2-3.08| INTELLIGENCE, NOT BUREAUCRACY
01| Every platform running work at this complexity faces the same choice and usually gets it wrong in one of two directions. Over-control turns each project into a bureaucratic gauntlet, and the autonomy the model depends on quietly disappears into approval workflows. Under-control lets quality vary until the first serious failure takes the platform's reputation with it. Neither is survivable here.
02| The answer is to calibrate control to risk rather than applying it uniformly. Most projects run with light oversight. Larger projects get more support. Genuinely risky projects get professional intervention. Every project, regardless of size, gets automated regulatory screening. Controls fire when they need to fire and stay out of the way when they do not.
03| Layer one — peers and AI. The default for everything. Peer Maveriqs review project plans in an advisory capacity, not as gatekeepers; the point is informal stress-testing rather than approval. Automated checks scan for budget errors, unrealistic timelines, missing implementation steps and regulatory flags. Community visibility does the rest — when other Maveriqs and neighbours can see what is planned, weak planning gets caught socially before it reaches execution. This layer handles the large majority of projects, and it should. Most Maveriqs working at the scope they are qualified for produce solid work without supervision, and a design that assumes otherwise insults the people it depends on.
04| Layer two — mentors and coaches. Fires on specific triggers: budgets past a threshold, durations past six months, high technical or social complexity, new teams without a track record, or projects touching local political and cultural friction. Experienced practitioners provide guidance through regular check-ins. The relationship is advisory. The mentor does not run the project; she catches issues early, surfaces blind spots, and brings patterns from work that has already been done. If she sees risk beyond her scope, she escalates.
05| Layer three — professional intervention. Reserved for critical risk: potential safety incidents, reputational damage that would travel beyond the local context, government relationships that could close doors for other CITIs, financial exposure beyond normal project scale, or repeated failure suggesting the team cannot recover on its own. Usually the project continues with substantially more support; sometimes it gets restructured; occasionally professionals take it over.
06| How a takeover is handled matters as much as when. It is framed publicly as a complexity decision, not a competence verdict. The Maveriq team's standing is protected, stakeholder relationships are maintained with the incoming team representing continuity rather than replacement, and the community still gets the thing that was promised. Layer three exists because some risks are too large to bet on every team absorbing them. The way it fires exists because a system that humiliates people for taking on hard work will stop having people who take on hard work.
07| Layer four — regulatory screening. Runs on every project before launch. Automated checks against financial, legal, safety, environmental and labour requirements in the relevant jurisdiction. Red flags block launch until resolved. No Maveriq team and no peer reviewer can reasonably be expected to know every regulation that might apply, so compliance is handled as a system function rather than an individual responsibility.
08| The second half of the model is recognizing that not all work suits the same producer.
09| PI Projects are Maveriq-led: mentorship, dialogue, cooperatives, peer education, community organizing. Relationship-intensive, dependent on local knowledge that only embedded people have, adaptable by necessity, transferable from Maveriq to Maveriq, and low in technical barrier. This is where our structural advantage lives. No external organization delivers this work as well, because none has the embedded knowledge or the peer-trained capacity to scale it.
10| PI Light Projects are professional-led: construction, solar, water systems, renovation, technical infrastructure. Specialized expertise built over years, expensive equipment, safety-critical, regulation-heavy, and not transferable to peer training at scale. You cannot teach a barrio cohort to safely install electrical systems as a side effect of community organizing. Our commitment to Maveriq autonomy does not extend to pretending otherwise. Maveriqs may take supporting roles where local knowledge helps; the technical execution sits with professionals.
11| Hybrid Projects are both, coordinated. A community centre that needs building and then needs programming. A water system that needs installing and then needs maintenance training and community education. These appear on the Exchange as two coordinated projects rather than one — the professional team contracts for the technical work, the Maveriq team for the social work, and the Exchange enforces the coordination between them.
12| Hybrids exist to prevent one specific failure, and it is the most visible failure in development: the white elephant. Infrastructure built and never activated. Community centres standing empty. Water systems nobody was trained to maintain. Training facilities with no programmes inside them. The sector produces these constantly, because the technical project gets funded and delivered while the social activation never gets coordinated. Requiring both halves to ship together makes coordination the deliverable rather than an afterthought.
13| The thresholds, the tiers and the trigger points in this chapter are working parameters and will move as evidence comes in. The principle underneath them will not: intelligence over bureaucracy, calibration over uniformity, autonomy wherever autonomy can be supported responsibly. Traditional project management adds oversight as scale grows, so friction increases with every new project. This design refuses that trajectory, because a system that gets heavier as it grows cannot reach the size the problem requires.
