Open Registry Rules

Author: Accord Project (imported by Entity.ID)

open-registry-rules@1.0.0 Contract ^2.0.0 cb3b9a3a0a02f855114d0a83bf3df9174da345498c385dab4434564842d6c3d6

The terms on which the Open Registry records an entity: eight rules, written once by the Registry, reproduced in no constitution and amendable by no entity.

Download Archive Download Compiled Archive Open in Template Playground Open in VSCode Web

Open Registry Rules

The terms on which the Open Registry records an entity: eight rules, written once by the Registry, reproduced in no constitution and amendable by no entity. This is Layer 1 of the three-layer model - the Registry's own instrument. An entity does not adopt it; it accepts it, through the open-registry clause, at the version in force when it adopts its constitution.

This document

  • Document: Open Registry Rules (rules)
  • Render model: id.entity.render.openregistryrules@1.0.0.OpenRegistryRulesRender
  • Projection: verbatim (model-factory lib/project-render-data.mjs)

The text is TemplateMark. It renders from sample.json, which is an instance of this template's own model.

Provenance

The text, the Concerto model and the namespace are the upstream author's, carried over unchanged. Only the sample data is Entity.ID's, and it is fictional.

  • Source: universal-constitution/v2-minimal-core-study.md section 3, Layer 1 - the eight rules carried verbatim from the study that defined them
  • Licence: Apache-2.0

Regenerating

Do not hand-edit this directory. It is generated:

node scripts/import-entity-templates.mjs [path-to-model-factory]   # emits src/open-registry-rules

Template Text

Open Registry Rules

Version 1.0.0, in force from 3 October 2026.

These are the terms on which the Open Registry records an entity. They are the Registry's own instrument. They are written once, by the Registry; they are not reproduced in any constitution; and no entity may amend them.

Rule 1 - Attribution

Every recorded entity resolves, through its constituents, to at least one natural person who is a subject of rights and obligations. The Registry refuses to record, and may suspend, an entity that does not.

Rule 2 - Chain

That resolution is checked to a stated maximum number of steps, set by the Registry.

Rule 3 - Substitutive transparency

No entity may keep both its constituents and its operations private. Where one is private, the Registry publishes the other.

Rule 4 - Announcement

Formation, every amendment, and dissolution are recorded. A recorded entity exists as a matter of fact from its first announcement, and third parties are entitled to rely on the record.

Rule 5 - Identifier

Identifiers are unique, persistent across amendment, conversion, migration and recognition, retired on dissolution, and never reassigned.

Rule 6 - History

Prior versions are retained and readable. No amendment erases the record.

Rule 7 - Recognition

A recognition by any registrar is recorded beside the constitution, names its grantor, and may be withdrawn by that grantor.

Rule 8 - Acceptance

By adopting a constitution on this Registry, the constituents accept the Open Registry Rules in force at adoption.


Rule 8 is what gives the other seven force without printing them in every document. An entity holds no power to amend Rules 1 to 7, because they were never part of its own instrument.

Open Registry Rules
====

**Version 1.0.0, in force from 3 October 2026.**

These are the terms on which the Open Registry records an entity. They are the Registry's own instrument. They are written once, by the Registry; they are not reproduced in any constitution; and no entity may amend them.

Rule 1 - Attribution
----

Every recorded entity resolves, through its constituents, to at least one natural person who is a subject of rights and obligations. The Registry refuses to record, and may suspend, an entity that does not.

Rule 2 - Chain
----

That resolution is checked to a stated maximum number of steps, set by the Registry.

Rule 3 - Substitutive transparency
----

No entity may keep both its constituents and its operations private. Where one is private, the Registry publishes the other.

Rule 4 - Announcement
----

Formation, every amendment, and dissolution are recorded. A recorded entity exists as a matter of fact from its first announcement, and third parties are entitled to rely on the record.

Rule 5 - Identifier
----

Identifiers are unique, persistent across amendment, conversion, migration and recognition, retired on dissolution, and never reassigned.

