Constitutional authority
Documented architectureDefines the highest-order mandate, reserved powers and boundaries that subordinate decisions must not exceed.
Live technical information site. The planned DLT is not live; membership is on ByteShares.dk.
Layers
The technical governance layer describes how decisions would be represented as protocol data. It is not the cooperative's governance, and it does not carry any binding decision today.
Member governance — general meetings, member votes, the board and any legally binding decision — sits with the ByteShares.dk cooperative. It is not conducted here and is not mirrored here.
What this layer describes is narrower: how a decision, once made, could be expressed in a machine-readable form that other layers can reference.
Defines the highest-order mandate, reserved powers and boundaries that subordinate decisions must not exceed.
Expresses delegated mandates, scopes, terms and thresholds for accountable institutional decision-making.
Converts an authorized outcome into machine-verifiable permissions and rule changes without creating legal authority by itself.
01
A change is described with its rationale, its scope and the state it would produce.
02
Where a vote applies, eligibility and threshold are fixed before the decision is taken, not after.
03
The outcome becomes an explicit authority record naming scope, holder, rule version and validity.
04
The protocol applies the authorized rule version. Execution never invents authority it was not given.
05
A proof object records the inputs, the authority relied on and the outcome.
06
Evidence is anchored, and the epoch closes with a snapshot fixing the resulting state.
The flow is a written design. No stage is implemented, and no decision taken anywhere is currently carried by it.
01
Preparatory governance state in which scope, authority and eligible participants are defined.
02
The initial authorized statement of rules, roles, boundaries and starting state.
03
A hash, timestamp and reference bind the approved memo to the protocol record.
04
A bounded proposed period with objectives, milestones and closure criteria; no timing or operating process is fixed.
05
The period closes with a defined state, governance outcomes and proof snapshot.
This sequence is a derived review model, not an operational DAO or proof that a precise state machine has been adopted. Missing eligibility, authority, constraint or evidence requirements fail closed in the proposed model.
Exceptional action should require a named authority, narrow scope, reason, expiry and permanent audit record.
A disputed result should be stayed, reviewed and resolved through an authorized compensating decision. Prior history remains visible rather than being deleted.
No exception body, reversal procedure, dispute forum or response timetable is operating.
Proposed / Non-operational — review questions, not decisions or implementation contracts.
Each statement on this page is tracked against a source. A claim without a verified source is never presented as fact.
| Claim | Source type | Verification | Note |
|---|---|---|---|
| Authority domains, governance objects and epoch sequence | Master Business Plan v2.1 / aligned canon | Source claimed, not yet verified | Owner-provided masterplan extracts support a proposed doctrine summary; full-source fidelity and public-disclosure scope remain unverified, and no protocol implementation exists. |
| Exception, reversal and dispute pathways | Owner-provided aligned technical canon | Source claimed, not yet verified | Pathways are owner-asserted; procedures, responsible bodies and timetables remain undefined. |
| Relationship to cooperative statutes | ByteShares.dk statutes | Source claimed, not yet verified | Statutes govern member decisions; alignment not yet reviewed. |