Review
Examine the proposal through independent review before comparison.
BoxViaIndependent systems can examine the same question without giving up their own rules or responsibilities.
This research explores how their conclusions can be compared and how the authority behind decisions can remain traceable.
Two systems may agree on the facts but reach different conclusions because they assess different questions or apply different rules.
A useful comparison makes those differences visible.
It also identifies what each participant is entitled to conclude.
Comparison does not itself create shared authority, certification or permission to implement a change.
WORKING DRAFT · v0.2
Andrey Ekhmenin is developing rules for interaction between independently governed architectures.
The working package covers a normative core, objects and interfaces, a conformance model, and version and contribution rules.
Its purpose is to preserve each system's own assessment rules while making comparison possible.
Participation does not silently transfer authorship, ownership, authority or responsibility.
The project is a working draft rather than an adopted international standard.
After an action, it should remain possible to identify who authorized it and on what basis.
Continued operation alone does not establish that the authority behind it remains valid.
This research examines origin as a property of governance state rather than as a separate governance layer.
The framework note addresses these questions in the AEGF governance-transition context.
Read Post-Execution Legitimacy and Origin in Governance State - Framework Note v1.0 on Zenodo
PUBLISHED · v1.0.1 · 13 August 2026
FRP structures the review of proposed changes and relationships between sovereign architectural systems.
Each participating system retains its own authority, scope and responsibility.
Examine the proposal through independent review before comparison.
Determine the proposal's relationship to the participating architectures.
Keep formal acceptance separate from the review findings.
Establish whether the conditions for implementation are met without treating that finding as runtime authorization.
The protocol does not itself grant authority, ratify changes or transfer responsibility.
Publication does not by itself establish adoption or deployment by participating systems.
Author: Andrey Ekhmenin.
Acknowledged reviewers: Timothy E. Zlomke, Arabinda (AB) Sahoo, Gary Williams and Allan Christopher Beckingham.
Reviewer acknowledgment records contributions to review and refinement rather than co-authorship, collective endorsement or ratification.
ANDEKS™ provides rules and a method for independent assessment within explicit boundaries.
EAS studies interpretation, recognition and legitimacy after execution.
Use the author, title, version and DOI of each publication when citing it.
Descriptions on this page do not extend the authority or claims of the source documents.