The objection
Bringing the decision systems of the executive, the judiciary and the legislature onto a common foundation nullifies, in practice, the separation that the constitution establishes.
The principle
Exchange between the branches must occur only through a legal act, never out of technical convenience.
What the separation of powers protects
The separation of powers is not an organizational chart: it is a defense against accumulation. Each branch knows what its powers allow it to know, and that reciprocal opacity is deliberate. A judge must not see the executive’s political agenda in order to rule; a legislator must not access the court file in order to legislate.
A platform that offered a unified view of the three branches would destroy that defense even if it were never used with ill intent. The capability itself is the problem.
Isolation by design, not by usage policy
That the three branches operate on a common technological foundation does not mean that they share an information space. Isolation must be a property of the system—verifiable, not entrusted to an administrator’s configuration or to an operator’s good faith.
When an exchange is legitimate, it must be formalized as what it is in law: a requisition that is grounded, addressed, bounded and time-limited. The instrument must state what is requested, on what grounds, for what purpose and for how long; and the issuer must sign the ceiling of that scope, so that the recipient cannot expand it on its own.
An omniscient view is not a pending goal
It is worth saying without ambiguity, because it is the kind of capability a customer might ask for and an accommodating vendor would build: Edelon must not offer a dashboard that aggregates the operations of the three branches, not even for the highest-ranking official. It is not a feature still waiting to be developed. It is a feature the design must prevent.
State of the evidence
What follows distinguishes design from demonstration. A principle upheld is not the same as a proven capability, and this series does not use the present tense for the latter.
- DesignedInter-branch exchange protocol mediated by a legal actSpecified in ADR-102, which remains in proposed status and records eight points as unproven, including end-to-end exchange.
- DesignedThe issuer signs the ceiling of the instrument’s scopeIt is the mechanism that prevents unilateral expansion by the recipient. It exists as a design contract, not as a capability verified in operation.
- UnprovenEffective isolation between branches in a real deploymentNo institutional installation has exercised the isolation under real load or under a documented adversarial attempt.
Open questions
- How is isolation demonstrated to someone who cannot inspect the code? Third-party verification and cryptographic evidence reduce the problem, but they do not eliminate it.
- What happens when a country’s law permits an exchange that this design restricts? The product restriction may be stricter than local law; that asymmetry must be resolved in writing before a deployment, not during it.