Eight situations. Eight features built in response.

Maria and David separated after eight years together. They have two children. David sends three to four messages a day — many containing veiled threats, sarcasm, and legal intimidation framed carefully enough to pass OurFamilyWizard's keyword filter. Maria opens each message with her hands shaking. She spends 45 minutes drafting a response, re-reading it, deleting it, starting over — terrified her words will be used against her in court. Her therapist says communication anxiety is her primary mental health stressor.

OFW's ToneMeter is a keyword-based flag system. It puts a warning sticker on the message. Then it delivers the message anyway. The hostile message still arrives. The damage is still done.

What no existing app did — and what Maria needed — was not documentation of the conflict but interruption of it. A system that stops a message before it lands, shows the sender what a better version looks like, and gives the recipient a way to read the factual content without the emotional load.

Parenting Path scores every outgoing message across four dimensions before it sends: hostility, legal risk, emotional volatility, and child impact. When a message scores above the threshold, it is held. The sender sees three alternative versions — all preserving the information, none carrying the tone that was going to make things worse. The co-parent never receives the original.

On the receiving end, messages from the co-parent that score highly are blurred by default. Maria sees a neutral, AI-generated summary of the factual content first. The original is always available with one tap — the record is never deleted. She chooses when she is ready to read the full version.

James is the father of two. His court order runs 23 pages. It contains 12 enforceable rules:

Right of first refusal kicks in if either parent will be away for more than four hours during their custody time. Fourteen days written notice is required before any out-of-state travel with the children. Spring break custody alternates annually between parents. His ex-wife pays 40% of extraordinary medical expenses. Holiday schedules rotate on odd and even years by a specific list.

James has the PDF. OurFamilyWizard has the PDF. TalkingParents has the PDF. AppClose has the PDF. None of them know any of those rules exist.

James manually tracks notice deadlines in his phone calendar. Last year, he created a work travel event and updated his personal calendar but did not convert it into a formal notice inside the app. The deadline passed by one day. His ex-wife's attorney used it in a motion. The rule was in writing. It had been in writing for three years. No app had ever mentioned it.

Zero co-parenting apps currently parse court orders. This is the single largest functional gap in the entire market. Every family has a court order. Every court order has enforceable rules. Every one of those rules is currently tracked manually by the parent — or forgotten entirely.

Parenting Path reads the order. Upload the PDF. An OCR pipeline extracts the text and a language model trained on thousands of US family court documents identifies every enforceable clause: the custody schedule, all notice periods, the holiday alternation, the expense ratios, right of first refusal terms, travel restrictions, communication restrictions. Every extracted clause is shown to the parent for review before anything is activated. You confirm what we understood correctly and edit anything we got wrong. Nothing activates without your explicit confirmation.

From that point on, the rule engine evaluates the active rules against the current calendar every morning at 6am. It looks seven days ahead. It generates countdown alerts for approaching deadlines. When a deadline passes without the required action, a violation record is created automatically — immutable, timestamped, and included in every court report covering that period.

Priya's divorce decree is specific about money. Extraordinary expenses — medical, dental, therapy, extracurricular — are split 60% father, 40% mother. Regular expenses — school supplies, clothing — are 50/50. Her court order runs four pages on the expense section alone.

Every time Priya submits a medical expense on OurFamilyWizard, the app gives her two choices for the split: 50/50 or 100%. Those are the only options. The most common court-ordered split ratio in the United States is 60/40. OurFamilyWizard supports neither.

So Priya writes "PLEASE PAY 60% PER COURT ORDER" in the expense notes. Every time. Her ex disputes the calculation. Every time. She has been through 27 separate expense disputes in 18 months. Each dispute requires a response, documentation, often an attorney consultation. The correct number was in the court order all along. The app simply had no way to read or apply it.

This is not an edge case. It is the most common complaint about expense tracking across every co-parenting app. Every family with a court order that specifies anything other than 50/50 or 100% faces exactly this problem.

Parenting Path allows any split ratio, per expense category. Medical: 60/40. Education: 70/30. Extracurricular: 50/50. Each category is independently configured. When a court order is uploaded and the expense split clauses are activated, those ratios auto-populate the expense settings. When Priya submits a medical expense, the app shows: "Based on your 60/40 arrangement — You pay $204 (60%). [Co-parent's name] owes $136 (40%)." The co-parent sees the same calculation. There is nothing to dispute.

