01
One-to-One
One record is directly associated with one primary record.
Example: Partner → Partner Profile
Formationly Executive Operating System
FEOS Object Relationship Model
The structural model defining how partners, organizations, contacts, relationships, conversations, activities, resources, learning records, and intelligence connect across FEOS.
Architecture Library • Version 1.0 • July 2026
Purpose of the Relationship Model
Every FEOS record should have a clear place and a clear connection.
The FEOS Object Relationship Model extends the Domain Model by defining how major business objects connect, depend on one another, inherit context, and contribute to the permanent organizational record.
These relationships will guide future database design, KCRM workflows, permissions, reporting, AI context, navigation, and user-interface development.
Core Relationship Hierarchy
The organization record sits at the center of ministry relationship history.
Formationly
→
Organization
→
Contact
→
Relationship
→
Activity
→
Next Action
Relationship Types
FEOS should use four primary relationship patterns.
02
One-to-Many
One parent record may contain multiple related records.
Example: Organization → Contacts
03
Many-to-Many
Multiple records may be associated through a controlled linking object.
Example: Partners ↔ Organizations
04
Hierarchical
A parent record may contain subordinate divisions, campuses, regions, or affiliated entities.
Example: Denomination → Churches
Identity Object
Partner
Represents an authorized Formationly user responsible for learning, outreach, relationship stewardship, activities, and assigned responsibilities.
Has One
Partner Profile
Has Many
Assignments
Has Many
Learning Records
Creates Many
Activities and Notes
Receives Many
Recommendations
Owns Many
Tasks and Follow-Ups
Core Relationship Object
Organization
Represents the authoritative record for a church, school, homeschool organization, publisher, ministry, nonprofit, association, business, or strategic partner.
Has Many
Contacts
Has Many
Partner Assignments
Has Many
Relationships
Has Many
Activities
Has Many
Opportunities
May Have
Parent or Child Organizations
Person Object
Contact
Represents a person associated with one or more organizations and participating in one or more ministry relationships.
Belongs To
One or More Organizations
Has Many
Roles
Participates In
Conversations
Receives
Resources and Follow-Ups
May Be
Primary Contact
Has One
Communication Preference Set
Stewardship Object
Relationship
Represents the ongoing connection between Formationly, an organization, one or more contacts, and the partner or team assigned to steward it.
Connects
Organization and Partner
Includes
Relationship Stage
Includes
Relationship Health
Has Many
Conversations
Has Many
Commitments
Produces
Recommended Next Actions
Timeline Object
Activity
Represents a timestamped event that becomes part of the permanent relationship, learning, governance, or operational timeline.
Created By
Partner, Administrator, System, or AI
Belongs To
Organization or Partner
May Reference
Contact or Relationship
May Produce
Task or Follow-Up
May Include
Resource Shared
Is Recorded In
Permanent Timeline
Supporting Object Map
Supporting objects extend the core relationship record.
CONVERSATION
Belongs to an organization and relationship; may include contacts, partners, notes, resources, and follow-up.
TASK
Assigned to a user; may relate to an organization, contact, conversation, opportunity, or internal mission.
FOLLOW-UP
Created from a conversation, task, commitment, presentation, or AI recommendation.
RESOURCE
May be linked to audiences, workspaces, conversations, campaigns, organizations, and partner actions.
LEARNING RECORD
Belongs to a partner and connects courses, lessons, progress, assessments, certifications, and readiness.
AI RECOMMENDATION
Belongs to a user and may reference workspace context, learning status, relationship data, resources, or activity.
OPPORTUNITY
Belongs to an organization and relationship; may include contacts, stage, next action, resources, and activity history.
CAMPAIGN
May include organizations, contacts, resources, activities, goals, assigned partners, and measured outcomes.
Assignment Model
Partner-to-organization relationships require a formal assignment object.
Because multiple partners may participate in a relationship over time, FEOS should not store ownership as a simple name field. A dedicated assignment object should preserve responsibility and history.
PARTNER
The user assigned to steward the relationship.
ORGANIZATION
The organizational record being assigned.
ROLE
Primary partner, supporting partner, regional lead, or administrator.
DATES
Assignment start, end, reassignment, and effective dates.
STATUS
Active, supporting, temporary, transferred, inactive, or historical.
AUDIT HISTORY
Who assigned, changed, approved, or ended the responsibility.
Organization Hierarchy
FEOS should support connected organizational structures.
Parent Organization
├── Regional Division
├── Local Organization
├── Campus or Location
└── Ministry Department
└── Local Organization
└── Strategic Affiliate
Hierarchies may represent denominations and churches, school systems and campuses, publishers and imprints, associations and chapters, or ministries and regional offices.
Data Integrity Rules
Relationships should preserve context without creating duplicate truth.
Each organization should have one authoritative record unless separate legal or operational entities require distinct records.
Contacts may belong to multiple organizations, but each organizational role should be documented separately.
Activities should not exist without a defined owner, creator, date, and meaningful related record.
Reassignment should update active responsibility without deleting prior assignment history.
Merged records should preserve prior identifiers, activity history, and the administrator responsible for the merge.
AI Context Relationships
AI guidance should inherit context through approved relationships.
Partner profile provides role, readiness, responsibilities, and permissions.
Organization provides mission, type, location, relationship status, and history.
Contact provides role, communication preferences, and prior participation.
Conversation provides verified notes, commitments, questions, and outcomes.
Task and follow-up objects provide timing, ownership, status, and next action.
Resources provide approved materials appropriate to the audience and relationship stage.
Relationship Governance
Connections require the same governance as records.
Users may only create, change, or remove relationships allowed by their role.
Important relationship changes should create an audit event.
Historical relationships should be ended or archived rather than erased.
AI may recommend a relationship or next action but should not alter authoritative links without explicit approval.
Restricted personal or ministry information should not be inherited outside authorized relationships.
Implementation Sequence
Object relationships should be implemented in controlled stages.
STAGE 1
Core Objects
Implement partners, organizations, contacts, and user profiles.
STAGE 2
Assignments
Add formal partner-to-organization assignment records.
STAGE 3
Relationship Activity
Connect conversations, notes, tasks, follow-ups, resources, and opportunities.
STAGE 4
Intelligence
Add approved AI context, recommendations, summaries, and executive insights.
Connected records create useful intelligence.
The FEOS Object Relationship Model ensures that partners, organizations, contacts, activities, resources, learning records, and recommendations operate as one connected system rather than isolated information.