Rule 6 - History
----

Prior versions are retained and readable. No amendment erases the record.

Rule 7 - Recognition
----

A recognition by any registrar is recorded beside the constitution, names its grantor, and may be withdrawn by that grantor.

Rule 8 - Acceptance
----

By adopting a constitution on this Registry, the constituents accept the Open Registry Rules in force at adoption.

---

*Rule 8 is what gives the other seven force without printing them in every document. An entity holds no power to amend Rules 1 to 7, because they were never part of its own instrument.*
# Open Registry Rules

**Version {{rulesVersion}}, in force from {{inForceFrom}}.**

These are the terms on which the Open Registry records an entity. They are the Registry's own instrument. They are written once, by the Registry; they are not reproduced in any constitution; and no entity may amend them.

## Rule 1 - Attribution

Every recorded entity resolves, through its constituents, to at least one natural person who is a subject of rights and obligations. The Registry refuses to record, and may suspend, an entity that does not.

## Rule 2 - Chain

That resolution is checked to a stated maximum number of steps, set by the Registry.

## Rule 3 - Substitutive transparency

No entity may keep both its constituents and its operations private. Where one is private, the Registry publishes the other.

## Rule 4 - Announcement

Formation, every amendment, and dissolution are recorded. A recorded entity exists as a matter of fact from its first announcement, and third parties are entitled to rely on the record.

## Rule 5 - Identifier

Identifiers are unique, persistent across amendment, conversion, migration and recognition, retired on dissolution, and never reassigned.

## Rule 6 - History

Prior versions are retained and readable. No amendment erases the record.

## Rule 7 - Recognition

A recognition by any registrar is recorded beside the constitution, names its grantor, and may be withdrawn by that grantor.

## Rule 8 - Acceptance

By adopting a constitution on this Registry, the constituents accept the Open Registry Rules in force at adoption.

---

*Rule 8 is what gives the other seven force without printing them in every document. An entity holds no power to amend Rules 1 to 7, because they were never part of its own instrument.*
{
    "$class": "id.entity.render.openregistryrules@1.0.0.OpenRegistryRulesRender",
    "rulesVersion": "1.0.0",
    "inForceFrom": "3 October 2026"
}

Template Model

/*
 * Render model for open-registry-rules@1.0.0.
 *
 * The Rules are the Registry's own instrument - Layer 1 of the three-layer
 * model - so this package renders VERBATIM: the fixture is the render data,
 * and there is no canonical Constitution instance behind it. An entity never
 * adopts this document; it accepts it, through the open-registry clause.
 *
 * provenance:
 *   source: universal-constitution/v2-minimal-core-study.md section 3, Layer 1
 *   licence: Apache-2.0
 */
namespace id.entity.render.openregistryrules@1.0.0

import org.accordproject.runtime@0.2.0.{Request,Response} from https://models.accordproject.org/accordproject/runtime@0.2.0.cto

@template
concept OpenRegistryRulesRender {
  o String rulesVersion
  o String inForceFrom
}

Model Dependencies

Template Logic

Find the full logic for this template on on GitHub.

State Types

Type Sample JSON
org.accordproject.runtime@0.2.0.State
{
    "$class": "org.accordproject.runtime@0.2.0.State",
    "$identifier": "0b10d980-bfdc-11f1-9ff7-1d72310b3eef"
}

Request Types

Type Sample JSON
org.accordproject.runtime@0.2.0.Request
{
    "$class": "org.accordproject.runtime@0.2.0.Request",
    "$timestamp": "2026-10-04T10:12:02.456Z"
}

Response Types

Type Sample JSON
org.accordproject.runtime@0.2.0.Response
{
    "$class": "org.accordproject.runtime@0.2.0.Response",
    "$timestamp": "2026-10-04T10:12:02.456Z"
}

Events Types

Type Sample JSON

Technical Integration

Please refer to the Accord Project documentation for how to use a template or integrate it within your application.

View the Latest code for this template on GitHub.