# Primary Company Lifecycle Sync Direction

Explain association-driven stages without treating contact changes as company updates.

## Scope
Preparation and review only. No account action or professional decision.

## Inputs
Contact/company IDs, primary association, lifecycle settings and dated field history.

## Workflow
1. Identify the primary company, not just any association.
2. Apply documented company-to-contact direction only with sync setting evidence.
3. Keep forward-only behavior and later-stage contacts separate.
4. Return provenance without changing primary associations or stages.

## Output contract
contact | primary_company | sync_enabled | company_stage | contact_stage | direction | unknown

## Fictional acceptance test
Fictional primary company is Lead; contact A Subscriber and contact B Opportunity. With enabled default sync A can advance to Lead, B does not move backwards. A contact-only edit does not prove a company edit.

## Review gates
Keep original values, source IDs and version dates. Unknown facts stay held. Use qualified review for hiring, legal and accounting conclusions. No send, share, sign-in, scheduling, ledger change or payment. Fictional contract review is not a live account compatibility test.

## Method source
https://knowledge.hubspot.com/object-settings/manage-how-lifecycle-stages-sync-between-objects

Checked October 13, 2026. Oct13 live AIS Search Console: marketing Copilot37 impressions, Planable/Claude43, Planable/ChatGPT24, campaignbrief12, investoragent19, MuseIndia103. Social calendar/reporting topics follow parent-query leads; other professions follow documented workflow needs, not measured exact intent. Site impressions are not monthly volumes; exact topic volume is unmeasured.