OPC Global AI-Native Web App Instruction

Document status

This file is the implementation and governance source of truth for the OPC Global homepage and stakeholder onboarding experience. The canonical TABLE AI × OPC Global blueprint is preserved in full after this instruction layer.

• Source blueprint: user-provided pasted-text.txt, 1,195 lines and 55,328 bytes
• OPC Global brand source: https://apuch.art/api/brands/opcglobal.json
• Brand directory manifest: https://apuch.art/api/manifest.json
• Pinned brand version: 735ff5e, published 2026-07-24
• Pinned asset checksums:
  • hero: 8351935e9abc74b963309f2ec5677f22a9eaf4998c0e0cb59ecd55be42e4fe40
  • vector logo: b58c3be7390a1b625de8ad7d5c953fe8b95d1467692977c338c9b255f266502c
  • primary blue logo: c970696e04ab2859dd66c7b85c2c1b461d06ede4e2d65ec6a97d9c11db1396b3
• Brand caveat: the published record is marked placeholder and has no primaryGuide. The tokens and assets are official. Typography, layout, component, motion, and interaction rules below are product-system extensions.

Product objective

Build three coordinated layers:

1. This complete instruction and governance record.
2. A concise bilingual public homepage that explains the task-value operating system without reproducing every policy table.
3. A bilingual, role-based onboarding prototype for all public and operational stakeholders.
4. A public standards center and versioned API/MCP registry that expose the canonical blueprint, controlled terminology, TaskSpecs, roles, policies, and source provenance without creating a second source of truth.

The experience must make the operating model understandable, auditable, and actionable while never accepting identity documents, payment credentials, confidential customer material, real KYC information, or regulated data.

Implementation baseline

• Sites-compatible React and Next-style routing through vinext.
• Tailwind CSS v4 for token integration, with scoped product CSS for the editorial layout and state system.
• Server-rendered content by default; client code is isolated to onboarding state, validation, confirmation, and device-local persistence.
• One optimized local derivative of the checksum-verified official hero is used for page performance. The untouched official source remains archived beside it.
• Exactly one branded social preview is approved for this release: public/og.png, SHA-256 bf3cc07f9597550af2830b217d7c3cc126d44a53a5d6791ccc10baacdb9d8d13.
• The site remains useful with JavaScript delayed and the copilot remains useful without a remote model provider.

Experience architecture

Routes

• / redirects to /zh
• /en and /zh are localized homepages
• /en/standards and /zh/standards render the complete canonical blueprint
• /en/developers and /zh/developers document the public API and MCP boundary
• /en/onboarding and /zh/onboarding are stakeholder selectors
• /[locale]/onboarding/[role] contains each guided role journey
• Locale switching preserves the current route and device-local progress

Public stakeholder roles

Role key	English name	Chinese name	Primary onboarding outcome
buyer	Organization / Buyer	企业与机构需求方	A structured need, outcome, data grade, timing, budget band, and acceptance owner
expert	Expert / Standard Owner	专家与标准所有者	Domain evidence, standard or IP scope, review role, and availability
coach	Coach / Work-package Lead	教练与工作包负责人	Delivery leadership, task decomposition, mentoring, quality responsibility, and OPC level
contributor	Contributor / OPC Unit	贡献者与 OPC 单元	Skills, task evidence, readiness, availability, data eligibility, and growth path
ecosystem-partner	Ecosystem Partner	生态合作伙伴	Regional-node or task-factory scope, territory, local capability, and delivery network

Operational stakeholder roles

Role key	English name	Chinese name	Primary onboarding outcome
task-architect	Task Architect	任务架构师	TaskGraph, TaskSpec, dependency, effort, acceptance, and split-design readiness
quality-reviewer	Independent Quality Reviewer	独立质量审查人	Rubric, independence, conflict, evidence, and review-timing readiness
compliance-lead	Data & Compliance Lead	数据与合规负责人	Data classification, regional controls, access, retention, and escalation readiness
settlement-lead	Settlement & ValueLedger Lead	分账与结算负责人	SplitRule, ledger, release, exception, and audit readiness

Homepage narrative

The homepage must present these ideas in this order:

1. Turn real demand into work that can be accepted and settled.
2. Define outcomes, design tasks, assemble delivery, verify evidence, settle transparently, and reuse what works.
3. TABLE AI, OPC Global, shared infrastructure, regional nodes, and task factories.
4. The five public role entry paths.
5. TaskSpec, evidence-based acceptance, transparent SplitRules, explainable matching, data classification, and dispute rights.
6. The three initial task factories.
7. Verified Settled Value as the operating north-star definition.
8. Transparent service fees and contribution rights.
9. A single clear route into onboarding.

Never present the expansion gates, the 0.5 / 3 / 2 model, or any target as an achieved result. Do not use fake customer logos, fabricated proof, invented performance data, or “zero platform fee” claims.

Brand and UI system

Official theme tokens

Semantic token	Value	Usage
Primary	#1D3557	Navigation, primary actions, headings, structural emphasis
Accent	#B79B63	Verified value, selected states, limited highlights
Secondary	#A23E3E	Critical risks and errors only
Surface	#F3F5F6	Page and grouped section background
Paper	#FFFFFF	Elevated or input surfaces
Ink	#162130	Primary text
Muted	#596776	Secondary text
Line	rgba(29, 53, 87, 0.16)	Dividers and control borders

Product-system extensions

• Light theme only for this release.
• Geist Sans with Noto Sans SC and system fallbacks; Geist Mono for IDs, formulas, and ledger values.
• One 12px corner-radius scale.
• Phosphor icons with a consistent weight.
• DESIGN_VARIANCE: 5, MOTION_INTENSITY: 3, VISUAL_DENSITY: 4.
• Motion must communicate hierarchy, progress, feedback, or state change.
• All automatic movement must respect prefers-reduced-motion.
• Avoid generic AI-purple gradients, neon glows, excessive glass, invented SVG illustration, equal three-card grids, and fake product screenshots.
• Use the official global-network hero image and official logo assets.

Localization rules

• Chinese is the default locale. English is available without resetting route or onboarding state.
• All navigation, content, roles, form labels, validation, copilot output, privacy guidance, and next steps must exist in both languages.
• Locale switching changes presentation only. It must not reset answers.
• Identifiers such as TaskSpec, TaskGraph, VSV, SplitRule, and ValueLedger remain stable across locales and receive a translated explanation.

Structured onboarding copilot

The copilot is not an open-ended chat surface. It is a deterministic, provider-neutral guidance layer over the typed onboarding state.

Allowed behaviors:

• recommend or confirm a role;
• identify missing non-sensitive information;
• calculate a readiness state;
• identify policy or data risks;
• propose the next preparation action;
• cite the relevant blueprint section.

Required behaviors:

• clearly label recommendations as proposals;
• keep the user in control of confirmation;
• work when AI services are unavailable;
• save only non-sensitive state in browser storage;
• provide a reset action;
• never issue credentials, release money, alter SplitRules, complete KYC, or submit a final production application.

Public interfaces

type Locale = "en" | "zh";

type PublicRole =
  | "buyer"
  | "expert"
  | "coach"
  | "contributor"
  | "ecosystem-partner";

type OperationalRole =
  | "task-architect"
  | "quality-reviewer"
  | "compliance-lead"
  | "settlement-lead";

type Role = PublicRole | OperationalRole;

interface OnboardingState {
  schemaVersion: 1;
  role: Role;
  answers: Record<string, string | string[] | boolean>;
  evidenceRefs: string[];
  currentStep: 0 | 1 | 2;
  readiness: "starting" | "building" | "ready";
  riskFlags: string[];
  nextActions: string[];
  confirmations: string[];
  lastSavedAt: string;
}

interface AIRecommendation {
  summary: string;
  suggestedRole: Role;
  missingInformation: string[];
  riskFlags: string[];
  blueprintCitations: string[];
  confidence: "low" | "medium" | "high";
  confirmationRequired: true;
}

interface BrandSnapshot {
  brandSlug: "opcglobal";
  status: string;
  sourceVersion: string;
  synchronizedAt: string;
  tokens: Record<string, string | string[]>;
  assets: Array<{
    id: string;
    filename: string;
    sha256: string;
  }>;
}

interface StandardsManifest {
  schemaVersion: string;
  contentVersion: string;
  sourceCommit?: string;
  instructionSha256: string;
  blueprintSha256: string;
  canonicalLanguage: "zh";
}

interface TermDefinition {
  id: string;
  canonicalZh: string;
  canonicalEn: string;
  aliases: string[];
  definitionZh: string;
  definitionEn: string;
  sectionId: string;
}

MCP boundary

Use apuch.art’s published get_brand, list_assets, get_asset, and request_asset_url capabilities through the brand-sync adapter, with its public brand JSON as the deterministic fallback.

Published OPC resources:

• opc://manifest/current
• opc://glossary/current
• opc://standards/{sectionId}
• opc://roles/{role}
• opc://taskspec/{taskCode}
• opc://policy/{policyId}
• opc://brand/current

