A comprehensive view of TenzaOne — the platform, the AI agents, the shared services, and the business units running on top. Phase-tagged so you can see at a glance what is live today, what is iterating, and what is on the Phase 3+ roadmap.
Strategic governance flows down. External signals flow in. TenzaOne shared services route, validate, and standardise. Business-specific AI applies domain logic and surfaces it to operators, capital, and carbon-market participants. Hover any block for component depth.
tenza-projects · tenza-vcs-assessment · tenza-wallet · tenza-analytics · tenza-outreach · tenzaone-terminal · tenza-companies · coachStrategy · compliance · cross-business intelligence
IoT · satellite · carbon registries · weather/market
carbon-markets-widget, regulatory APIs. DePIN sensor mesh + MCP-driven satellite ingest in Phase 3. Phase 2 · iteratingBridge between AI agents and platform context
mwai_mcp_tools. Fallback: guarded class-mcp-server. Enterprise multi-tenant MCP routing planned for Phase 3. Phase 2 · iteratingDecentralised data acquisition + verification
Provenance · entitlements · governance
Solar thermal · AMS-II.C / AMS-I.E / VT0001
HVAC optimisation · building digital twins
Carbon Asset Futures · DePINaaS · MCP-Ent
Climate developers · cooperatives · SMEs
VC · family offices · impact funds
Operators · Scope-3 reporters
Buyers · verifiers · registries
Four invariants every layer respects.
Async DePIN-ready processing. WP cron + REST queues today; Streamr P2P / Kafka in Phase 3. Coach & agent runs are background-deferred so the page never waits on the model.
Cross-chain & cross-registry standards. VCS schema canonical for project state, UN SDG cross-mapping for impact, single tenza_project CPT shape, paired-entry treasury ledger.
Node redundancy & circuit breakers. try/catch + ob_start guards on every external call. Sim wallet absorbs chain-anchor latency. Phase-3 multi-region Polygon deployment.
From physical sensor wire-protocol up to user-facing application. Each layer carries its own colour identity. Each technology chip is colour-coded by phase — green = live, amber = iterating, violet = planned. Cross-layer concerns — security, scalability, fault-tolerance — apply to every layer simultaneously and live in the sidebar.
User-facing surfaces · auth · smart contracts
tenza_project CPT, REST API, admin shell, custom plugins. Phase 1 · live
Elementor
PeepSo
40+ shortcodes
tenzaone-terminal
WalletConnect
Web3.js / Ethers.jsDashboards · analytics · marketplace UI
A virtual wallet held by the DAO at user_id = 0 (no real WP user has that id). It holds the entire TNZU platform supply in escrow. Initial supply is configurable — default 100,000 TNZU.
Every TNZU granted to a user comes FROM the treasury (paired negative entry). Every TNZU a user pays for a package or action goes BACK to the treasury (paired positive entry). Net system supply = initial_supply + endowments. Always.
At MVP, any admin (manage_options) acts as DAO proxy and can grant from the treasury page or through automatic award rules (signup bonus, wallet activation, founding-member). When on-chain DAO governance lands, grant authority moves to proposal & vote.
tenza_wallet_buy_package): user debit + treasury receive.tenza_credits_debit): user debit + treasury receive.Some legacy grant paths (signup_bonus, sim_wallet_bonus, real_wallet_bonus, sim_to_real_bonus, founding_member) historically wrote only the positive user-side entry. The R15e wiring added treasury mirrors for these flows; pre-R15e bonuses in the ledger will under-report against treasury "granted_out" counters until reconciled.
The treasury model is open by design — every TNZU you hold is traceable back to a treasury grant, and every TNZU you spend on a package returns to the pool.
No project found.
Verified Impact Data Card6-tab project metrics card with anon-aware redaction (Core / Scope 3 / DePIN / Assurance / Intelligence / Help). Phase 2 TensorFlow / PyTorch GrafanaAuth state · service comms · state mgmt
Streaming · queues · cross-chain transport
/tenza/v1/ namespace. Project assessment, scores, summary endpoints. anon-aware via rest_prepare_tenza_project filter. Phase 1
admin-ajax.php
Developer API portal
WP Cron
Streamr P2P
Apache Kafka
RabbitMQ
MQTT brokersAPI gateway · routing · load balancing
/wp-json/tenza/v1/. Phase 1
WP capability system
LiteSpeed CacheLiteSpeedPage-cache tier on the host. Purges on post save via do_action('litespeed_purge_post'). Phase 1
CloudflareCloudflare FreeEdge proxy + DNS + DDoS shield. Phase 3 adds IP Access Rules driven by tenza-analytics suspect-IP feed. Phase 1 / Phase 3 expansion
GraphQL
OAuth 2.1
KubernetesValidation · DePIN protocols · ETL
Sensors · ingestion · edge devices
_tenza_vcs_assessment_data. Phase 1
Owner attestation
Arduino + ESP32
MQTT / CoAP
W3bstream
IoTeX DePINThree subsystems power every business unit: Model Context Protocol routes AI to project state, DePIN handles tamper-evident ingest, and the DAO + Wallet layer manages provenance, entitlements, and treasury. Every business unit is a client of these three.
tenza-projects + Meow MCP
Bridges AI agents to the canonical project state. Every Coach run, Coop Matcher overlay, and post-PDD agent reads through the MCP layer rather than poking meta directly — same context shape for AI as for the dashboard.
class-mcp-server.php, guarded fallback)mwai_mcp_tools (Meow plugin)decentralised ingest · verification mesh
Today: TenzaOne's manual + AI-extracted ingest pipeline carries PDDs, monitoring docs, and registry feeds. Phase 3+: full DePIN sensor mesh with edge compute and proof-of-presence anchors so MRV data is tamper-evident from sensor to chain.
depin-widget surface for capacity reportingtenza-wallet + treasury + marketplace
Unified provenance + entitlement layer. Every cert (project / assessment / cooperative / performance) is paired-entry-logged in the simulated TNZU treasury. DAO governance, treasury ops, soft-listing marketplace, and public portfolios all read from one ledger.
Owner registers project · uploads PDD
10-agent AI chain extracts canonical state
Readiness Coach + Coop Matcher run via MCP
Evidence chain + cert issuance + ledger entry
Marketplace soft-listings + DAO governance
Each business unit owns a domain — Climatenza (solar/thermal), Net0Link (HVAC), Future Units (Carbon Asset Futures, DePINaaS, MCP Enterprise) — and ships its own AI on top of TenzaOne shared services. The shared spine means every unit gets MCP, treasury, marketplace, and governance for free.
Solar Thermal AI · AMS-II.C / AMS-I.E / VT0001
The founding business unit. Real Climatenza projects (Colgate Sanand, Tata, etc.) are the live test bed for the AI assessment + Coach + Coop Matcher stack.
Building HVAC · Digital Twins · Scope-3 reporting
HVAC efficiency platform with the TARA AI engine and per-building digital twins. Onboarding pilots Phase 2.
Roadmap-12 expansions on top of the shared spine
Three planned units that extend TenzaOne's reach without expanding its core. All consume MCP, treasury, marketplace, and governance from the shared spine.
15+ AI agents in production across four lifecycle stages. Pre-PDD assessment turns raw uploads into canonical project state. Coach + Match runs continuously. Post-PDD agents prep the project for VVB review. Certification + DAO closes the loop.
Raw upload → canonical project state
Continuous: blocker analysis + peer matching
Prep for validation/verification body review
Issuance · cooperative formation · investment
Phase 1 brought the platform online with sim wallet, AI assessment, and marketplace. Phase 2 layered Coach, Coop Matcher, post-PDD agents, treasury ops, developer API, and the carbon-markets terminal. Phase 3+ adds chain anchoring, DePIN sensors, and the future-unit portfolio.
Core ecosystem online and battle-tested with real Climatenza projects.
tenza-projects CPT + 34 meta fieldsProject / Company / Stakeholder hubtenza-vcs-assessment plugin10-agent extraction · React 18 apptenza-wallet sim + treasuryTNZU · paired-entry ledger · 6 packagestenza-analytics dashboardMatomo PHP API · 5 tabs · 11 KPIsAI agents, post-PDD prep, financial overlays, partner onboarding.
Chain anchoring, DePIN sensor mesh, derivatives, multi-tenant MCP.