ManyKind Findings / system of record for professional findings

Findings, not answers.

ManyKind turns a matter record into a governed Finding: a conclusion that keeps its controlling evidence, reasoning, review decision and history attached.

Hand it to another lawyer. Reopen it six months later. Supersede it when the record changes. Verify how it was reached without reconstructing the matter from scratch.

No account needed for the sample.

Evidence attached Review recorded History preserved Independently inspectable

Built for contract review, diligence, disputes and in-house legal teams.

Finding MK-0241 on matter TERM-118, marked approved. The conclusion reads: termination requires 30 days written notice. Controlling evidence is Amendment 02 section 3. The conflict is the master agreement's 60 days against the amendment's 30 days. Review shows approved by Jane Doe. History shows it supersedes MK-0198.
  1. Create
  2. Review
  3. Approve
  4. Supersede
  5. Audit
Inspect Finding Record
An illustration of a Finding at the approved stage. Approval is a professional decision recorded by a person: ManyKind does not perform it.

An answer vs a Finding

An answer tells you what the AI thinks. A Finding records what your team concluded, and why.

Professional work does not end when a question is answered. Someone reviews it. Someone relies on it. The matter changes hands. New evidence arrives. Six months later, someone asks why the team reached that conclusion in the first place. ManyKind makes that entire lifecycle part of the record.

Answers are disposable. Findings become part of the record.

One matter record / five kinds of Finding

One matter. Governed Findings.

The conclusion usually lives in no single document. ManyKind joins the matter record, computes what it can, and keeps the controlling source lines attached to the Finding. Where the record runs out, the Finding says so.

Conflict / routed to review

Which notice period controls?

Two records disagree. Both stay visible.

60 daysmaster agreement §8.2
30 daysamendment 02 §3

Exact source lines

master-agreement.pdf §8.2

Either party may terminate with 60 days written notice.

amendment-02.pdf §3

The notice period in §8.2 is replaced by 30 days.

Routed to review, not silently resolved

Derived Finding

What is still owed?

$2,400 is due September 15, 2026.

$2,40050% of $4,800
Sep 15Aug 16 plus 30 days

Exact source lines

engagement-letter.txt

The remaining 50% is due within 30 days of accepted delivery.

invoice.txt

Total fee: $4,800.

acceptance.eml

Looks great, consider it accepted, Aug 16, 2026.

3 / 3 source lines matched

Change Finding

What changed in the latest draft?

The indemnity cap doubled.

€500,000draft v3 §11.2
€250,000draft v2 §11.2

Exact source lines

msa-draft-v3.docx §11.2

Aggregate liability shall not exceed €500,000.

msa-draft-v2.docx §11.2

Aggregate liability shall not exceed €250,000.

Both versions stay attached to the Finding

Derived Finding

Did we terminate in time?

Notice landed 12 days early.

Mar 31deadline, 60 days before renewal
Mar 19documented service

Exact source lines

msa.pdf §4.1

Renews automatically on May 30 unless notice is given 60 days prior.

courier-receipt.pdf

Delivered to registered agent, March 19, 2026.

Deadline computed, service documented

Insufficient evidence

Was notice ever served?

The authorised record does not establish service.

1record requires notice
0records show it was served

What the record does and does not hold

lease.pdf

Termination requires written notice to the landlord.

no record of service

No authorised source establishes a notice, a date or a recipient.

Insufficient evidence. ManyKind stops there.

The Finding / a governed unit of work

The Finding is the unit of work.

A ManyKind Finding is not a saved chat response. It is a versioned professional record containing the issue, conclusion, controlling evidence, conflicts, missing evidence, derivation, review decision and history. A matter lives in a Space. The work product is the Finding.

01 / Create

Evidence becomes a structured Finding.

The matter record is inventoried and the relevant evidence stays attached to the conclusion.

02 / Review

A lawyer reviews the decision points.

The reviewer can inspect the controlling language, challenge the reasoning and record a decision.

03 / Approve

Professional judgment goes on the record.

The machine does not approve its own conclusion. Responsibility stays with the professional.

04 / Reference

The Finding becomes reusable work product.

Another lawyer can reopen it without repeating the original reconstruction.

05 / Supersede

New evidence changes the Finding, not history.

A new Finding supersedes the old one. The previous conclusion stays intact and inspectable.

06 / Audit

Come back months or years later.

See what the team knew, which evidence existed, what it concluded, who reviewed it and what subsequently changed.

ManyKind does not give legal advice. The lawyer owns the judgment; the Finding keeps the record of how that judgment was reached.

The missing record layer

Documents record what happened. Findings record what you concluded.

Legal systems already preserve documents remarkably well. What they usually fail to preserve is the reasoning between those documents and the conclusion a professional ultimately relied upon. ManyKind creates that missing record layer.

Built for handoffsA matter changes hands. Instead of can you work out why we thought the notice period was 30 days? the next lawyer opens the approved Finding. The controlling documents, reasoning and review decision are already there.
Built for changeNew evidence should not silently rewrite old conclusions. When an amendment, correspondence or other relevant record changes the basis of an existing Finding, ManyKind preserves the prior Finding and creates a successor.
Finding MK-019860-day noticeSuperseded
Record changeAmendment 02 addedNew evidence
Finding MK-024130-day noticeApproved

You can inspect both.

Sovereignty, end to end

Sovereignty is a chain, not a slogan.

A professional system of record should not require an organisation to surrender control of the records, the execution or the resulting knowledge.

Deployments your organisation controls is what the system is designed for, not a per-deployment claim about how any given customer has configured it.

Data

Who controls the records? Authorised matter material enters under access your organisation controls, scopes and revokes.

Yours
Execution

Who controls the processing? Models and agents can execute inside infrastructure controlled by the organisation.

Controlled
Evidence

Who decides what supports a Finding? Evidence sufficiency, conflicts and abstention are explicit parts of the system.

Bounded
Conclusions

Who owns the Findings? Your Findings stay organisational work product with their evidence and history attached.

Owned
Verification

Can the record be inspected without trusting the interface? Finding Records preserve the evidence manifest, derivation, versions, review events and integrity information required to reconstruct what happened.

Verifiable

The exit

Sovereignty should include the exit.

Your professional knowledge should not become another form of SaaS lock-in. Export the Finding Record together with its evidence manifest, derivation, review history and receipts in a documented format. Your records stay useful outside ManyKind.

Built for how legal work actually runs

Built for the questions senior lawyers already ask.

ManyKind turns those questions into product structure.

Which document controls? What changed? Where exactly is that stated? What evidence are we missing? Who reviewed this? What did we conclude last time? Why did that conclusion change?

See it on your own matter

Bring one real matter. Leave with a Finding.

A 30 minute working session with your team. One matter. One governed Finding. Evidence attached. Review recorded. No slideware.