Permitted read or draft tools:

• resolve_term
• validate_standard_reference
• validate_taskspec
• compare_standard_versions
• draft_alignment_report
• recommend_role
• draft_onboarding_profile
• assess_readiness
• propose_task_path

Do not expose autonomous payment release, credential issuance, SplitRule modification, or final onboarding submission. Remote MCP uses stable protocol version 2025-11-25 over stateless Streamable HTTP and may negotiate future versions only after they become stable. The 2026-07-28 revision is an RC at the time of implementation and must not be a first-release dependency. Protocol status must be rechecked against the official MCP releases.

The build-time brand adapter should attempt the published MCP tools first and fall back to public brand JSON without weakening checksum validation. Runtime AI integration must sit behind a provider-neutral adapter. Every future model-assisted provenance event records the model, prompt or Skill version, tool calls, source data, output proposal, and explicit human confirmation.

Accessibility and performance

• WCAG AA contrast for all text and controls.
• Visible keyboard focus on all interactive elements.
• Labels above inputs; helper text optional; errors below inputs.
• No placeholder-only labels.
• Explicit loading, empty, validation, completion, recovery, and reset states.
• Explicit mobile layouts at 375px, 768px, 1024px, and 1440px.
• Hero image dimensions must be reserved to prevent layout shift.
• Target LCP below 2.5 seconds, INP below 200ms, and CLS below 0.1.
• Honor reduced motion and avoid scroll listeners tied to React state.

Traceability matrix

Blueprint section	Homepage	Onboarding	Future product module	Governance / policy
一、核心结论	Hero and value loop	All role introductions	Command Center	Platform charter
二、愿景、使命与战略定位	Mission and VSV	All role purpose statements	KPI layer	Strategy charter
三、TABLE AI 与 OPC Global 的角色分工	Operating network	Ecosystem partner	Organization and permissions	Brand and operating model
四、从职业目录转向任务图谱	TaskGraph explanation	Role and skill matching	TaskGraph / SkillGraph	Classification standard
五、任务层级与最小交易颗粒度	Value-loop detail	Buyer and task architect	TaskGraph	Task granularity policy
六、标准任务卡 TaskSpec	Trust architecture	Buyer and task architect	TaskSpec library	Task standard
七、第一批标准任务目录	Task-factory examples	Relevant role examples	Standard task market	Versioned catalog
八、价值交付标准	Evidence and quality	Buyer and reviewer	Quality Engine	Acceptance policy
九、工作量、报价与价值分离	Transparent commercial model	Buyer and settlement lead	Quote Engine	Pricing policy
十、智能分账	Transparent contribution rights	Settlement lead	ValueLedger	Split and asset policy
十一、Demand Radar	Task-factory context	Buyer and ecosystem partner	Need Studio / Demand Radar	Opportunity scoring
十二、AI时代新岗位	Role entry paths	Expert, coach, contributor	TalentGraph	Role formation standard
十三、OPC UNI	Paid growth	Coach and contributor	OPC UNI	Credential policy
十四、人才匹配与信誉体系	Explainable matching	Delivery roles	Match Engine	Appeal and reputation policy
十五、交付、验收与争议机制	Trust architecture	Buyer, coach, reviewer	Workroom / Quality Engine	Dispute policy
十六、产品系统架构	Shared infrastructure	Operational roles	All named modules	Technical governance
十七、全球化架构	Regional network	Ecosystem partner and compliance	Trust & Compliance	Regional and data policy
十八、商业模式	Transparent service model	Buyer and partner	Quote / Billing	Commercial policy
十九、首期三个任务工厂	Task-factory section	Buyer and partner	Vertical task factories	Launch focus
二十、90天落地计划	Not presented as achievement	Next-step guidance	Delivery roadmap	Program governance
二十一、扩张闸门	Labeled validation criteria	Operational readiness	Command Center	Expansion policy
二十二、管理指标体系	VSV and hypothesis framing	Role readiness metrics	Analytics	Measurement standard
二十三、最容易失败的十个地方	Trust safeguards	Prohibited actions	Risk monitoring	Risk register
最终战略表达	Final CTA	Completion summary	Product narrative	Strategy charter

Acceptance checks

• The canonical blueprint below retains all source headings, tables, task codes, formulas, benchmarks, gates, and risk items.
• Every role has complete English and Chinese content.
• Every role page includes purpose, responsibilities, prerequisites, evidence, prohibited actions, readiness, next actions, and blueprint citations.
• Brand assets match the recorded SHA-256 checksums.
• No visible website copy contains an em dash.
• No production-only or sensitive action is presented as operational.
• All routes build and render without client-side errors.

---

Canonical TABLE AI × OPC Global Blueprint

Unified organization, identity, and settlement module extension

This release extends the public task-value system with a protected operations workspace. The formula migration source is ref/经营与分账模型v3.html, pinned at SHA-256 76ca4c88c9c1778f1842a1c03de2a74d38ab2a6d68b7de2116266a4cba740d79. The source is an operating forecast calculator, not an accounting ledger. Its examples become golden tests, while production rules add versioning, participants, idempotency, integer rounding, approval, reversal, disputes, and append-only provenance.

Identity, organization, and rights holders

• TableUser Hosted OIDC is the authentication authority. Natural persons use taid as the only stable cross-system key; Logto sub, email, and username must never become business foreign keys.
• An Organization is a collaboration and authorization space. Each Split Project belongs to one Organization and may involve several Legal Entities.
• Every Settlement Basis Line belongs to exactly one Legal Entity. Each entity calculates, approves, and posts to an independent subledger; project-level views aggregate but never merge entity funds implicitly.
• A Party is either a natural person bound to TAID or a verified Legal Entity. Each Party has one global Split Account. ledger_ready is not payout_ready.
• External invitees become Project Participants only. They do not become Organization members. Invitations use single-use, revocable, hashed tokens, expire after seven days by default, and require reissue when the signed-in email differs.

TableUser is the resource-authorization authority and flay01 stores a versioned projection only. Formal writes call TableUser in real time and fail closed when the service is unavailable. Resource grants cover organization, legal_entity, split_project, and equity_ledger; role names are: platform:admin, opc:org:owner, opc:org:admin, opc:settlement:approver, opc:equity:admin, opc:project:admin|editor|viewer, opc:project:participant, and opc:auditor.

Platform administrators can provision, suspend, troubleshoot, and draft but cannot alone approve an Organization payable ledger. Organization admins can create projects, publish rules, invite participants, and prepare settlements. An Organization owner or settlement approver approves formal payables. An Organization with only one active approver may self-approve below its own future-effective limit.

Separate planning and settlement contexts

OperatingPlan models services, customers, revenue cycles, collection, refunds, and cost forecasts; all output is advisory. Settlement consumes only confirmed actual amounts with source evidence. Forecast refund or collection rates can never create or alter a payable obligation.

The first immutable template is OperatingFourPoolV3@1:

1. Aggregate confirmed revenue or an approved cash basis for one Legal Entity.
2. A cash basis first protects all unearned revenue and refund exposure.
3. Deduct actual refunds, bad debt, tax, direct cost, and explicit platform fees.
4. Calculate positive gross margin and reserve; a loss becomes an entity deficit and never a participant negative payable.
5. Allocate acquisition, delivery, product, and platform pools whose ratios sum to exactly 100%.
6. Acquisition rights decay to 50% in cooperation year two and 20% from year three; the remainder reflows to the platform pool.
7. Product rights expire at the earlier of three years after first delivery or cumulative allocation equal to five times research investment.
8. Apply salary-advance offsets, external tax treatment, fixed costs, loan repayment, and the explicit platform waterfall.
9. External-member eligibility is controlled by the Rule Version, never by an internal/external hard-coded distinction.
10. Normalize participant weights independently within each pool.

Money uses ISO 4217 currency and integer minor units. Rates use exact decimal representation. Largest-remainder allocation guarantees conservation, with stable Party ID as the tie-breaker. Refunds and losses never generate automatic debt; future offsets require a pre-existing, accepted, disputable rule.

Rule, FX, review, and ledger lifecycle

Reference FX initially uses ECB daily reference rates and deterministic EUR triangulation. The UI must label it as a reference rate, not an execution rate. Weekend or holiday dates use the latest published rate not later than the reference date. A system admin or Organization admin may create a manual override for an unapproved run only, with reason, evidence, difference, impact scope, and participant notice. A run freezes raw response, source date, pair, hash, and override; history never recalculates with a current rate.

Rule versions follow draft → published → active → superseded. They affect future periods only. New and impacted participants must accept the current version before entering a new period. Historical rules, calculation snapshots, and approved ledgers are immutable.

Settlement runs follow draft → calculated → participant_review → ready_for_approval → approved. Participant review lasts five business days. A disputed line freezes while undisputed lines continue; expiry records no objection rather than fabricated approval. Approved runs cannot be edited. Corrections create an AdjustmentRun with linked reversal or adjustment entries.

