Evolution and lessons
The model evolved with the work.
Earlier domain systems coexist with newer production-first boundaries. The current architecture did not exist from the beginning.
- Profile and professional relationships
- Project and workflow expansion
- Teams and publishing
- Availability and staffing
- Production-first work model
- Resources and shared review
- Native client expansion
Profile and professional relationships
- What existed
- Persistent presentation and personal professional connections.
- Problem
- Identity alone does not describe participation in temporary work.
- What changed
- Introduce explicit work context and participation.
- Retained
- Persistent people, profiles and personal relationships.
- Transitional
- Earlier person presentations and domain-specific context links.
- Lesson
- Professional identity should outlast a production.
Project and workflow expansion
- What existed
- Project context and feature-owned obligations.
- Problem
- Growing workflows need clearer ownership and consistent transition semantics.
- What changed
- Separate canonical source work from presentation and effects.
- Retained
- Useful domain records and compatibility.
- Transitional
- Earlier domain-specific workflow paths.
- Lesson
- Generalization must preserve the source domain’s authority.
Teams and publishing
- What existed
- Shared operational state and public presentation.
- Problem
- Visual collaboration similarity can obscure different authority boundaries.
- What changed
- Describe shared presentation separately from Team ownership and public projections.
- Retained
- Team lifecycle and explicit publication.
- Transitional
- Provider and ownership compatibility where still active.
- Lesson
- Sharing UI does not mean sharing authority.
Availability and staffing
- What existed
- Candidates, requests and coordination sources.
- Problem
- Interest, availability, booking and actual presence are different facts.
- What changed
- Connect staffing evidence to intended work without conflating identifiers.
- Retained
- Existing source-owned staffing and availability mechanisms.
- Transitional
- Links between earlier staffing records and newer production work.
- Lesson
- A commitment is not an arrival record.
Production-first work model
- What existed
- People participating in project work.
- Problem
- Participation and a single job description do not cover changing or multiple assignments.
- What changed
- Make Membership, Assignment, Groups and Production Days explicit.
- Retained
- Durable identity and compatible operational records.
- Transitional
- Preparation, cutover and compatible application release remain separate.
- Lesson
- Changing work should not recreate a person.
Resources and shared review
- What existed
- Creative assets and existing approval subjects.
- Problem
- Separate approval stacks repeat version, review and audit mechanics.
- What changed
- Use context-bearing resources, immutable versions and shared subject adapters.
- Retained
- Subject ownership, media boundaries and independent task completion.
- Transitional
- Integration coverage and hosted acceptance vary.
- Lesson
- Approval needs exact content identity.
Native client expansion
- What existed
- Web and supported shell experiences.
- Problem
- Platform interaction differs while domain truth should remain shared.
- What changed
- Expand native UI through shared server contracts.
- Retained
- Supported existing experiences during migration.
- Transitional
- Incremental SwiftUI migration and uneven native coverage.
- Lesson
- Share contracts without promising identical interfaces or parity.