Formationly Executive Operating System

FEOS Master Architecture Index

The central directory for Formationly’s architecture documents, governing standards, development specifications, and future implementation records.

Architecture Library  •  Version 1.0  •  July 2026
Purpose of the Master Index

Every architecture document should be easy to locate, understand, and maintain.

The FEOS Master Architecture Index serves as the front door to the complete Formationly architecture library. It identifies each governing document, its purpose, status, version, relationship to other documents, and role in future development.

As FEOS grows, this index should remain the authoritative directory for product strategy, technical architecture, governance, design, implementation standards, and sprint records.

Governing Library Principle
“The architecture library should provide one reliable source of truth for the entire FEOS development program.”
Architecture Library Status

Foundation Library Established

The first FEOS architecture documents have been defined. Future documents will expand the library into product, engineering, governance, implementation, and operational volumes.

CURRENT VERSION
Library v1.0
FOUNDATION DOCUMENTS
9 Defined
CURRENT PHASE
Architecture
NEXT LIBRARY AREA
Technical Specifications
Foundation Documents

The documents that define FEOS

01
Complete

Founder’s Declaration

Defines why FEOS exists, its ministry purpose, its view of technology, artificial intelligence, relationships, excellence, and long-term stewardship.

Classification: Executive Foundation
02
Complete

FEOS Design Charter

Establishes the governing principles used to evaluate features, workflows, AI capabilities, design decisions, and future enhancements.

Classification: Governance
03
Complete

FEOS Master Development Roadmap

Documents the phased progression from platform foundation through navigation, KCRM, AI, executive intelligence, and enterprise scale.

Classification: Product Strategy
04
Complete

FEOS Navigation Specification

Defines the executive navigation structure, partner journey, workspace hierarchy, device behavior, and implementation sequence.

Classification: Experience Architecture
05
Complete

FEOS Domain Model

Defines the core business objects for users, organizations, relationships, ministry activity, learning, resources, and intelligence.

Classification: Data Architecture
06
Complete

AI Executive Guide Architecture

Defines contextual AI roles, inputs, boundaries, response standards, implementation stages, and human decision authority.

Classification: Intelligence Architecture
07
Complete

FEOS Design System

Establishes visual standards, page structure, colors, typography, spacing, reusable components, mobile behavior, and accessibility requirements.

Classification: Interface Architecture
08
Complete

KCRM Architecture

Defines Formationly’s stewardship-centered relationship platform, ownership model, records, permissions, lifecycle, governance, and future AI assistance.

Classification: Relationship Architecture
09
Complete

FEOS Sprint History

Preserves the development record, sprint outcomes, architecture decisions, milestones, source-control history, and future sequence.

Classification: Program History
Architecture Library Structure

Recommended document organization

FEOS Architecture Library
├── 01 Executive Foundation
├── Founder’s Declaration
├── Design Charter
└── Master Development Roadmap
├── 02 Product Architecture
├── Navigation Specification
└── Domain Model
├── 03 Intelligence Architecture
└── AI Executive Guide Architecture
├── 04 Experience Architecture
└── FEOS Design System
├── 05 Relationship Architecture
└── KCRM Architecture
├── 06 Program Governance
├── Sprint History
└── Master Architecture Index
└── 07 Future Technical Specifications
Planned Architecture Volumes

Future documents will expand the library.

VOLUME 10
Object Relationship Model
Defines formal relationships between core FEOS business objects.
VOLUME 11
Permissions Matrix
Documents view, create, edit, assign, archive, and administrative authority.
VOLUME 12
Engineering Standards
Defines HTML, CSS, Liquid, JavaScript, responsive, and documentation standards.
VOLUME 13
Git & Release Workflow
Documents branch standards, commits, backups, testing, rollback, and deployment.
VOLUME 14
API & Integration Architecture
Defines Thinkific, AI, CRM, messaging, analytics, and future integration boundaries.
VOLUME 15
Executive Intelligence Architecture
Defines KPI governance, ministry impact, analytics, reporting, and future AI insight.
Document Standards

Every volume should follow a consistent structure.

Official document title, version, date, owner, and status.
Purpose, scope, governing principles, definitions, and architecture decisions.
Business rules, user experience guidance, governance, and implementation implications.
Dependencies, related documents, future considerations, and revision history.
A clear distinction between approved architecture, planned capability, and future concept.
Version Control

Document versions should reflect the significance of the change.

VERSION 1.0
Initial Approved Baseline
The first formal architecture version.
VERSION 1.1
Minor Enhancement
Clarifications, added details, or limited scope expansion.
VERSION 2.0
Major Architectural Revision
A meaningful redesign, change in philosophy, or expanded system model.
Library Maintenance Workflow

Architecture changes should follow a controlled process.

STEP 1
Identify
Determine whether a new decision affects an existing document.
STEP 2
Evaluate
Review the change against the Founder’s Declaration and Design Charter.
STEP 3
Revise
Update the affected document and assign the correct version.
STEP 4
Cross-Reference
Update related documents, dependencies, and the Master Index.
STEP 5
Archive
Preserve the prior version and record the reason for the change.
Source of Truth

Chat supports development. The architecture library preserves development.

Conversations may generate ideas, drafts, recommendations, and implementation guidance. Approved architecture decisions should be transferred into the appropriate permanent document.

The most recently approved and versioned document should govern future implementation whenever earlier conversations, drafts, or notes conflict with the architecture library.

One architecture. One source of truth. One coherent platform.

The FEOS Master Architecture Index ensures that every future developer, leader, and implementation partner can locate the governing documents, understand their relationships, and extend Formationly without losing the original vision.