Relationship Intelligence
SynkHeart
SynkHeart — relationship intelligence powered by SoulGraph.
Turn scattered context into respectful, privacy-first next actions. Built for people actively dating or maintaining important relationships.
High alignment signal based on ontology fit, pacing, safety, and compatibility inputs.Not destiny. Not diagnosis. Use as a reflection prompt.
Relationship timing: Near-term timing and emotional readiness.Powered by SoulGraph, CosmicRank, YANAMSA, SynkOS.
Product Modules
SynkHeart is the consumer UX layer, while shared packages own the meaning graph, compatibility signals, YANAMSA timing lens, and SynkOS planning contracts.
A dating CRM surface for people, matches, notes, preferences, next actions, and relationship state.
Displays summaries and user-approved notes; raw chat is not required.A review queue for pasted text, screenshots, chat exports, CRM rows, and calendar summaries.
Raw payload storage remains false by default; users approve extracted signals.Scores fit across values, cadence, interests, timing, and contextual compatibility.
Uses summarized features rather than raw private conversations.Interprets symbolic systems, symbols, archetypes, and meaning frames.
Frames symbolic output as reflective context, never deterministic fact.Models cycles, windows, message timing, date timing, and reflective planning moments.
Timing suggestions are opt-in and subordinate to consent and availability.Turns suggested actions into reminders, calendar holds, and follow-up workflows.
Adapter contracts avoid direct frontend tokens and keep scheduling consent explicit.Real Relationship Flows
Public examples show how SynkHeart supports reflection without diagnosing people or pretending a score decides the relationship.
Use Attraction Dynamics and Safety Signals to separate real interest from rush. The next move is a warm, specific invitation with space to decline.
Use Communication Asymmetry to ask whether care is present but arriving through a different cadence or channel.
Use Repair Pathways to name the rupture, choose clarification over pressure, and look for changed behavior rather than a perfect apology.
Use Attachment Rhythm and Vulnerability Timing to decide whether the connection has earned deeper disclosure.
User Workflows
Clear flows keep relationship intelligence useful without turning private communication into surveillance.
Add a person, context, consent boundaries, and current relationship stage.
SoulGraph summarizes interests, cadence, signals, risk, and timing context.
CosmicRank, YANAMSA, and SynkOS shape a date suggestion with rationale.
User approves extracted signals, corrections, reminders, and next actions.
Relationship Ontology Overlay
SynkHeart exposes the feeling of a connection as editable compatibility signals: resonance, pacing, attachment, communication, growth, and tension.
Relationship Ontology Map
Every concept is a clickable diagnostic surface: chemistry, attachment, planning, trust, repair, safety, compatibility, and growth.
Concept Clusters
Follow the relationship graph by need: understand chemistry, repair tension, plan better dates, or test trust evidence.
Relationship intelligence clusters
What To Click Next
SynkHeart keeps the next useful diagnostic move visible after every interpretation.
People often over-trust attraction when it is strong and dismiss it when it is quiet. Naming the source of attraction helps the user tell the difference between aliveness, anxiety, projection, and genuine fit.
AttachmentAttachment RhythmMany promising relationships fail because one person's healthy space feels like disappearance to the other. Rhythm makes pacing discussable before it becomes a story about care.
AttachmentEmotional PacingGood pacing protects chemistry. It keeps the user from forcing clarity before trust exists or avoiding clarity after trust has been earned.
CommunicationCommunication AsymmetryWithout translation, people often interpret style differences as rejection, pressure, neediness, or indifference.
PlanningTravel FairnessFair logistics create emotional safety. Repeated imbalance can quietly become resentment even when chemistry is strong.
PlanningDate EnergyA good match can feel wrong in the wrong energy container. Energy-aware dates help chemistry appear without overtaxing either person.
AttractionConversation ChemistryConversation is often the first live test of values, pacing, intelligence, and emotional safety.
RepairConflict RepairLong-term compatibility depends less on never missing each other and more on whether the misses become information.
Date Planning Ontology
Date suggestions are not random activities; they are plans shaped by energy, travel fairness, novelty, pacing, and trust formation.
Choose a date with enough novelty to test spark and enough quiet to test ease.
Logistics equityTravel FairnessOffer a midpoint option and explicitly name the travel tradeoff.
Energy fitDate EnergySelect a plan with matching noise, duration, and recovery cost.
Conversational fitConversation ChemistryChoose a setting with light shared stimulus and enough quiet for follow-up questions.
Timing readinessMomentum WindowsSend a clear invitation inside the next low-pressure availability window.
Reciprocal interestMutual CuriosityPick a plan that creates natural prompts for stories, preferences, and choices.
Shared delightPlayfulness IndexChoose a low-stakes activity with room for shared discovery.
Tension qualityMagnetic TensionChoose a date with structure and enough calm to test whether tension can become dialogue.
Trust and Privacy Explanation
SynkHeart favors reviewed signals, correction actions, and privacy-preserving explanations over black-box certainty.
Draft repair prompt · Name impact before intent · Delay escalation · Track follow-through
TrustTrust FormationWeight behavior over promise · Ask for specific plan · Flag reliability gap · Slow vulnerability
SafetyBoundary SignalsHonor stated limit · Remove late-night suggestion · Ask before escalating · Mark boundary as hard constraint
TrustEffort BalanceAsk for plan ownership · Mark effort imbalance · Pause over-functioning · Suggest simpler reciprocal action
SafetySafety SignalsFlag safety concern · Remove escalation suggestion · Recommend public/short date · Slow intimacy pacing
RepairRepair PathwaysChoose repair type · Draft message · Ask for changed behavior · Pause escalation
TrustEmotional ReciprocityAsk for specific support · Mark one-sided care · Pause over-disclosure · Choose lighter plan
Architecture Boundaries
Each layer owns a narrow job so the consumer app does not duplicate ontology or hidden inference logic.
Consumer relationship intelligence and dating CRM experience.
Owns: relationship workspace, preference chips, date review UXShared ontology, memory graph, inference contracts, and relationship graph engine.
Owns: ontology entities, memory graph shape, inference boundariesCompatibility and fit scoring across relationship dimensions.
Owns: dimension weights, compatibility score output, fit explanationsSymbolic, astro-temporal, Western, Vedic, Chinese, archetypal, and timing interpretation.
Owns: symbolic systems, archetypes, temporal cyclesPlanning, synchronization, reminders, and workflow orchestration adapters.
Owns: date workflow steps, reminder plans, calendar handoff contracts