Life by Design · Project №60
Version 1.0 · en-US

Project Constitution
Life by Design

The fundamental rules governing the existence and development of the project

✅ Approved 03.07.2026
Gap — Chief Project Architect · Oleg — Project Leader

Purpose of the Document

This Constitution defines the fundamental rules governing the existence, development, and management of the «Life by Design» project.

The document establishes the roles of participants, the principles of decision-making, the life cycle of project documents, requirements for publications, and the project's core values.

The Constitution is the second most important project document after «Project Manifesto».

Scope

This document applies to:

  • all project participants
  • all project documents
  • all digital services of the project
  • all published materials
  • all future areas of development of the ecosystem

The Main Goal of the Project

The main goal of the project is to create an open ecosystem of family decisions based on the family's real-life experience.

The project exists to show how difficult life decisions are made, what consequences they have, and what conclusions can be drawn from them.

Important: the project does not provide consulting services. The project publishes its own experience only.

Principles of the Project

4.1 Honesty

The project prohibits the deliberate publication of inaccurate information. If published information is found to be incorrect, it must be corrected with a mandatory explanation of the reason for the change.

4.2 Openness

All decisions that do not involve personal data, trade secrets, or legal restrictions are published openly.

4.3 Verifiability

TypeExamples
Calculationsestimates, FIN tables
DocumentsDEC documents, contracts
Mediaphotographs, video materials
Regulationsbuilding codes, GOST standards, laws
Experiencepersonal experience of project participants

4.4 Responsibility

Each project participant is responsible exclusively for their own area of responsibility. Responsibility cannot be transferred without a corresponding decision by the Project Leader.

4.5 Respect

The project excludes: insults, humiliation of participants, the publication of knowingly false information, and discrimination on any grounds.

Project Governance Structure

The project follows the principle of separation of responsibilities.

Oleg — Project Leader

Approves strategy and documents · makes final decisions · determines areas of development.

The decision of the Project Leader is final.

Yulia — Project Co-Author

Discussing decisions · forming the family's position · preparing materials · assessing the impact of decisions on the family.

Gap — Chief Project Architect

Project architecture · strategy · document structure · financial architecture · engineering logic · quality of published materials · compliance of documents with the adopted architecture.

Gap does not approve documents.

Gip — Chief Project Engineer

Digital infrastructure · GitHub · automation · information storage · AI tools · integrations · technical implementation of solutions.

Gip does not change strategic decisions without the approval of the Project Leader.

Decision-Making and Documents

All significant decisions of the project are formalized in documents of the DEC series.

Each decision must contain a description of the problem, the options considered, the decision made, the rationale, the expected consequences, the date of the decision, and the responsible executors.

PrefixPurpose
PROJECT-BOOKProject Book
MANManifesto
CONConstitution
DECDecisions
STDStandards
REGDocument Register
DIADiary
FINFinances
ENGEngineering Conclusions

Project publications must correspond to actual events, reflect the family's real experience, be understandable to a broad audience, and maintain a respectful tone of communication. Materials are published only after review.

This Constitution may be amended exclusively by a new document of the DEC series. Changing the text without formalizing a decision is prohibited.

This Constitution entered into force on 03.07.2026 after approval by the Project Leader and is binding on all project participants.

Related documents

Revision history

VersionDateAuthorChanges
1.003.07.2026GapInitial edition
1.016.07.2026Gapen-US translation synced with ru-RU canon

Prepared by Gap · layout — Gip · en-US · 16.07.2026