Elements

app.docketiq.xyz/elements
Search the case
Ask AI⌘J

What must be established, count by count

28 elements across 7 counts · 10 assessed as supported

Count 1 — Breach of Contract

#ElementWhat must be establishedFactsEvidenceWitnessesGapsStatus
1Valid contractA valid and enforceable contract existed between Meridian and Halvorsen.4100Supported
2Plaintiff's performanceMeridian performed its own obligations under the contract.1111Contradicted
3BreachHalvorsen failed to perform: it did not remit the full share and did not report all fees collected.2220Supported
4DamagesMeridian suffered damages caused by the breach.0000Partially supported

Count 2 — Misappropriation of Trade Secrets

#ElementWhat must be establishedFactsEvidenceWitnessesGapsStatus
1Trade secretTempo's forecasting models and training pipeline are trade secrets: not generally known, deriving independent economic value from secrecy.1100Supported
2Reasonable measuresMeridian took reasonable measures to keep the information secret.0000Partially supported
3Interstate commerceThe trade secret relates to a product used in interstate commerce.0000Supported
4MisappropriationDefendants acquired the secret by improper means, or used or disclosed it without consent.6210Partially supported
5Damages or unjust enrichmentMeridian suffered actual loss or defendants were unjustly enriched.0001Evidence needed

Count 3 — Breach of Fiduciary Duty

#ElementWhat must be establishedFactsEvidenceWitnessesGapsStatus
1Fiduciary relationshipKane owed Meridian fiduciary duties as a director.1100Supported
2BreachKane breached the duty of loyalty or confidentiality.1110Partially supported
3CausationThe breach caused harm to Meridian.0000Attorney review
4DamagesMeridian suffered damages, or Kane profited.0001Evidence needed

Every Count, One Page.What Must Be Established, in Plain Words.

Each element states what has to be shown, beside the facts, documents, witnesses and open gaps standing behind it, and its status. Twenty-eight elements across seven counts, read top to bottom.

Element status

Only counsel moves an element from one to another.

  • Evidence neededNothing in the vault has been linked to this element yet.
  • Partially supportedSome propositions under this element have support; others do not.
  • SupportedEvidence and witnesses are linked to every factual proposition under this element.
  • ContradictedMaterial in the vault cuts against this element.
  • Attorney reviewWaiting on counsel’s assessment.

When the Record Cuts the Other Way.Contradicted, and Shown Why.

An element the record contradicts carries the evidence against it alongside the evidence for it: the disputed fact, the document and witness that cut the other way, what is still missing, and counsel’s assessment of what to do about it.

2Plaintiff's performance

Meridian performed its own obligations under the contract.

Contradicted
Facts supporting this element
  • FACT-037Meridian delivered the v4 integration API about six weeks after the January 31, 2025 target.Disputed
Evidence supporting those facts
  • MERIDIAN-000001 Reseller and Implementation Agreement, § 3.2 Context
Witnesses
  • Elena Ruiz Contradicts
Contrary evidence
  • MERIDIAN-000011 Email — E. Ruiz to T. Kane re v4 integration API timing
Missing evidence
  • Whether the delay was material

    § 3.2 requires commercially reasonable efforts, not a fixed date, and v3 stayed supported.

    Suggested: Collect the v3 support tickets for February and March 2025.

AI analysis Advisory

The answer’s prior-breach defense rests on the six-week slip. The Agreement sets an effort standard rather than a date, which is the stronger reading, but the slip itself is documented and should be owned.

Attorney assessment
Evidence neededPartially supportedSupportedContradictedAttorney review
Halvorsen's answer alleges Meridian delivered the v4 integration API late in breach of Section 3.2; the March 2025 email (MERIDIAN-000011) shows a six-week slip. Assess whether the delay was material.
Save assessment

Default Framework.Nothing Assumed, Until Counsel Adopts It.

Elements written at setup are marked as a default framework, not taken from the pleading as filed or checked against the governing jurisdiction. Counsel edits what is wrong, then confirms the count.

Confirming records that counsel adopted the structure, by name.

2 elements here are still the default framework.

Confirm Count 6

1Benefit conferred

Defendants received a benefit.

Adopted by counselPartially supported

2At plaintiff's expense

The benefit came at Meridian's expense.

Default frameworkAttorney review

3Unjust retention

Retaining the benefit without payment would be unjust.

Default frameworkEvidence needed

Counsel’s Own Words.Reword, Reorder, Remove.

Put the elements in the order of proof, rewrite any of them, or remove one. Editing marks an element as counsel’s own. Removing one detaches its facts, evidence and witnesses rather than deleting them.

3Unjust retention

Evidence needed
↑↓Edit wordingRemove
Save wordingCancel

See It on a Real Case.Request a Demo, or Take the Tour.