Operational equity ledger

Each eligible Legal Entity may have one append-only operational equity ledger covering classes, holders, units, subscribed and paid amounts, option pools, vesting, issue, transfer, cancellation, repurchase, and adjustment events. Derived balances are never overwritten directly. Internal approval may affect operating rights and profit allocation but always shows legalRegistrationStatus. Mainland China and Hong Kong have separate jurisdiction profiles; all other jurisdictions are read-only in this release. The module is off by default and opens only after an initial holding snapshot is reconciled. It does not replace a statutory shareholder register, legal filing, or legal transfer instrument.

REST and MCP contract

REST formal writes require a TableUser OIDC JWT or M2M token, a resource grant, Idempotency-Key, and If-Match for versioned updates. Responses return the resource version, audit event ID, and input/calculation hashes.

MCP resources include:

• opc://organizations/{id}
• opc://split-templates/{version}
• opc://split-projects/{id}
• opc://settlement-runs/{id}
• opc://equity-ledgers/{legalEntityId}

MCP tools are limited to read and draft operations: simulate_operating_plan, draft_split_project, validate_split_rule, calculate_draft_settlement, explain_settlement, compare_rule_versions, and draft_invitation. MCP must never publish a rule, override FX, approve a ledger, post equity events, submit final onboarding, or execute payment. Every AI or MCP proposal records model, prompt or Skill version, tool calls, source data, and human confirmation in provenance events.

Data, deployment, and explicit exclusions

Production data remains in Tencent Cloud Nanjing. The target data plane is PostgreSQL 16 with separate flay01_core and tableuser_authz databases, separate runtime and migration roles, TLS, encryption at rest, automated backups, and at least fourteen days of point-in-time recovery. Postgres outbox workers process calculations, email, and notifications without adding Redis. The private Sites deployment is a sanitized UI review plane and never connects to the production ledger.

The pilot capacity target is 100 Organizations, 100 participants per project, and 5,000 lines per run; calculation p95 is under five seconds and in-Organization authorization p95 is under 200ms. Large ledgers use server pagination.

This release does not execute payment, collect identity documents, bank credentials, KYC material, confidential customer uploads, issue credentials, perform tax filing or withholding, provide an arbitrary formula designer, automatically pursue debt, or claim that a UI action completes a legal equity transfer.

TABLE AI × OPC Global 全球透明任务协作与智能分账体系蓝图

1. Core conclusion

What you really want to build is a "global mission value operating system":

Break down the real needs of enterprises and institutions into tradable tasks, encapsulate expert wisdom into standards and assets, form a temporary delivery team of people and agents, use evidence for acceptance, and use rules to divide accounts, so that each delivery can simultaneously generate revenue, capability certificates, reputation records, and reusable assets.

The platform takes "verified task results" as the smallest unit:

• Transaction unit: Accepted task results
• Training unit: Capacity increment with real evidence
• Accounting unit: contribution agreed in advance and auditable afterwards
• Reputation unit: historical performance on a specific task
• Asset units: methods, templates, data structures, courses, and agent components that can be authorized for reuse
• Core barriers: task map, capability map, delivery data, reputation network, professional asset library and transnational compliance nodes

The entire closed loop can be summarized as:

真实需求 → 结果定义 → 任务图谱 → 人机协作 → 证据验收 → 透明分账 → 能力认证 → 资产复用 → 持续收益

The most powerful set of platform principles are:

Tasks are courses, orders are training grounds, delivery is certification, contributions are rights and interests, and reuse is dividends.

This is highly consistent with the triangular collaboration of "industry experts-coaching partners-OPC units" that OPC Global has formed, and also follows TABLE AI's direction of "connecting expert wisdom with the real needs of enterprises". OPC Global official website, TABLE AI official website

---

真实需求 → 结果定义 → 任务图谱 → 人机协作 → 证据验收 → 透明分账 → 能力认证 → 资产复用 → 持续收益

2. Vision, mission and strategic positioning

1. Mission

** Cultivate new positions in the AI era and bridge the gap between global professional wisdom, data and practical results. **

The mission needs to fall specifically into four things:

1. Transform tacit experience into executable task standards, intelligence, and professional assets.
2. Convert real orders into paid learning and career growth opportunities.
3. Allow talents from different countries, languages, and industries around the world to collaborate transparently.
4. Allow every real contribution to be recorded, verified, settled and reused in the long term.

2. Vision

**Become the world's largest network of transnational transparent task collaboration, practical talent training and value distribution. **

So that any real demand can be converted into:

• Clear results;
• Calculable workload;
• Matchable capabilities;
• Executable tasks;
• Verifiable quality; *Traceable funds;
• Portable competency credentials;
• Professional assets with sustainable returns.

3. Platform positioning

**A valuable collaboration infrastructure for global professional wisdom and practical talents in the AI era. **

This definition is more complete than "freelance platform", "expert platform", "training platform" and "account sharing platform". All of the above forms can become one of the modules.

4. Measurement of “World’s Largest”

Registration numbers should not be the main metric. "World's largest" needs to be defined with six results:

Dimensions	Core indicators
Real demand	Annual effective demand quantity, number of paying companies, repurchase rate
Delivery scale	Annual number of accepted tasks and total accepted value
Talent growth	Number of people earning real income, ability promotion rate, income growth
Cross-border collaboration	Proportion of cross-border tasks, number of languages covered and compliance areas
Trust quality	First-time acceptance rate, punctuality rate, dispute rate, settlement time
Asset accumulation	Number of reusable assets, reuse rate, asset licensing income

It is recommended that the North Star indicator be set as:

**The total value that has been accepted and settled in the year: Verified Settled Value, VSV. **

VSV also excludes false demands, unfinished orders, unaccepted results and unaccounted flow.

---

3. Division of roles between TABLE AI and OPC Global

System	Core Positioning	Main Responsibilities
TABLE AI	Enterprise requirements and intelligent delivery engine	Enterprise modeling, demand diagnosis, task disassembly, agent orchestration, delivery management, quality assessment, enterprise workbench
OPC Global	Global Talent, Education and Governance Network	Recruitment of experts, coaches, and OPC units; paid practice; competency certification; community governance; regional nodes
Common middle platform	Mission and value infrastructure	TaskGraph, SkillGraph, ValueLedger, AssetGraph, reputation and credentials
Table AI HK	Initial cross-border arrangement and settlement entity	Responsible for main contract, international project arrangement and settlement coordination within actual qualifications and contract scope
Regional Cooperation Node	Local Compliance and Delivery Node	Local Contracts, Tax, Payments, Data, Languages, Customer Service and Dispute Handling
Industry task factory	Vertical demand sources	Enterprise AI transformation, education and training, cultural tourism hotels, catering, research, scientific research communication, etc.

The existing "Triangular Collaboration·Liquid Delivery Network" is suitable as a front-end organizational narrative:

• Industry experts: definitional meaning, professional judgment and quality standards;
• Coaching partner: break down tasks, lead delivery, and cultivate talents;
• OPC Unit: Perform real tasks, earn income and grow in capabilities.

There are four types of roles that need to be completed in the background:

• Mission architect;
• Independent quality reviewer;
• Head of data and compliance;
• Person in charge of accounting and settlement.

A brand statement that needs to be corrected

The official website of OPC Global currently states that "individuals directly own all output value, no longer receive commissions from the platform, and 100% of the value belongs to themselves." This conflicts with the real costs of platform infrastructure, customer acquisition, quality inspection, payment, compliance and dispute handling in the future. OPC Global official website

It is recommended to change to:

The destination of each value is transparent; contributors retain verifiable contribution rights; the platform charges fees that match the actual services in accordance with public rules.

"100% value belongs to you" can be used to express:

• Individuals have their own ability records;
• Individuals own intellectual property rights within the agreed scope;
• Individuals can bring their own mission resume and certification;
• The platform does not deprive contribution rights through black box algorithms.

It should not be construed to mean that the platform will always charge zero fees.

---

4. Underlying Method: From Occupational Catalog to Task Map

