Anchor Escapement
The system of record for real-life coordination
Every action becomes a record. Every change is versioned. Every step is provable.
TS360 is the first product lens—household coordination built on the same platform spine that connects records, documents, Vault collections, and proof events.
See it in action
TransparentSee360 runs on this platform spine—open the public Lab on TS360 to explore households, timelines, expenses, and Anchor proof in one DEV surface.
Open TransparentSee360 LabThe problem
Life does not happen in one system. It happens across texts, emails, receipts, notes, appointments, documents, and memory. When it matters — court, care, recovery, accountability — scattered information is not enough.
A simple model
User → Record → Version → Document → Anchor
- Record what happened
- Version every change
- Link documents once
- Prove activity through Anchor
See the Platform
A unified system where records, documents, timelines, and proof all connect.
Records, versions, documents, and proof events all connect through a single operational spine.
The Anchor Platform Flow
How the Anchor Platform Databases Work Together
META defines identity. BM routes behavior. ED operates the product. ANCHOR proves what happened.
Explore layers
Current focus: ED
ED DB — Operational System
ED is the usable record. It stores operational records, record versions, domain tables, documents, vault collections, links, and the timeline spine the application runs on.
Highlights
- ed_record universal spine
- ed_record_version lifecycle
- Expenses, documents, vault, parenting plan
- Links and associations
- Source of app activity
META
Identity and relationships
BM
Behavior, rules, routing, orchestration
ED
Operational records, versions, and domain data
ANCHOR
Immutable proof and audit history
Core flows
Record & Edit
Create once. Never overwrite. Every edit appends a new version.
Expense + Receipt
Expenses become records, receipts become documents, and the relationship is provable.
Vault Documents
Important documents are curated by family, household, actor, or child.
Flow diagrams
Deeper views for TS360 and coordination workflows.
Expense submission
Vault birth certificate
Record edit and Anchor
Provable by Design
ED is the usable record. ANCHOR is the provable truth. DOMAIN tells the story. LIFECYCLE proves the chain.
When we refer to Anchor on this page, we mean the immutable proof layer—not the company name. Anchor Escapement is the platform; Anchor events are the audit trail you can rely on.
See the system working
Run the TS360 Lab Demo to watch records, documents, Vault membership, and Anchor proof events in one flow.
Explore further
Platform topics
- AnchorThe foundation architecture behind the full product suite.Open →
- TimelineThe chronological spine events attach to—one record, many lenses.Open →
- What It IsIdentity, permissions, chronology, and shared structure across products.Open →
- How It WorksHow the platform turns complexity into a coherent, connected system.Open →
- Connected SystemsWhy disconnected tools fail—and how the platform connects context.Open →
- Ask AlexGuidance and structured reads layered on the timeline—not generic chat.Open →
- See the PlatformLayers: Anchor, timeline, guidance, and product surfaces.Open →