Kevin uses Google Calendar for everything. His work meetings are there. His personal appointments are there. When his custody schedule changes, he updates Google first because that is where his life lives.

Lisa is court-ordered to use OurFamilyWizard. Their shared co-parenting calendar exists inside OFW. Kevin's personal life exists in Google. These two systems do not talk to each other.

Every time something changes in OFW, Kevin re-enters it in Google. Every time something changes in Google that affects co-parenting, Lisa never sees it unless Kevin also enters it manually into OFW. The duplication is constant. The gap it creates is inevitable.

Last month, Kevin's work schedule changed. A meeting moved. He updated his Google calendar with the new pickup time. He was going to update OFW. He forgot. Lisa drove 25 minutes to the school at 4pm. Kevin wasn't there — he had moved the pickup to 2pm, updated his Google calendar, and genuinely believed he had handled it. He hadn't. Lisa was standing at the school pickup line at 4pm for a child who had already been picked up by Kevin at 2pm and was now at home doing homework.

The resulting argument lasted three days.

The fix is technically straightforward. It is called bidirectional calendar sync and it has existed as a standard software feature for over a decade. No co-parenting app has implemented it. OurFamilyWizard has had 25 years. They haven't.

Parenting Path connects to Google Calendar via OAuth and to Apple Calendar via CalDAV. A dedicated calendar — "Parenting Path — [Child Name]" — is created in the user's Google or Apple account. Events created or changed in Parenting Path appear in Google within seconds. Events changed in the Google calendar sync back to Parenting Path within five minutes. The custody calendar and the personal calendar are the same calendar.

Sarah's abuser was ordered to co-parent via a co-parenting app. The court meant well. The order was designed to give both parents a structured, documented communication channel. What it did not account for was that the standard features of every co-parenting app were, for Sarah, a threat.

The profile photo she uploaded showed her face and her new haircut. Her abuser studied the background of the photo and used the visible details to track the neighbourhood she had moved to. The GPS coordinates embedded in the photo's metadata — which no existing app stripped — confirmed the area.

The app displayed her check-in location for 30 minutes after each pickup event. Her abuser used this to know where she went after each exchange. The feature that was designed to help coordinate pickups was being used to monitor her movements.

The app's name was visible on her home screen. During one exchange, her abuser's new girlfriend, who had access to Sarah's phone for a few minutes, saw it. The app became known. The phone became unsafe.

The Safety Net Project's documented finding states it plainly: if a survivor is ordered to use an app that conflicts with their safety plan, they become confused and less safe. The order that was meant to help was making things more dangerous.

Approximately 23.5% of US divorces involve domestic violence. That is roughly 3.2 million co-parenting relationships where standard app features actively create risk. No existing app was designed for these families.

DV Safety Mode in Parenting Path was built around one principle: the co-parent must never know it is on. Activating Safety Mode changes nothing visible to the other parent. The shared interface — messages, calendar, expenses — looks identical. No notification is sent. No difference is detectable.

What changes is everything else: the app can display as a neutral decoy icon on the home screen. An emergency quick-exit gesture closes the app and clears it from the recent apps list instantly. Every photo uploaded through any part of the app — on any plan, always — has GPS and device metadata stripped before storage. Incoming messages are blurred by default. Notifications show no content, no sender name, no sound. The safety journal is encrypted on-device with keys stored in the phone's secure enclave — we cannot read it, and we cannot produce it under subpoena because we do not hold it.

Rachel Kim is a family law attorney in Los Angeles. Her client came to her in crisis. She needed to understand what had happened in the past 14 months of a high-conflict co-parenting relationship. The evidence was all there — messages, expenses, calendar events, compliance violations — sitting inside OurFamilyWizard and TalkingParents in three different export formats and a folder of screenshots.

Before Rachel could advise her client on anything, she needed to turn that material into something usable. She read through 847 messages to identify hostile patterns and extract the ones that mattered. She exported and reformatted expense records showing 23 payment delays. She cross-referenced calendar events against court-order dates to find 7 missed pickups. She built a chronological timeline from multiple disconnected sources.

Six hours. $2,100. Before any legal work had begun.

