Compare concepts
Commons and Court
Compared from declared Lexicon data only. Shared relationships are not a claim the concepts agree.
How they relate
- Court part-of Commons
| Commons | Court | |
|---|---|---|
| Meaning | The shared behavior, interfaces and institutions no single Realm governs, including the Creator's. Not a fourth pillar or an owner of instance data. | The institution of the Commons that hears motions and records verdicts under the Covenant. It decides; it never observes or executes. |
| Adoption | proposed | proposed |
| Change rule | entrenched | entrenched |
| Decision | none; proposed | none; proposed |
| belief What does it hold to be true? | People and machine Things should be able to choose behavior and resources while retaining control of their own data and credentials. | Not captured. |
| purpose Why does it exist? | Provide one consistent way to describe parameters, manage chosen values, resolve runtime configuration and request protected credential use. | Not captured. |
| intention What does it set out to do? | Reuse the existing Corpus and deterministic execution paths, starting with production Settings and qualifying each missing custody boundary explicitly. | Not captured. |
| agency Who chooses and acts? | The owning Thing and its authorized delegates decide within their scope. Definitions, saved values, model output and secret references confer no permission by themselves. | Not captured. |
| capability What can it actually do? | Supply revisioned Settings, definition-driven rendering and validation, deterministic configuration resolution, and replaceable protected credential-use interfaces. | Not captured. |
| consequence What follows from it? | Applications can share behavior without sharing all state or secrets. Uncertain effects, unavailable custody and stale configuration remain visible and cannot silently become success. | Not captured. |
| responsibility Who answers for it? | The relevant Thing owns its records; reBe owns Settings and KeyRing experience, aThing owns portable data/control semantics, and theCy owns concrete configuration and custody providers. | Not captured. |
| wisdom What does it learn and keep? | Preserve failures, context, revisions and receiving evidence. Turn repeated mistakes into checks and retire advice whose conditions no longer apply. | Not captured. |
| unity How does it fit with others? | Use shared contracts and interoperable definitions across independent Realms while keeping ownership, admission and failure domains distinct. | Not captured. |