The labor market is shifting from "one person corresponds to a fixed position" to "skills are combined to perform different tasks." Autor's "task approach" directly studies how skills are configured to tasks; modularity theory emphasizes that complex systems require defined components, interfaces, dependencies, and test standards. [NBER "The Task Approach to Labor Markets"] (https://www.nber.org/papers/w18711), [Harvard Business School's research on system architecture and modularization] (https://www.hbs.edu/ris/Publication%20Files/15-028_ec57f2ea-890d-4243-b9f3-60784359bab9.pdf)

Therefore, the platform should adopt:

**A stable main tree + multi-dimensional labels + task relationship map. **

A single classification tree cannot simultaneously express the industry, skills, outcomes, complexity, data risk, language, and business model.

1. Main Category: Services and Task Areas

Code	Level 1 Task Area	Typical Content
STR	Strategy, Research and Consulting	Market research, positioning, business model, decision-making report, feasibility study
MOD	Enterprise and Business Modeling	Organization, process, metrics, data, decision-making, business semantic modeling
AIA	Agents, data and software	Agent design, knowledge base, evaluation, MCP/API, automation
DES	Brand, design and content	Brand, PPT, report, website, visual, article, video
EDU	Curriculum, training and talent development	Curriculum development, cases, assessment, lecturer training, training
EXP	Expert knowledge and knowledge assets	Expert interviews, methodology extraction, digital clones, knowledge products
EVT	Events, study tours and incentive travel	Conferences, study tours, corporate visits, incentive travel, on-site operations
SCI	Science popularization and scientific research transformation	Literature research, science popularization content, scientific research dissemination, and achievement transformation
GRO	Marketing, Growth & Sales	Customer Research, Leads, Marketing Content, Sales Tools, Private Domain
GLB	Internationalization and localization	Market entry, translation, localization, partner development, overseas expansion
OPS	Operations and project support	Project management, procurement, scheduling, customer service, data and process operations
QCG	Quality, Compliance and Governance	Acceptance, Review, Data Security, Intellectual Property, Dispute Resolution

Industry cannot blend into this master tree. Industry as a separate label:

• Education;
• Hotels and cultural tourism;
• Catering; *Manufacturing;
• Medical health;
• Scientific research;
• Government and public services;
• Finance; *Consumer goods;
• Cross-border e-commerce, etc.

2. Classification dimensions that must exist at the same time

Dimensions	Suggested categories
Demand maturity	Long-term rigid demand, structural growth, emerging demand, experimental demand
Value chain stages	Discover, define, design, develop, test, deliver, operate, optimize, govern
Basic actions	Research, interview, analysis, modeling, design, creation, configuration, development, testing, teaching, coordination, review
Outcome type	Report, data set, model, code, agent, course, design draft, SOP, activity, decision memo
Work level	E0 actions, E1 microtasks, E2 atomic tasks, E3 work packages, E4 milestones, E5 projects
Complexity	C1 Repeated Standard, C2 Conventional, C3 Multi-Source Complex, C4 Highly Ambiguous, C5 Strategic or High Risk
Responsibility levels	R1 follows, R2 assists, R3 executes independently, R4 is responsible, R5 coordinates, R6 structures, R7 defines standards
Human-machine approach	Human-led, AI-assisted, human-machine cooperation, intelligent agent performs manual review and automatic execution
Collaboration methods	Direct assignment, candidate bidding, competition, fixed team, temporary team, open collaboration
Data Levels	P0 Public, P1 Internal, P2 Confidential, P3 Regulated or Locally Processed
Rights model	Entrusted buyout, limited authorization, common assets, platform assets, open source assets
Business model	Fixed price, quantity unit price, milestone, subscription, residency, reward, authorization, result bonus
Language and Region	Working Language, Delivery Language, Time Zone, Service Countries, Applicable Laws
Competency requirements	Professional skills, industry knowledge, tools, languages, responsibility levels, certifications

O*NET has broken down occupations into knowledge, abilities, activities and specific tasks; ESCO provides multi-lingual occupation-skill relationships; SFIA uses professional skills and seven levels of responsibility to jointly define competencies. You can use these standards as external mappings while retaining your own task classification. O*NET Content Model, ESCO Classification System, SFIA Responsibility Level

---

5. Task level and minimum transaction granularity

Level	Definition	Typical cycle	Whether to separate accounts separately
Need Need	The business status that the customer wants to change	Continuous	No
Solution Solution	Overall path to meet needs	2-16 weeks	No
Project	Delivery unit with contract, budget and overall leader	2-16 weeks	Yes
Milestone Milestone	Stage results that can be independently accepted and paid for	1-4 weeks	Yes
Work Package	A set of highly related tasks	1-5 days	Yes
Atomic Task	One person in charge, one main result, one acceptance	2-12 hours	Yes
Action Action	Search, clean, label, check and other steps	5-60 minutes	Separate accounts after batch
Evidence Evidence	Files, logs, tests, approvals, version records	Instant generation	No

A qualified atomic task must have:

1. A main person in charge;
2. A major result;
3. Clear input boundaries;
4. Clear definition of completion;
5. An independent acceptance judgment;
6. An independent budget and ledger record;
7. Clear dependencies;
8. Clear modification times and out-of-range conditions.

For example:

Excessively rough statement	Tradable tasks
Develop an agent	Establish 50 test cases and scoring criteria for the sales question and answer agent
Take a course	Complete a 90-minute course module, instructor manual, cases and 20 assessment questions
Conduct a study	Complete the itinerary structure, budget model, supplier inquiry and risk plan for a 40-person, 3-day project
Make a PPT	Complete the 20-page presentation visual system and editable final draft under the premise of freezing the content

---

6. Standard task card TaskSpec

Each standard task should have a unique, immutable TaskSpec ID, with categories and tags saved as separate fields. Avoid writing all semantics into numbers, as categories will continue to change.

Standard task card fields

Field group	Required fields
Identity	TaskSpec ID, name, version, status, standard owner, applicable language
Business results	Paying entities, usage scenarios, tasks to be completed, expected results, value levels
Scope	Inclusions, exclusions, quantities, objects, geographic scope, time range
Input	Required data, data format, minimum quality, latest provision time, data level
Output	Result name, format, quantity, granularity, editable source file, handover requirements
Execution	SOPs, tools, models, templates, manual checkpoints, prohibitions
Workload	Baseline effective hours, role hours, agent costs, external costs, complexity
Dependencies	Predecessor tasks, parallel tasks, downstream tasks, blocking conditions
Competencies	Skills, industry knowledge, level of responsibility, language, certifications, historical evidence
Acceptance	Rating form, hard threshold, sampling method, acceptance person, review time limit
Business	Base price, quotation method, number of modifications, payment nodes, and accounting rules
Rights	Background intellectual property rights, new achievement rights, reuse rights, signature, confidentiality period
Cultivation	Prerequisite courses, simulation tasks, coaching requirements, obtainable credentials
Assetization	Whether it can be reused, scope of asset extraction, maintenance responsibilities, future authorization sharing
Risk	Data, compliance, copyright, model, geography, reputation, execution risk
Traceability	Task instance, personnel, agent version, prompt word/skill version, file version, approval log

---

7. The first batch of standard task catalogs V0.1

The following workloads are all baseline effective working hours with complete input, normal timeliness, and modifications within one round. It is used for cost measurement and internal accounting and is not directly equivalent to the sales price. Model calls, databases, software licenses, travel, venue, and vendor fees are listed separately.

1. Strategy, Research and Enterprise Modeling

Code and tasks	Baseline workload	Core acceptance
STR-01 Requirements and Decision Briefing	6-10 hours	Clarify decision makers, business issues, results, scope, constraints and success indicators
STR-02 Special topic evidence package	12-20 hours/topic	About 20 valid sources; time, source, conclusion and conflict information can be traced
STR-03 Stakeholder interviews	4-6 hours/person	Complete interview outline, 60-minute interview, minutes, insights, and questions to be verified
STR-04 Benchmarking case files	6-10 hours/case	Use unified dimensions; separate facts, judgments, reference points and applicable boundaries
STR-05 Decision Memo	12-20 hours	Provide options, standards, comparisons, suggestions, risks and next steps
MOD-01 Business process modeling	16-28 hours/process	Current situation, goals, roles, data, control points, breakpoints and responsibilities complete
MOD-02 Dictionary of indicator caliber	16-28 hours/20 items	Complete definitions, formulas, granularity, sources, responsible persons, exceptions and test samples
STR-06 Two-hour workshop	16-24 hours	Plan, materials, hosting, discussion records, conclusion, responsible person and deadline
STR-07 Solution and SOW	16-28 hours	Scope, task map, milestones, responsibilities of both parties, acceptance, price and change rules complete

2. Agents, data and software

Code and tasks	Baseline workload	Core acceptance
AIA-01 AI scenario readiness assessment	12-20 hours	Value, process, data, risk, integration and personnel readiness completion score
AIA-02 Intelligent Product Requirement Document	20-32 hours	Complete roles, goals, boundaries, tools, status, exceptions, permissions and indicators
AIA-03 Prompt/Skill prototype	12-24 hours/workflow	Versioning instructions, at least 20 test samples, failure conditions and manual takeover rules
AIA-04 Knowledge base processing package	12-24 hours/100 pages of qualified documents	Classification, segmentation, metadata, deduplication, citation and sampling inspection completed
AIA-05 agent evaluation set	24-40 hours/50 cases	Complete routine, edge, refusal, and safety cases; expected results and scoring rules are clear
AIA-06 MCP/API connector	24-60 hours/interface	Authentication, Schema, exception retries, logs, tests and interface documents passed
AIA-07 single-process agent prototype	40-80 hours	The sandbox is runnable, the demonstration path is complete, the core evaluation is passed, and the problem list is clear
AIA-08 Production deployment work package	80-200 hours	Complete permissions, security, monitoring, rollback, operation and maintenance manual and acceptance environment
AIA-09 Security and Privacy Review	16-32 hours/system	Data flow, permissions, prompt injection, leakage, manual supervision and trace completion inspection
AIA-10 Monthly Optimization Sprint	16-32 hours/month	Error classification, improvement records, regression testing and traceability of indicator changes

3. Brand, design and content

Code and tasks	Baseline workload	Core acceptance
DES-01 Creative and Design Brief	6-10 hours	Audience, scene, information level, visual direction, restricted areas and delivery specifications are clear
DES-02 Presentation/Report Visual System	12-20 hours	Complete fonts, colors, grids, charts, covers, chapter pages and masters
DES-03 20-page presentation design	24-40 hours	Content frozen; logical hierarchy clear; data correct; editable source files complete
DES-04 30-page report layout	24-40 hours	Unified table of contents, title level, tables, diagrams, page numbers and printing layout
DES-05 Single-page website UX/UI	32-56 hours	Complete information architecture, desktop/mobile terminal, component status and development annotation
DES-06 Main visual design	12-20 hours	Two directions, one to deepen the final draft, adapted size and complete source files
CNT-01 Professional article	10-18 hours/2000-3000 words	Facts, structure, tone, quotation and action value passed review
CNT-02 short video script	8-14 hours/5-8 minutes	Complete oral broadcast, lens, rhythm, material, subtitles and action guidance

4. Curriculum, training and talent development| Code and tasks | Baseline workload | Core acceptance |

| --------------- | ----------: | -------------------------- | | EDU-01 Learning needs analysis | 10-16 hours | Clear target groups, work tasks, ability gaps, behavioral results and measurement methods | | EDU-02 course system structure | 12-20 hours | Groups, levels, modules, pre-relationships, hours and assessments form a closed loop | | EDU-03 90-minute course module | 30-45 hours | 24-36 pages of courseware, instructor's manual, exercises, handouts and assessment complete | | EDU-04 case or sparring sandbox | 16-28 hours | Complete description of background, roles, data, tasks, branches, scoring and review | | EDU-05 course evaluation question bank | 10-18 hours/20 questions | The questions correspond to the goals; complete answers, analysis, difficulty and scoring rules | | EDU-06 Instructor Operation Manual | 8-14 hours/module | Complete time, lectures, interactions, FAQs, risks and backup plans | | EDU-07 course trial lecture and revision | 8-12 hours + trial lecture time | Actual duration, understanding, participation and completion record of question list | | EDU-08 training trainer | 16-24 hours preparation + teaching | Lecturers are assessed through knowledge, expression, field control and case exercises | | EDU-09 Formal teaching | Priced based on half day/full day | Attendance, process records, evaluation, feedback, action plan and review complete |

5. Study, incentive travel and activities

Code and tasks	Baseline workload	Core acceptance
EVT-01 Briefing on project goals and people	6-10 hours	Clear corporate goals, people, budget, time, experience and learning results
EVT-02 Destination Benchmarking File	8-12 hours/city	Transportation, resources, hospitality, prices, risks and seasonal suitability complete
EVT-03 Three-day project structure	16-24 hours	Each activity corresponds to a goal; rhythm, movement lines and learning logic are executable
EVT-04 Supplier inquiry and comparison	20-32 hours/5 categories of suppliers	At least three comparable quotes for each category; billing period, cancellation terms and validity period are clear
EVT-05 Three-scenario budget model	8-14 hours	Prudential, baseline, upgrade scenarios; complete taxes, service fees and reserves
EVT-06 Operation and safety assessment	10-18 hours	Complete traffic, weather, medical, insurance, personnel, data and emergency plans
EVT-07 40-person execution manual	16-28 hours	Minute-level processes, contacts, materials, dining cars, emergencies and clear permissions
EVT-08 On-site operation	1 general controller per day + 1 coordinator for every 20 people	Real-time records of logs, changes, accidents, expenses, attendance and customer confirmation
EVT-09 Project Evaluation Report	8-14 hours	Goal achievement, satisfaction, learning results, costs and improvement suggestions complete

6. Science popularization, scientific research dissemination and achievement transformation

Code and tasks	Baseline workload	Core acceptance
SCI-01 Briefing on popular science issues and audiences	4-8 hours	Clear scientific issues, audience awareness, communication goals and risk boundaries
SCI-02 Document Evidence Package	12-24 hours/15-25 articles	Complete document grade, conclusion, disagreement, timeliness and scope of application
SCI-03 Expert interview	5-8 hours/person	Complete outline, interview, fact confirmation, quotable content and controversial points
SCI-04 Long popular science article	12-20 hours/1500-2500 words	Scientific and accurate, understandable to ordinary readers, clear source, no exaggeration
SCI-05 Popular science infographic	12-20 hours	One picture, one conclusion; accurate values, units, sources and visual hierarchy
SCI-06 popular science video script	8-14 hours/5-8 minutes	Scientific conclusions, explanation sequence, lens and risk wording passed review
SCI-07 Independent fact-checking	4-8 hours/article	Each key claim has a source; errors, ambiguities and outdated information are marked

7. Internationalization and localization

Code and tasks	Baseline workload	Core acceptance
GLB-01 Single country market entry briefing	20-36 hours	Customer groups, channels, competition, prices, partners, compliance and complete entry paths
GLB-02 Professional localization	4-8 hours/1000 source language words	Terminology, culture, format, brand tone and local expressions passed native language review
GLB-03 Partner long list	16-28 hours/30 companies	Complete subjects, capabilities, regions, contacts, matching degree and information sources
GLB-04 Basic due diligence on partners	4-8 hours/subject	Complete verification of registration, equity, team, cases, risks and conflicts of interest
GLB-05 International Expansion Material Package	16-24 hours	Bilingual introduction, email, meeting outline, FAQ and complete follow-up process
GLB-06 Cross-cultural adaptation review	8-16 hours/results	Language, symbols, culture, legal risks and audience understanding completion check
GLB-07 Single country compliance requirements map	24-48 hours	Subject, contract, tax, data, employment, payment and licensing issues are complete; local professionals are responsible for final confirmation
GLB-08 Cross-border project coordination	8-16 hours/week	Time zones, responsibilities, risks, meetings, actions and decision-making records are continuously updated

8. Quality, Projects and Governance| Code and tasks | Baseline workload | Core acceptance |

| -------------- | -----------: | -------------------------- | | QCG-01 Special Acceptance Rating Form | 6-12 hours | Indicators, weights, hard thresholds, examples and scoring instructions are executable | | QCG-02 Independent quality review | 15%-25% of production working hours | Score with evidence; problem location, severity and modification requirements are clear | | OPS-01 Project coordination | 8%-15% of production hours | Complete traces of scope, scheduling, risks, decision-making, changes and communication | | QCG-03 Data and Privacy Classification | 6-12 hours/project | Clear data list, level, region, permissions, retention and deletion rules | | QCG-04 Review and capitalization | 8-16 hours/project | Reasons for success or failure, standard updates, templates, cases and asset rights completed registration | | QCG-05 Scope Change Order | 2-4 hours/time | Joint confirmation of reasons for change, addition or deletion of tasks, time, price and account adjustment |

The significance of this batch of catalogs is to establish the first edition of measurement benchmarks. After completing about 100-200 real task instances, actual data should be used to calibrate working hours, price, first-time acceptance rate and complexity coefficient.

---

8. Value delivery standards

The task acceptance cannot stop at "does the document exist?" It is recommended to establish a four-level value standard:

Level	Definition	Example
V1 results are complete	Delivered according to format and quantity	Reports, PPT, and data sheets have been completed
V2 decision-making available	Can directly support judgment or choice	Decision memorandum, benchmark conclusion, plan comparison
V3 operation is available	It has entered the actual process and can continue to operate	The agent is online, the course is officially taught, and the activities are executed
V4 Result Correlation	Develop clear relationships with measurable business results	Improved conversions, reduced costs, shortened cycle times, increased revenue

V4 is only suitable for projects with clear baselines, responsibility boundaries, and attribution methods. The results affected by factors such as customer resources and market environment will adopt "basic delivery price + result bonus".

General 100-point acceptance framework

Dimensions	Recommended weights
Scope Completeness	20
Correctness and Evidence	25
Usability and decision-making value	20
Standards and Compliance	15
Reviewable and traceable	10
Handover and Reuse Quality	10

Rules:

• 80 points: reaching contract acceptance;
• 90 points: professional and high-quality delivery;
• 95 points or above: Qualified as a candidate for platform reference assets;
• If there are serious errors in key items such as correctness, privacy, security, and intellectual property rights, it will be rejected directly;
• Scoring items are adjusted based on design, software, courses, activities, etc.;
• Subjective design tasks must confirm the direction, samples and reviewers before starting work.

---

9. Separation of workload, quotation and value

The platform has to calculate three things separately:

1. How many resources are needed to do this?
2. How much value does this create for customers;
3. How money received is distributed among contributors.

1. Standard effective working hours

Definition:

1 standard effective working hour, representing 1 hour of effective professional work completed by a qualified role that meets the task requirements.

It does not include:

• Waiting for customer information;
• Invalid meeting;
• Rework caused by own errors;
• Modifications beyond the agreed scope;
• Model, data, travel and supplier costs.

2. Workload calculation

$$ \text{Standard workload} = \text{Basic unit working hours} \times \text{Quantity} \times \text{Complexity coefficient} \times \text{Input readiness} \times \text{Coordination coefficient} \times \text{Timeliness coefficient} $$

Complexity coefficient

Level	Description	Coefficient
C1	Highly repetitive, complete template	0.8
C2	General professional tasks	1.0
C3	Multiple sources, multiple roles, certain ambiguity	1.35
C4	Highly customized, cross-system or high uncertainty	1.8
C5	Strategic, high-risk, scientific or regulated tasks	From 2.4, individually assessed

Other coefficients

Condition	Coefficient
Enter complete, existing template	1.0
Input part missing	1.2
Input is scattered and requires a lot of governance	1.5
Single Decision Maker	1.0
2-3 major stakeholders	1.15
4+ stakeholders	1.3
Normal cycle	1.0
Expedited	1.2
Emergency order	1.5

3. Quotation formula

$$ \begin{aligned} \text{Customer Quotation} ={}& \sum(\text{Role standard working hours} \times \text{Role base rate}) \ &+ \text{Model, data and software costs} \ &+ \text{External supplier costs} \ &+ \text{Professional intellectual property authorization} \ &+ \text{Risk preparation} \ &+ \text{Platform Service} \ &+ \text{result bonus} \end{aligned} $$

The quotation must show:

• Scope of work;
• Assumptions and exclusions;
• quantity;
  • workload;
• Complexity;
• Role composition;
• External costs;
• Platform service content and rates;
• Taxes and exchange rates;
• Acceptance node;
• Number of modifications;
• Accounting rules;
• Settlement time.

The same base task price should be used for the same task, responsibility and quality level. Regional differences mainly reflect local legal costs, taxes, currencies and professional services that must be completed locally, avoiding the simple use of low-income areas as a source of cheap labor.

---

10. Intelligent ledger sharing: four ledgers and a capital waterfall

1. Four accounts

Cash Ledger

Record customer payments, taxes, channel fees, external costs, funds to be released, funds released, refunds, and exchange rates.

Contribution Ledger

Document each person's assigned tasks, responsibilities, budget weights, quality results, changes, and final assignments.

Capability Ledger

Record what tasks were completed, difficulty, roles, evidence, evaluations, certifications, and competency changes.

Asset Ledger

Record the rights holders, versions, authorizations and future benefits of methods, templates, courses, codes, agents, data structures and cases.

These four accounts must be associated through the same Task Instance ID.

2. Account sharing principle

• The accounting ratio is frozen before the task starts;
• 80%-90% of remuneration is determined by task responsibilities and agreed delivery;
• 10%-20% can be used for quality bonus, result bonus or capitalization reward;
• Scope changes are adjusted through change orders;
• No algorithm may secretly modify the ratio after the task is completed;
• Changes in accounting rules for active projects require confirmation from relevant parties;
• Sales referral rewards will decrease with contract renewal;
• Customers cannot delay acceptance indefinitely without justifiable reasons;
• Coaching, reviews and project management are explicit labor and should be priced separately;
• Learning tasks that create real value for customers must be paid.

3. Three default ledger templates

The following is based on the "net service income" after deducting taxes, payment channel fees and external procurement designated by the customer as 100%.

Role	Standard delivery	Expert-led consultation	Coaching delivery
Customer Development and Commerce	6%	6%	5%
Solution/Task Architecture	10%	12%	8%
Industry Experts and Intellectual Property	8%	30%	10%
Project Manager/Coach	12%	10%	20%
Task executor	44%	20%	35%
Independent Quality Review	8%	7%	10%
Platform Infrastructure and Settlement	9%	10%	8%
Public training and venture funds	3%	5%	4%
Total	100%	100%	100%

This is just the default template. The true proportion of each task is determined by service intensity.

4. Platform service fee grading

Service level	Content undertaken by the platform	Recommended rates
Infrastructure	Identity, contract template, workbench, ledger, settlement record	5%-8%
Escrow matching	Infrastructure + talent matching + project support	8%-12%
Managed delivery	Requirements diagnosis, task breakdown, team, QA, customer service	15%-22%
Expert productization	Customer acquisition, product design, content production, operations, customer service, settlement	20%-30%

Only one service level is applicable to the same order to avoid overlapping fees.

The previously envisaged 30% expert subscription platform share is only applicable to the model where the platform undertakes complete productization and operation. Pure matching, pure payment or expert self-acquisition scenarios should not charge a uniform 30%.

5. Asset reuse and long-term dividends

When methodologies, courses, templates, code components or agents are reused by new projects, 3% to 15% of the income from related tasks can be extracted into the asset authorization pool.

Initial suggestions:

• Original creator: 50%;
• Current version maintainers and localizers: 30%;
• Expert Standard and Public Asset Fund: 20%.

Rules:

• Record contributions by asset version;
• Recertify validity every 24-36 months; *Customer-specific achievements may not enter the public asset pool without authorization;
• Background intellectual property rights, customer results and joint assets are listed separately in the contract;
• Future licensing income must not rely on vague identification of "participated in projects".

---

11. Demand Radar who continues to discover market demand

"Traditional requirements" and "new requirements" are suitable as maturity labels and are not suitable as main classifications. Design demand radar to continuously transform market signals into mission products.

1. Signal source

*Real enterprise consultation and quotation;

• New requirements in delivered projects;
• CRM and customer interviews;
• Recruitment positions and procurement announcements;
• Cooperation between industry associations and universities;
• Policy and regulatory changes;
• New methods proposed by experts;
• Changes in open source software and model capabilities;
• Feedback from overseas markets and regional nodes;
• Problems with failed projects and repeated rework.

2. Demand signal card

Each requirement record:

• Who pays;
• What events trigger requirements;
• Frequency of occurrence;
• How to solve it currently;
• Current cost;
• Budget sources;
• Outcome indicators; *What data is needed;
• Can it be standardized;
• Whether it is possible to train new people;
• How much can the AI take on;
• Whether it is reused across borders; *Main risks;
• There is evidence of real payment.

3. Opportunity Scoring

$$ \begin{aligned} \text{Opportunity points} ={}& 20% \times \text{Payment frequency}

• 15% \times \text{Repurchaseability}
• 15% \times \text{Budget and Value} \ &+ 15% \times \text{Standardization degree}
• 15% \times \text{Talent training value}
• 10% \times \text{AI Leverage} \ &+ 10% \times \text{Transnational reuse}

• \text{Risk points deduction} \end{aligned} $$

4. Requirements life cycle

Stage	Entry Conditions	Action
Signal	Single occurrence	Recorded, not immediately developed
Watch Observations	Repeats from Multiple Sources	Interviews, Finding Budgets and Alternatives
Validate verification	Real willingness to pay	Manual hosting to complete the first batch of tasks
Standardize Standardize	Task chain and acceptance stabilized	Create TaskSpec, rates and courses
Scale	Stable quality, gross profit and supply	Enter the task market and automatic matching
Maintain maintenance	Has become a long-term task	Continuously update versions and capability requirements
Retire	Need disappears or is replaced by automation	Archiving, migrating talent and assets

Suggested standardization threshold:

• High customer single task: at least 3 real paying customers;
• High-frequency tasks: at least 10-20 paid instances;
• The one-time acceptance rate reaches about 80%;
• The deviation between workload estimate and actual is controlled at 20%-30%;
• Repeatable task chains have appeared;
• There have been at least two independent deliverers able to achieve the same standard.

---

12. New job incubation mechanism in the AI era

New positions should form organically from recurring task clusters.

Position formation path

市场信号 → 付费任务 → 稳定任务簇 → 能力模型 → 带薪训练 → 认证 → 独立接单 → 新岗位

After a task cluster meets the following conditions, it can be upgraded to a formal position:

• Multiple customers continue to purchase;
• More than 70% of core tasks can be standardized;
• Have clear deliverables and quality scores;
• There is a trainable entry path;
• Have a relatively stable income level;
• Able to form a clear interface with other positions;
• AI augmentation still requires human responsibility, judgment or relationship capabilities.

Suggested new positions to be prioritized for incubation

New positions	Main task clusters
Enterprise Semantic Modeler	Business interviews, metric definition, process, role, data and decision modeling
Task Architect	Result Definition, Work Decomposition, Dependencies, Workload, Acceptance and Accounting Design
Agent Product Manager	Scenario evaluation, Agent PRD, tool boundaries, status and manual takeover
Agent Workflow Engineer	Prompt/Skill, MCP, API, Automation and Operational Monitoring
AI Evaluation Engineer	Test sets, scoring criteria, edge cases, security and regression testing
Expert knowledge engineer	Expert interviews, knowledge extraction, methodology, knowledge base and digital avatar
Human-machine delivery coach	Task coaching, process supervision, capability diagnosis, quality and review
AI achievement reviewer	Facts, data, models, copyright, security and delivery quality review
Course experience architect	Work task analysis, courses, training, cases, evaluation and lecturer system
Transnational study project producer	Corporate goals, destination resources, courses, suppliers and on-site operations
Science Communication Engineer	Documentation, Experts, Scientific Accuracy, Public Language and Multimedia Communication
Value Allocation and Settlement Specialist	Accounting Rules, Contribution Account, Asset Equity, Settlement and Dispute Handling

---

市场信号 → 付费任务 → 稳定任务簇 → 能力模型 → 带薪训练 → 认证 → 独立接单 → 新岗位

13. OPC UNI: Upgrading from training system to task certification system

The platform needs to upgrade "what has been learned" to "what can be accomplished."

OPC L1-L3 recommended definition

Level	Positioning	Permissions and Standards
Preparatory members	Learning and simulation	Complete basic tools, confidentiality, copyright, data and collaboration training
OPC L1	Supervised task performer	Complete 2 simulation tasks and 3 real teaching tasks, with a score of 80 or above
OPC L2	Independent task leader	Complete at least 10 acceptance tasks; on-time rate is over 90%; have independent delivery capabilities
OPC L3	Coach/Work Package Leader	Able to break down tasks, define acceptance, lead the team, develop members and be responsible for results
Expert/Standards Owner	Independent Professional Identity	Recognized by Industry Practice, Peer Review, Real-World Examples, and Standards Contributions

"Expert" does not equal an administrative level higher than L3. Expert is an independent professional certification dimension.

Capability evidence generated by each real task

• What tasks were performed;
• What skills were used; *Task difficulty;
• What responsibilities to bear;
• Who conducted the review;
• Final rating;
• Number of modifications;
• Whether the customer adopts it;
• What reusable assets are generated;
• Whether you are qualified for the next level.

Credentials can be gradually compatible with Open Badges 3.0 and W3C Verifiable Credentials, allowing members to carry and verify their abilities; xAPI can be used to record learning events in courses, simulations, and real tasks. 1EdTech Open Badges, W3C Verifiable Credentials 2.0, IEEE xAPI Standard

---

14. Talent matching and reputation system

1. Hard filtering

Judge first:

• Country and service qualifications;
• Whether access to data is allowed;
• Whether there is a conflict of interest;
• Language and time zone; *Required certification; *Level of responsibility; *Available time; *Budget range.

2. Match score

$$ \begin{aligned} \text{matching points} ={}& 30% \times \text{Skills and Evidence}

• 20% \times \text{History of similar tasks}
• 15% \times \text{Quality and rework} \ &+ 10% \times \text{Punctuality}
• 10% \times \text{Industry, Language and Culture}
• 5% \times \text{Available time} \ &+ 5% \times \text{Collaboration performance}
• 5% \times \text{Budget Adaptation} \end{aligned} $$

3. Reputation does not use an overall star rating

Each person should have a task-specific reputation vector:

*Task type;

• Difficulty; *Level of responsibility;
• First acceptance rate; *Rework rate;
• Punctuality;
• Communication performance; *Number of samples; *Latest completion time;
• Reviewer credibility;
• Whether significant compliance issues arise.

Five points for completing a simple task cannot directly replace the ability to perform complex projects. Scores with small samples must show confidence.

4. Match pattern

Mode	Applicable Scenarios
Direct assignment	High trust, confidentiality, long-term customers
Short List	Consulting, Design, Expert Services
Standard task recognition	Clear boundaries and quick acceptance
Competitions and bounties	Multiple solution exploration, algorithms, creativity
Fixed team	Continuous operation, long-term corporate service
Ad hoc teams	Interdisciplinary, complex projects
Teaching team	Newcomer training, low-risk modules

Competition models should limit unpaid speculative labor. High workload proposals that are shortlisted shall pay a shortlisting fee.

Reasons are given for each algorithm recommendation, and members are allowed to correct data, submit reviews and appeals. EU platform working rules have clearly emphasized transparency in algorithm management, human supervision and the right to appeal against automated decisions. EU Platform Working Rules

---

15. Delivery, acceptance and dispute mechanism

1. Complete process

1. Requirements entry;
2. Definition of results and acceptance;
3. Dismantle the task map;
4. Quotes and accounts are frozen;
5. The funds enter a protected state;
6. Talent matching;
7. Input data readiness check;
8. Human-machine collaborative execution;
9. Automated pre-check;
10. Independent professional review;
11. Customer acceptance;
12. Fund release;
13. Generation of capability certificates;
14. Asset registration;
15. Project review and standard upgrade.

Upwork’s fixed-price milestones use pre-funding, submission, review and release of funds; Topcoder uses a rubric to measure submission quality; Open Collective showcases open budgets and deals. These three types of mechanisms correspond to fund protection, quality judgment and financial transparency respectively, and can be combined into your basic mechanism. Upwork Milestone Funding Mechanism, Topcoder Scorecards, Open Collective Transparent Budget

2. Acceptance rules

• Confirm "input readiness standards" before starting work;
• Submission must include results, evidence, version and self-test;
• AI completes machine checks such as format, citation, field, code testing, etc.;
• Independent reviewers are responsible for professional judgment;
• Customers will provide feedback within 5-10 working days as agreed in the contract;
• If there is no feedback, it will be automatically accepted according to the contract rules or enter reminder and arbitration;
• In-scope modifications usually include one round;
• New requirements, new objects, new data, and new directions enter the change order;
• Reviewers need to check for conflicts of interest;
• Review work is billed independently.

3. Dispute resolution

Three-level mechanism:

1. Project manager coordination and scope verification;
2. Re-scoring by independent professional reviewers;
3. The platform dispute committee will make a ruling based on the contract, task card and evidence.

Appeals are allowed, but each level must be time-limited. Dispute judgments should be based on ex-ante standards and cannot be based on temporary additions of customer preferences.

---

16. Product system architecture

Modules	Core Functions
Need Studio	AI interview, needs diagnosis, result definition, budget and scenario identification
TaskGraph	Project disassembly, dependencies, task standards, versions, workload
Quote Engine	Time, complexity, price, scenario quotation, changes
TalentGraph	Talent, skills, task evidence, certification, availability
Match Engine	Eligibility filtering, interpretive recommendations, team composition
Workroom	Files, messages, versions, meetings, decisions, task status
Agent Orchestrator	Agent-to-Agent workflow, tool invocation, manual takeover
Quality Engine	Scoresheets, Machine Checks, Benchmark Sets, Peer Reviews
OPC UNI	Courses, simulations, teaching tasks, competency certification
AssetGraph	Methods, templates, courses, codes, agents, authorizations and versions
ValueLedger	Budget, contribution, sub-account, bill, payment and asset income
Trust & Compliance	KYC, Contracts, Data, Taxes, Sanctions, Disputes
Command Center	Demand, Delivery, Talent, Quality, Billing, and Assets Dashboards

Core Data Object

• Organization;
• Buyer; *Contributor; *Expert;
• Coach; *Need; *Outcome;
• Project; *Milestone;
• WorkPackage;
• TaskSpec;
• TaskInstance; *Assignment;
• Deliverable; *Evidence;
• Rubric;
• Review;
• Skill;
• Credential;
• Asset;
• License; *Contract;
• ChangeOrder; *Invoice;
• Payment;
• SplitRule;
• LedgerEntry;
• Dispute; *Agent;
• Tool; *Policy.

Technical principles

• The financial system adopts double-entry accounting;
• All key actions use appended event logs;
• The result file enters the object storage and the version is saved;
• Form a relationship map between tasks, capabilities, personnel, and assets;
• Semantic retrieval uses independent knowledge index;
• The agent output records models, skills, tools, data and manual reviewers;
• Smart contracts only execute stable and clear accounting rules;
• Complete the auditable ledger in the initial stage, and then decide which links need to be on-chain.

---

17. Global architecture: one standard core, multiple regional nodes

Centrally operating a global labor platform quickly encounters contract, tax, payment, data and employment discrepancies. A federal structure should be adopted in the long term.

Global Core Responsible

*Task standards;

• Competency standards;
• API and data protocols;
• Global identity and credibility;
• Mutual recognition of certificates;
• Asset registration;
• Audit rules;
• Brand and governance.

The regional node is responsible for

• Local entities and contracts;
• KYC, AML and sanctions screening;
• Payment, invoicing and taxes;
• Labor and contracting relationships;
• Data localization;
• Local language;
• Customer service;
• Dispute handling;
• Network of local experts and coaches.

Data classification

Levels	Data	Cross-border principles
P0	Public information	Cross-border available
P1	General internal information	Used with permission, minimized
P2	Trade secrets and confidential information	Limited areas, limited roles, leaving traces throughout the process
P3	Personal sensitive information, important data, customer source code, regulated data	In principle, processed locally, not cross-border

During cross-border collaboration, priority is given to generating a “de-identification task package”:

• Delete personal information;
• Delete customer identity;
• Replace sensitive data;
• Only keep the fields necessary to complete the task;
• Interface the source code;
• Separate professional judgment from regulated data processing.

The transfer of personal data abroad from the EU requires the use of mechanisms such as adequacy decisions and standard contractual clauses; digital platforms may also be subject to income information collection and tax reporting obligations. [EU Cross-Border Data Standard Contractual Clauses] (https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en), [OECD Digital Platform Tax Reporting Rules] (https://www.oecd.org/en/topics/sub-issues/international-tax-compliance-policies-and-best-practices/model-reporting-rules-for-digital-platforms.html)

OPC members can use real independent business entities for B2B cooperation, but the contract name itself cannot replace the real business relationship. Platforms need to ensure that members have task selection rights, time autonomy, non-exclusivity, algorithm appeal rights and clear business responsibilities to prevent de facto false self-employment.

Fund custody and cross-border payments should be connected to licensed payment or custody institutions, and the platform itself should avoid directly depositing customer funds when it lacks the corresponding qualifications.

---

18. Business model

Types of revenue	Content purchased by customers	Charging methods
Enterprise Managed Delivery	Results, Teams, Task Management, QA	Project Fees, Milestone Fees
Standard task market	Standardized professional tasks	Fixed price, quantity unit price
Enterprise task subscription	Continuous design, research, operation, agent maintenance	Monthly fee, quarterly fee
Expert knowledge products	Consulting, courses, digital avatars, knowledge licensing	Subscription, single time, licensing sharing
OPC UNI	Courses, simulations, coaching and certification	Course fees, business training fees
Asset authorization	Templates, courses, data structures, agent components	Authorization fees, reuse sharing
Regional nodes	Brands, standards, systems, order networks	Node service fees, revenue sharing
API/white label	Task map, competency certification, accounting system	SaaS, API calling fee
Results bonus	Attributable operating results	Base fee + bonus

Training income cannot become the dominant logic of the platform. Training must continue to be oriented towards real tasks, real income and real abilities, and avoid evolving into an education business centered on selling certificates.

---

19. Focus of the first issue: three mission factories

The cold start of the global platform requires the formation of high-density supply and demand and reliable standards. In the first phase, it is recommended to adopt a managed delivery network and open the market after the quality and supply density mature.

Task Factory 1: Enterprise AI Transformation

Complete chain:

企业访谈 → 业务语义建模 → 决策流程 → Agent PRD → 开发评测 → 部署 → 使用陪跑 → 效果验收

Value:

• High unit price;
• Continued demand;
• TABLE AI already has the capability;
• A large number of new positions can be formed in the AI era;
• Can accumulate enterprise tasks and evaluation data.

Task Factory 2: Productization of courses and experts

Complete chain:

专家识别 → 知识萃取 → 方法论 → 课程 → 案例陪练 → 讲师培养 → 企业交付 → 专家资产授权

Value:

• docking OPC UNI;
• Experts become standard owners;
• Coaches are responsible for large-scale delivery;
• OPC unit grows through real projects;
• Can generate ongoing licensing revenue.

Task Factory 3: Study, Incentive Travel and Corporate Activities

Complete chain:

企业目标 → 项目架构 → 课程与访问 → 供应商 → 预算 → 现场执行 → 评估

Value:

• Connect education, hotels, tourism, and international resources;
• Highly dependent on human judgment and on-site responsibility;
• Requires content, design, operations and cross-border collaboration at the same time;
• A unified platform that facilitates verification of online tasks and offline delivery.

Design, content, research, translation, project management and QA are embedded as horizontal capabilities of three task factories.

---

企业访谈 → 业务语义建模 → 决策流程 → Agent PRD → 开发评测 → 部署 → 使用陪跑 → 效果验收

专家识别 → 知识萃取 → 方法论 → 课程 → 案例陪练 → 讲师培养 → 企业交付 → 专家资产授权

企业目标 → 项目架构 → 课程与访问 → 供应商 → 预算 → 现场执行 → 评估

Twenty and 90 days implementation plan

Days 1-30: Establish rules and data base

Delivery:

1. Vision, brand and organizational division of labor charter;
2. Task classification dictionary V0.1;
3. TaskSpec data structure;
4. The first batch of 60 standard task cards;
5. 8-12 sets of acceptance score sheets;
6. Standard working hours and complexity rules;
7. Three types of ledger templates;
8. Intellectual property rights and asset dividend rules;
9. OPC L1-L3 capability standards;
10. Data classification and cross-border rules;
11. Standard contracts, task orders, change orders, and acceptance orders;
12. The first roster of experts, coaches and OPC units.

Days 31-60: Run real paid projects

Choose 3-5 real projects and complete:

• Requirements entry; *Task dismantling;
• Quotation;
• Sub-account freezing;
• Talent matching;
• Delivery;
• QA; *Acceptance;
• Settlement;
• Ability records;
• Asset registration.

The goal is to accumulate no less than 50-100 real task instances.

Days 61-90: Form MVP

The first version of the system will be implemented first:

• Demand table; *Task map;
• Standard task library;
• Talent and ability files;
• Quotation and accounting;
• Submission of documents and evidence;
• Acceptance score; *Fund status;
• Certificate of ability;
• Asset registration;
• Basic dashboard.

There is no need to pursue complete automation for the first release. After the rules and data structure are stable, smart matching, smart quotes and smart contracts will be gradually added.

---

21. Expansion gate

A larger public task market will be opened after the following standards are met:

• Completed more than 200 real tasks;
• The one-time acceptance rate reaches more than 80%;
• On-time rate reaches above 90%;
• Dispute rate is less than 3%;
• The deviation between actual workload and estimate is less than 25%;
• Customer repurchase rate reaches more than 40%;
• The median settlement time after acceptance is less than 5 working days;
• At least 20 task products can be stably delivered by different teams;
• At least three types of positions form a clear growth path from L1 to L3;
• At least three regions with local contract, payments, tax and data capabilities.

Development stage:

Stage	Form
M0	TABLE AI and OPC Global internal collaboration system
M1	Selected Talent, Managed Delivery Network
M2	Certified Talents and Standard Task Market
M3	Multi-language, multi-region federated network
M4	Open task standards, credentials, APIs and regional node ecology

---

22. Management indicator system

Requirements

• Effective demand quantity;
• Paid verification rate;
• Time from demand to quotation;
• Standard task coverage; *Repurchase rate.

Delivery

• First acceptance rate;
• On-time delivery rate;
• Rework hours;
• Estimate deviation; *Customer adoption rate;
• Dispute rate.

Talent

• Number of people receiving income for the first time;
• Promotion rate from L1 to L2, L2 to L3;
• Median monthly income of members;
• Income continuity;
• Number of valid task types for each member; *International mission participation rate; *Coach training success rate.

Fairness and Trust

• Subsequent modification rate of accounting rules;
• Settlement time after acceptance;
• Algorithm recommendation appeal rate;
• Complaint redressal rate;
• Platform fee disclosure rate;
• Free trial work hours;
• Revenue and order concentration.

Assets

• Added professional assets;
• Asset reuse rate;
• Asset licensing income;
• Continuous benefits earned by the original creator;
• Timely rate of asset update;
• Ratio of expired assets.

Verifiable definition of 0.5 / 3 / 2

The official website of OPC Global proposes that "in half a person's time, you can do the work of three people and get the money of two people." It is recommended to convert it into a long-term experimental indicator:

• 0.5 time: The effective human working hours for similar tasks are reduced to 50% of the baseline before AI is used;
• 3 times output: The number or value of results that pass acceptance per unit time is increased to 3 times;
• 2 times income: The effective working hours income or stable annual net income of the member unit reaches 2 times the original baseline.

Each calculation must be based on similar tasks, similar quality, and sufficient samples.

---

23. The ten most likely places to fail

1. Covering all industries at the beginning resulted in insufficient supply and demand.
2. Mix task classification, job classification, and industry classification into one tree.
3. Only work hours are recorded, results and acceptance are not defined.
4. Pay only by results, but have no attributable boundaries of responsibility.
5. Rate all abilities using an overall star rating.
6. The platform later modifies the ledger or uses hidden algorithms.
7. Package newcomers’ practical experience as free labor.
8. The platform uniformly owns all the intellectual property rights of experts, coaches and members.
9. Develop complex blockchains and DAOs first, and the rules themselves are still vague.
10. Relying on a large amount of training to acquire customers, but not enough real orders to accept students.

---

#final strategic expression

**TABLE AI is responsible for converting complex enterprise needs into executable human-machine task systems; OPC Global is responsible for allowing global experts, coaches and individuals to obtain income, capabilities and long-term rights and interests through real tasks; the common infrastructure is responsible for recording tasks, verifying results, allocating value and precipitating assets. **

One sentence can be defined as:

** Divide global needs into standard tasks, turn real tasks into paid growth, turn deliverables into credible evidence, and turn every contribution into long-term equity. **