This is not unique to Rachel's practice or to this client. The structure of existing co-parenting apps — data stored in formats designed for parents, not attorneys — means that every family law attorney who uses these records as evidence must first convert them into something a court can process. That conversion is billable time. It is paid by clients who are already under financial strain from the divorce itself.

Parenting Path generates a court-standard PDF report in under 90 seconds. The parent selects a date range and chooses which sections to include: the AI-written executive overview, communication tone analysis with trend charts, missed and late pickup log, expense payment history and delays, court order compliance violation log with clause text, and a chronological incident timeline with every significant event from all included sections. The PDF is US Letter, 20mm margins, with a SHA-256 tamper-evident hash in every footer.

Rachel's client generates the report. She shares a time-limited link. Rachel opens it in any browser — no account, no app installation. She clicks any item in the timeline to view the source record. She downloads the PDF. The first meeting with her client is spent on strategy, not on formatting spreadsheets.

Sophie's parents have been co-parenting for two years. Both parents use a co-parenting app. The app knows their schedule, their disputes, their payment history, and their message audit log. It knows nothing about Sophie.

Sophie has been having panic attacks on Sunday nights before custody transitions. Her school counsellor noticed her grades dropping on weeks following high-conflict exchanges between her parents. Her therapist has been working with her for four months and would find it useful to know whether Sophie's emotional state correlates with specific calendar events or communication spikes. No app captures any of this.

Sophie — the person every co-parenting app claims to be designed for — is completely invisible inside every co-parenting app on the market.

Child wellbeing tracking in Parenting Path was built around three design principles. First: neutral, not accusatory. Every AI-generated insight is framed as an observation about what correlates with the child's wellbeing — never as blame toward either parent. Second: visible to both parents equally. Neither parent has privileged access to mood data. Third: strictly scoped for therapists. A therapist granted access sees mood history, transition records, and patterns. They see nothing else — no messages, no expenses, no court data. This scope is enforced at the system level, not just in the interface.

Each day, a parent (or Sophie herself, if she is old enough) logs how her day went using a five-level emoji scale. Optional notes can be added. The check-in takes less than 30 seconds. Both parents see every entry at the same time. Neither parent gets a different view.

At the end of each month, a mood heatmap shows every day colour-coded by Sophie's self-reported state. Transition days are marked. The 30-day moving average trend is visible. If the data shows that Sophie's mood is consistently lower on the days following a custody exchange, both parents see that pattern together — framed not as an accusation but as an observation.

Tom and Angela disagree about Marcus. Their son is eight. He wants to join a travel hockey team. The cost is $3,200 per year, which needs to be split. The training schedule requires travel on alternating weekends, which will affect the custody arrangement. The expense category doesn't clearly fit any of the categories in their court order.

There is no bad faith here. Tom thinks hockey is too expensive and the schedule disruption too significant. Angela thinks the activity would benefit Marcus and that they can accommodate the logistics. Both positions are reasonable. Neither parent is wrong.

They have been arguing about it for three weeks via the co-parenting app. The tone scores are spiking. Both attorneys are now involved. Tom is paying for his attorney's time. Angela is paying for hers. Combined, they are spending more than $2,000 in consultation fees to adjudicate a decision about whether an eight-year-old should play travel hockey.

The only escalation path available inside any existing co-parenting app is: more messaging (the broken channel), or an attorney (expensive, slow, adversarial). There is no third option.

Dispute Resolution in Parenting Path is that third option. It is a structured, AI-facilitated mediation flow that gives both parents a path to resolution before it reaches a lawyer.

Either parent initiates a Structured Discussion. Both join. An AI categorisation identifies the issue type: Financial, Scheduling, or in Tom and Angela's case, Extracurricular. The matching resolution template loads.

Each parent answers three structured questions privately — neither can see the other's answers while writing. When both have submitted, the answers are revealed simultaneously. The AI then generates a shared interest summary: a neutral paragraph identifying what both parents agree on (Marcus's wellbeing) and what separates them (cost and schedule disruption). This summary is shown to both parents before any direct negotiation begins.

Each parent submits a proposal. The proposals appear side by side. Each parent can mark individual elements they agree with, elements they want to counter, and elements they cannot accept. Counter-proposals are targeted — only the unresolved elements, not a full re-proposal from scratch.

When all elements are resolved, a digital agreement is generated. Both parents type their name to sign. The signed document is stored permanently. No attorney required. No filing fee. No waiting for a court date.