№ 07·0207 · AI Agent System3 min read · Section 2 of 5
7.2 The five MVP Agents
The five MVP Agents WCN ships first, each with its own scope, permissions, output log, and PoB attribution record.
Updated
7.2 · The five MVP Agents
Five MVP Agents, each a defined execution unit with its own scope and record.
WCN does not open with a single all-purpose Agent. It ships five MVP Agents, each a structured execution unit with its own position, its own permissions, and its own attribution record. A type is a governance object, not a chat persona: it fixes what an Agent may see, what it may do, and what record it must leave.
What this page doesDefines the five MVP Agents and what separates them
The fiveFounder Decision Support, Project Diligence, Outreach and Meeting Summary, Node Support, PoB Evidence Validator
You will learnEach Agent's scope, its permissions, and the record it leaves
The five MVP Agents
Founder Decision SupportA thinking partner for the founder. It structures options, surfaces trade-offs, and drafts reasoning for review. It frames decisions; it does not make them, and its output stays advisory until a person acts on it.
Project DiligenceA four-dimension first draft of project due diligence. It retrieves from permitted sources, fills the diligence checklist, and marks every claim with a source. Figures default to "to be verified"; it does not contact the project on its own.
Outreach and Meeting SummaryDraft outreach email plus meeting transcription and summary. It produces action items, owners, and follow-up drafts against a template. Nothing is sent automatically; the node reviews and sends by hand.
Node SupportAutomated node question-and-answer and FAQ. It answers from approved material and routes anything outside its scope to a person. It does not improvise policy or speak for the node.
PoB Evidence ValidatorA first-pass review of submitted evidence. It checks an evidence package against the required fields and flags gaps for the Proof Ledger. It pre-screens and sorts; it never finalizes a PoB record.
Why each Agent is a separate unit
A single all-purpose Agent sharing one toolset breaks the principle of least privilege. Separating the five lets the system fix, for each one, what it may see, what it may do, and what it must record.
What each may seeProject Diligence reads a wide set of materials; Node Support reads approved FAQ content; the PoB Evidence Validator reads only the submitted package and the required fields.
What each may doOutreach and Meeting Summary drafts notes and emails; Node Support answers within approved material. No Agent may move funds or sign on its own.
What each must logProject Diligence records its query and the retrieved fragment; Outreach records the source meeting and timestamp; the Validator records which fields it checked and what it flagged.
How each reaches PoBAttribution templates differ by Agent, so an adopted diligence draft and an adopted outreach note carry different Proof fields and do not collide at settlement.
The expansion schedule
The five MVP Agents are the starting set, not the ceiling. The whitepaper sets a phased path: the cluster grows to ten Agents in Phase 1, twenty-five in Phase 2, and forty mature Agents in Phase 3.
Each new Agent enters the same way as the first five: a defined position, a scoped permission set, an output log, and an attribution record. Growth adds units to the cluster; it does not loosen the boundary.
The resident management cluster
Beneath the MVP Agents, WCN's own operation runs on the founder plus eight resident Agents. One acts as conductor, six cover the pillar domains of legal, capital, network, knowledge, brand, and operations, and two are cross-cutting: one maintains the base layer, one handles audit.
Each resident Agent carries one forbidden act and one always-true ledger assertion. The capital Agent never moves funds; the brand Agent never publishes without authorization. The pattern is the same as the MVP Agents: a fixed scope, a fixed limit, and a record that holds.
Without separation, permissions widen, logs cannot be defended, and a PoB record cannot be priced. The type of an Agent is a precondition for governance and settlement, not a label.
One event, several Agents
Project Diligence
Reads public financing news and the internal memo, then produces a list of conflict points and open questions.
Founder Decision Support
Structures the trade-offs from that list and drafts the reasoning for the next round of discussion, for the founder to review.
Outreach and Meeting Summary
Writes the meeting conclusion as action items with owners and due dates, and attaches them to the task.
PoB Evidence Validator
Checks the resulting evidence package against the required fields and flags any gap before the Proof Ledger reviews it.
The point of separating the Agents is to answer one question when something goes wrong: was it the model, the tools, the configuration, or the human adoption. A boundary can be drawn only once the work is split.
