Formationly Executive Operating System
FEOS Domain Model
The foundational business objects that define how people, organizations, relationships, training, resources, ministry activity, and intelligence fit together within FEOS.
Version 1.0 • July 2026
Purpose of the Domain Model
Define the platform before expanding the interface.
FEOS should not be designed as a collection of unrelated pages. It should be built around a consistent set of business objects that can be reused across navigation, workflows, dashboards, relationship management, reporting, and future AI capabilities.
The domain model establishes a common language for development and helps prevent duplicate records, conflicting terminology, and fragmented workflows.
Core FEOS Relationship
Partners steward relationships with people and organizations while Formationly preserves the complete ministry history.
Every conversation, task, resource, recommendation, and follow-up should connect back to a defined person, organization, partner, or ministry objective.
Domain Overview
FEOS is organized into seven connected domains.
01
Identity Domain
Who participates in FEOS?
Identity objects define users, roles, responsibilities, permissions, and the relationship between human users and AI-assisted capabilities.
Partner
A Formationly representative completing the guided partner journey.
Premier Partner
An advanced partner with greater leadership, expansion, or coaching responsibilities.
Administrator
A Formationly team member with governance and platform management authority.
AI Executive Guide
A contextual assistant that equips users without replacing human judgment.
02
Organization Domain
Who does Formationly serve?
Organization objects represent the ministries, schools, associations, publishers, and communities connected to Formationly.
03
Relationship Domain
How are relationships developed?
Relationship objects preserve the progression from first contact through conversations, follow-up, partnership, and long-term ministry collaboration.
04
Ministry Activity Domain
What mission activity is occurring?
Ministry objects help FEOS measure work that matters beyond transactions, including outreach, family impact, prayer, testimony, and expansion activity.
05
Learning Domain
How is the partner prepared?
Learning objects connect Thinkific training with readiness, certification, progress, and future AI recommendations.
06
Resource Domain
What tools support the mission?
Resource objects allow marketing, outreach, training, and conversation materials to be categorized, recommended, reused, and measured.
07
Intelligence Domain
How does FEOS guide decisions?
Intelligence objects convert activity, context, history, and progress into useful preparation, recommendations, alerts, and executive insight.
Primary Relationship Flow
How core FEOS objects connect
Partner
→
Organization
→
Contact
→
Relationship
→
Conversation
→
Next Action
Domain Governance
Every object requires clear ownership and lifecycle rules.
Formationly retains ownership of organizational and relationship records.
Partners may create, view, and update records according to assigned permissions.
Partners should not permanently delete organizational knowledge or relationship history.
Important changes should be recorded through audit history.
Objects should be archived, reassigned, merged, or restored according to governance rules.
Implementation Guidance
The domain model should guide every future FEOS build.
STEP 1
Define
Confirm each object’s purpose and official terminology.
STEP 2
Relate
Document how objects connect and depend on one another.
STEP 3
Govern
Define permissions, ownership, reassignment, archival, and deletion rules.
STEP 4
Implement
Build interfaces and workflows around approved objects.
A shared data language creates a coherent platform.
The FEOS Domain Model provides the common structure needed to connect partner development, ministry relationships, resources, AI guidance, and executive intelligence within one operating system.
