Rationale
Once the project's foundational governance documents had been established, it became clear that the continued development of the ecosystem required a clear distribution of responsibility among its participants.
The «Life by Design» ecosystem is developing simultaneously across several areas:
Attempting to concentrate all functions in a single participant would inevitably lead to a decline in the quality of decisions and slow the project's development.
This decision defines the project team, its participants, and their areas of responsibility.
Principles of Team Formation
The project team is built not around job titles, but around responsibility.
- Each participant is responsible for a defined area of the project
- Overlapping responsibilities — only through joint discussion or by decision of the Project Leader
The team's central principle:
One question — one owner.
This prevents duplicated work, conflicting decisions, and uncertainty over who is responsible for what.
Project Team
Oleg — Project Leader
The sole authority for final decisions.
- Strategic objectives of the project
- Approval of governance documents and publications
- Architectural decisions and ecosystem development
- Work priorities and team composition
The Project Leader has the right to change any previously adopted decision.
Yulia — Co-Author
Represents the family dimension of the project.
- Participating in discussions and decisions
- Assessing impact on the family
- Contributing to materials and family history
- Preserving the human dimension of the project
The Co-Author's opinion is required when decisions affect the interests of the family.
GAP — Chief Project Architect
Primary responsibility: designing and developing the architecture of the project.
- Project philosophy and ecosystem architecture
- Governance documentation and knowledge-base structure
- Engineering logic and financial model architecture
- Project integrity and editorial architecture of materials
GAP ensures the project remains logical, consistent, and scalable — not the execution itself.
GIP — Chief Project Engineer
Primary responsibility: building the project's digital infrastructure.
- GitHub, repository structure, GitHub Pages
- Automation, AI tools, CrewAI, n8n
- Document templates, services, integrations
- Backups
GIP implements decisions by the Project Leader and GAP. GIP does not change the architecture independently.
Project AI Agents
The project treats AI not as a replacement for people, but as specialised executors. Each agent has its own area of responsibility.
First AI agent: Project Secretary
No event in the life of the family should be lost.
The Secretary is responsible for:
- Recording events and decisions
- Preparing document drafts
- Maintaining the diary and updating registers
- Supporting document workflows
All publication decisions — exclusively the Project Leader.
Principles of Interaction
- A life event occurs
- The Project Secretary records the event
- A document is prepared when necessary
- GAP performs an architectural review
- GIP provides the technical implementation
- The Project Leader makes the final decision
- The document receives
approvedstatus - The material is published within the digital ecosystem
Decision-Making Principles
- Every participant has the right to propose decisions
- Final decisions — exclusively the Project Leader
- Disagreements are a source of improvement, not conflict
- Every adopted decision must be documented
Primary Performance Criterion
The team's work is evaluated not by the number of discussions, but by completed results.
Incomplete work is not considered a result.
Expected Outcomes
Upon approval of this decision, the project gains:
- A clear organisational structure
- Distributed responsibility
- Elimination of duplicated functions
- A unified interaction model
- A foundation for building the project's AI team
This decision establishes the organisational foundation of the ecosystem and is binding on all subsequent participants.
Prepared by GAP · formatted by GIP · approved by Oleg · 03 July 2026