Governance review

The Governance tab is two lists: the rules attached to this specification, and the roles the viewing agent holds. Both are rendered raw.

Governance rules, as rendered

A rule is a type string plus a JSON blob, and the tab prints the blob in a <pre>. That is honest about the data model — rule_data really is an untyped JSON string in the zome — and it puts the raw shape in front of whoever has to act on it.

  • access_requirement
    {
  "min_role": "AccountableAgent",
  "requires_validation": true
}
    Enforced by: PrimaryAccountableAgent
  • benefit_redistribution
    {
  "contributor_pool": 0.6,
  "maintenance_reserve": 0.3,
  "commons_levy": 0.1
}

Roles, and the disabled button

Under the role list sits a permanently disabled amber button reading AccountableAgent (governance-gated). It is a placeholder for role promotion, and it is the clearest statement in the app of something the protocol specifies and the UI has not built.

  • AccountableAgent
  • Repair

Where reputation is not

Nothing on this tab is a score, and that is deliberate. Private Participation Receipts are private entries on each agent's own source chain: bilaterally signed, non-transferable, and invisible to third parties by default. There is no aggregator to render and none to capture.

Open questions

  • Rules render as raw JSON. Useful to a developer, opaque to the custodian the rule governs.
  • The tab shows my roles rather than who is accountable for this NDO, which is the question the page's title implies.
  • The disabled button has no explanation of what would enable it.

Live: the Governance tab.