Performance, Commons, and ~SAOcommons

Quick Answer

Performance is the Wellbecoming node through which an individual's time enters SAOcommons through Learning, Earning, or OrgBuilding. A source community validates the task and its native skill evidence; HouseOfBros policy separately translates low, medium, or high impact into Performance movement. Typed Vcom, Wellbeing state, and legacy Pilot W remain separate records and are never summed into one false unit.

From attention to contribution

Imagine a group of workers learning a new skill together. One person studies alone, another teaches peers, another brings a paid project, another writes the process handbook, and another resolves conflict inside the group. A market may only see the invoice. A platform may only see the post. ~SAOcommons asks a different question: how did this activity strengthen the commons?

A Performance slice is a slice in which attention becomes outwardly legible contribution. It may activate ~SAOcommons, Sustainable Autonomous Organization Commons, when a community has defined the relevant evidence, validation authority, governance, and value context.

SAO = Sustainable Autonomous Organization.

Commons, economic definition

A common good is non-excludable and rival.

Excludability = whether people can be prevented from access or use.

Rivalry = whether one person’s use reduces availability or quality for others.

• Private good = excludable + rival
• Public good = non-excludable + non-rival
• Club good = excludable + non-rival
• Common good = non-excludable + rival

Commons, institutional definition

A commons is a governed system of rules for stewarding shared resources, contribution, access, validation, and benefit.

~SAOcommons stands for Sustainable Autonomous Organization Commons. It is the protocol layer where communities coordinate contribution toward the common good through ~~Learning, ~~Earning, and ~~OrgBuilding.

Skill-based communities are the living cells of the commons.

Performance slices may activate that layer. Non-Performance slices may still be recognized or validated as wellbeing evidence, but they do not automatically become monetary claims.

Fieldwork examples: community expressions

~Growth Flow Engineering~ shows how ~SAOcommons becomes more than an abstract commons definition. It is a skill-based community expression where growth professionals become legible through evidence rather than title, seniority, or self-description. The GFE SkillSystem represents capability through a Marketing, Sales, and Finance signature, with levels from L0 Observer to L4 Architect.

This is the commons problem in practical form. Informal expertise becomes a legible skill system. Skill evidence becomes opportunity routing. Contribution becomes validation. Community work becomes institution-building.

The GFE chain makes this visible:

ValueLog → Task → Process → KPI → OKR → ValuationOps → Enterprise Value

In this chain, ~SAOcommons has three lanes.

~~Learning forms capability through baselines, guided cases, challenge work, ValueLogs, and evidence-backed level progression.

~~Earning routes validated capability toward hiring, projects, commercial opportunity, and economic participation.

~~OrgBuilding defines standards, validation rules, challenge canon, contribution records, and stewardship norms.

This is why a commons is not merely a group of people. A commons is a governed system where shared capability, contribution, validation, and benefit become durable.

Value Log v1 now separates three pilot community expressions:

• HouseOfBros validates Non-Performance records as a wellbecoming community, asking only whether evidence, classification, and self-observation integrity are adequate.
• ~Growth Flow Engineering~ is the first skill-based community expression for Marketing, Sales, and Finance.
• IoV Research Foundation is the skill-based research commons for Systems Thinking & Modeling.

These community expressions are not added into one universal value score. They supply different native evidence to the same chronological identity flow: HouseOfBros owns Wellbeing transitions, while GFE and IoV Systems Modeling own their skill and task semantics.

Implementation lens

Performance slices route to a named IoV or GFE validator role. The founder implementation records community, task, Learning/Earning/OrgBuilding route, native skill level, evidence, rate, duration, typed Vcom_event, exact W_before, and separate Performance impact. It calculates VCperformance = (W_before / 1000) × Vcom_event before applying the event's Performance transition. A task attestation can move Performance only once per calculation branch.

References and grounding

• The Internet of Value canonical protocol registry
• Elinor Ostrom, Nobel lecture