Part Two: The Architecture
Block 17

R6/R7 — The Action Framework

R6/R7 is the transport protocol of Web4Web4Open governance ontology for trust-native entity interactions. It transports energy, tracks work, and attests to value and reputation. Every interaction — every action an entity takes, every request it makes, every result it produces — is wrapped in this structured action context.

The R7 Equation

Rules + Role + Request + Reference + Resource → Result + Reputation

Seven terms, each a concrete governance primitive:

  • Rules — The law-in-the-loop mechanism. Rules places law in context of action — the versioned law datasets, quorum requirements, and scoped authority from the society the entity operates in. Every R6/R7 action carries its governing law, not as a reference to look up later, but as a present participant in the interaction.
  • Role — What function the entity fills in this context. Role-contextual: an entity's trust profile as a code reviewer is independent of its profile as a database administrator.
  • Request — What is being asked. The specific action, scoped by MRHMarkov Relevancy HorizonFractal context scoping — defines where governance applies — what's relevant to this interaction, what's outside the boundary.
  • Reference — What context informs the action. Prior decisions, precedent, the entity's accumulated history in this role.
  • Resource — What ATPAllocation Transfer PacketCharged resource packet — an entity's capacity to act budget is available. Every action has a cost. The resource allocation determines what the entity can afford to do.
  • Result — What happened. The output, the deliverable, the observable outcome. Witnessed and recorded.
  • Reputation — What changed about trust. T3Talent / Training / TemperamentThree-dimensional trust measurement, role-contextual, with decay/V3Valuation / Veracity / ValidityThree-dimensional value measurement — did real value transfer occur? deltas computed from the outcome. Did the entity deliver? Was the claim true? Did real value transfer? Reputation is the R7 addition that makes trust evolution a first-class output of every interaction.

R6 vs R7: Proportional Governance

Not every interaction justifies full reputational accounting. A routine status check doesn't need the same governance overhead as a high-stakes financial decision. This is where R6 and R7 diverge:

R6(Rules + Role + Request + Reference + Resource → Result) is the lightweight action framework for routine, low-consequence interactions. Six terms. No reputational overhead. The action is governed — it has rules, role scoping, resource budgeting — but it doesn't compute trust deltas. Fast, cheap, sufficient for most interactions.

R7 adds Reputation as an explicit seventh output. The interaction now updates the entity's T3Talent / Training / TemperamentThree-dimensional trust measurement, role-contextual, with decay/V3Valuation / Veracity / ValidityThree-dimensional value measurement — did real value transfer occur? profile. This is reserved for interactions where trust evolution matters — consequential decisions, value transfers, authority exercises, anything where the outcome should change how much the entity is trusted in this role going forward.

The distinction is proportional governance. Biology does this naturally — your immune system doesn't run a full inflammatory response for every skin cell that divides. It reserves the heavy machinery for threats. R6 is routine cellular operation. R7 is the immune response — triggered when the stakes justify the cost.

R6/R7 as the Governance Wrapper

Every primitive introduced in the preceding sections — LCTLinked Context TokenAn entity's witnessed presence — permanent, non-transferable, cryptographically anchored identity, T3Talent / Training / TemperamentThree-dimensional trust measurement, role-contextual, with decay/V3Valuation / Veracity / ValidityThree-dimensional value measurement — did real value transfer occur? trust, MRHMarkov Relevancy HorizonFractal context scoping — defines where governance applies scoping, SALSociety / Authority / LawFramework for governing collectives — membership, delegation, norms governance, ATPAllocation Transfer PacketCharged resource packet — an entity's capacity to act/ADPAllocation Discharge PacketDischarged packet with delivery confirmation — record of work done metabolism — comes together inside an R6 or R7 action. The action framework is not a separate layer. It's the structure within which all the other primitives operate. Rules carry SALSociety / Authority / LawFramework for governing collectives — membership, delegation, norms law. Role carries LCTLinked Context TokenAn entity's witnessed presence — permanent, non-transferable, cryptographically anchored identity. Request carries MRHMarkov Relevancy HorizonFractal context scoping — defines where governance applies scope. Resource carries ATPAllocation Transfer PacketCharged resource packet — an entity's capacity to act budget. Result is witnessed. Reputation updates T3Talent / Training / TemperamentThree-dimensional trust measurement, role-contextual, with decay/V3Valuation / Veracity / ValidityThree-dimensional value measurement — did real value transfer occur?.

From the entity's perspective, governance is participation — and R6/R7 is the shape of every participatory act.

And participation is not compliance. Governance in this framework is not control — it is persuasive influence in context. The R6/R7 structure doesn't restrict what an entity can do. It shapes what makes sense to do, given the entity's trust profile, resource budget, and the consequences that witnessed accountability creates.