The Wardline platform
The trust layer under every product.
Every Wardline product is built from the same foundations: records that show any change, approvals that need everyone, encryption that can be made permanent, and sign-in without passwords. Each product uses the parts it needs, and runs on its own.
Approved: swap weekend, Fri 9 Oct
- By
- Parent B
- At
- 2026-10-02 18:41:57 PT
- Previous
- 9f3c 71ae ··· 5a07
- This entry
- c41d 0b92 ··· e7f3
Illustrative example.
Foundations
What every product is built from
History nobody can rewrite
Every action is added to an append-only record, each entry linked by its fingerprint to the one before. A copy is written to storage that can't be edited or deleted, even by us, so any change after the fact shows.
Decisions that need everyone
Some actions only happen when every person with authority agrees. One decline stops them, unanswered requests expire, and closing access needs only one person.
Approval tied to exact text
Agreements, consents and forms are versioned and fingerprinted. An approval records exactly which version was approved, and any change clears it.
A key per family or case
Sensitive content is encrypted under its own key. Destroying the key makes that content permanently unreadable everywhere, including backups, while the record can still prove what existed.
Every space stands alone
Each family, case or organisation is kept separate from every other, and each product runs on its own infrastructure with its own keys and records.
Check it without us
Records can be exported and checked independently. Where it matters, they're also timestamped by outside services that anyone can verify.
One platform, separate products
How each product uses it
Each product has its own infrastructure, keys and records. A problem in one can't reach another, and each can grow at its own pace.
| Foundation | Co-Parent | Accord |
|---|---|---|
| Tamper-evident record | Every message, request and decision | Every change and approval on a case |
| Agreement rules | Plan changes, members, professionals, closing the account | Every party approves the final version |
| Approved versions | Parents confirm their legal relationship | Approvals tied to the plan's exact version |
| Encryption | A key per family | A key per case |
| Independent proof | Free, self-service export | Export, and fingerprints kept after deletion |
How we build
Verified, not assumed
Nothing clicked together
Every environment is defined in code and reviewed, so it can be rebuilt, audited and compared.
Against the real thing
Security rules are tested against real infrastructure, not just simulations.
Only where it helps
AI is used only where a product needs it, never to decide anything, and your content is never used to train models. Accord uses none.