Under development. Not finished, not released. Version numbers are build numbers; four claims are unverified. What that means
TESSERA

Federation mesh · specification v1.1

TESSERA

The mosaic layer above every CRM.

Every system you already run becomes a tile. The tiles keep their own shape and their own identity. Together they make one picture — and one tamper-evident record of how the picture was made.

Specification + reference core — no product Console: live in your browser 748 tests passing, no dependencies 43 defects found, 43 closed 22 deliverables, 22 acceptance criteria PolyForm Noncommercial 1.0.0

It runs. Right now, in this browser tab.

The console is the reference core ported to the client: field-level merge, conflict resolution that names its rule, a SHA-256 chain you verify yourself, and seat-based routing. No server, no account, no network after the first load.

The TESSERA console: one customer record with provenance on every field, three conflicts flagged, and an activity feed from four systems.
Open the live console Console source
  • Unified — every field names the system it came from and the rule that chose it
  • Resolve — both values, both trust scores, and the deciding rule before you choose
  • Ledger — verify recomputes SHA-256 in the page; a tamper button proves it works
  • Workforce — work goes to a position; the router prints its arithmetic
  • Automate — a playbook written by an agent cannot run until a person approves it

Installable as an app. Works offline. One 43 KB HTML file, no framework.

The problem

Four to seven systems hold a slice of the same customer. The slices disagree.

Reconciling them costs a person a morning a week, and the reconciliation is invisible to everyone else. The usual answer is a migration: move everything into one CRM, lose two years of history in the edges, and repeat the exercise in five years.

01

No migration

Adoption is additive. The mesh connects to what exists and produces the first result before anything is moved. The native core is one node in the mesh, not the product.

02

One ledger

Every action in every connected system becomes one hash-chained event. “What did each system know at time T” has exactly one answer, and it is provable.

03

Seats, not users

Work is assigned to a position, not a person. A human or an agent fills it. Every agent seat must declare a fallback, and every handoff carries full state, signed.

How it works

Three moves, in this order.

STEP 1

Connect

A node joins with a capability manifest, a versioned schema map and a per-field authority map. Nothing is copied. Nothing is migrated.

STEP 2

Unify

One canonical schema, ten objects, four sync modes per field. Conflicts resolve by a declared order and are logged — never silently overwritten.

STEP 3

Prove

Every action lands in the ledger. Bi-temporal views and git checkpoints are projections of it, and a projection that cannot be rebuilt is a defect.

Four systems, one merge, one proof.

Sources feed the mesh. The mesh merges field by field and records the rule it used. The ledger keeps every action. Work goes to seats, and a human or an agent fills them.

Architecture: HubSpot, Salesforce, Zendesk and NetSuite feed the federation mesh, which writes to a hash-chained ledger and a seat-based workforce; a console reads both.

Architecture

Eight layers. Five are specified, three are roadmap with written entry criteria.

L0

Federation mesh v1

Nodes, canonical schema, four connectors, deterministic routing, universal ledger, conflict resolution.

L1

CRM core v1, optional

Reference implementation of the canonical schema. Local-first web, encrypted offline mobile.

L2

Workforce v1 subset

Seats, occupants, tasks, handoff packets, escalation ladders, two observable autonomy tiers.

L3

Intelligence v2

Graduated autonomy, workforce analytics with provenance, cost-aware routing.

L4

Protocol and settlement v3

Cross-company chains, agent-to-agent transactions, a universal dispute trail.

L5

Economic engine v3

Marketplace with provenance, outcome billing, revenue share for published org designs.

L6

Experience v1

Design system, jargon discipline enforced by lint, migration as an interface rather than a project.

L7

Learning v1

Bootcamp, coach, academy, documentation, changelog, community — ten artefacts, each with a criterion.

Non-negotiable

Three rules, each with a test. A rule without a test is a slogan.

1

No AI in the critical path

Read, write, sync, auth, search, report and notification work with every AI container switched off. The full test suite must pass at the bare profile.

2

Nothing is silently overwritten

A cross-system conflict resolves by a declared order and is written to the ledger with both candidate values and the rule that settled it.

3

History has one authority

The event ledger is the record. Bi-temporal columns, git checkpoints and graph projections are derived, and must be rebuildable from it.

The audit

The specification was audited against itself before anything was built.

The source was a 261-line build prompt. Four passes — structural, definitional, contradiction, external — found 43 defects. All 43 are closed here, by formal definition or by a numbered assumption with a named owner.

43
defects found
7
blockers that stopped construction
7
composite scores defined for the first time
22
deliverables with testable criteria
18
recorded assumptions
3 → 1
history mechanisms ruled to one authority

What exists: a specification, an audit register, a metric dictionary, acceptance criteria, three rendered documents, and a dependency-free reference core — the canonical schema, the hash-chained ledger, every metric, routing, conflict resolution, the connector contract, the conformance suite, four connectors, backpressure, a working mesh, projections that rebuild from the ledger a workforce layer, an HTTP surface with an OpenAPI 3.1 contract, three-layer access control, a compliance substrate and local-first sync, under 748 tests. Reviewed: 13 findings, 11 fixed.

What does not exist: the product. No connector has called a live tenant — every result comes from a recorded transport. The Postgres DDL has been parsed by Postgres’s own parser and never executed against a server. There is no hosted service and no customer has used this.

What changed since this page was written: the service does listen (python3 -m tessera.api), the interface does render (the console, in a separate repository), and a demo starts both halves with python3 -m tessera.demo. The sentence that used to say otherwise was wrong, and being wrong in the modest direction is still being wrong. Every public claim and its check is in the claim register.

What was corrected: the source document’s 30-day data-subject-request clock was a GDPR transplant and is now a per-jurisdiction configuration. Its 72-hour breach clock was right — DPDP Rules 2025, rule 7(2), requires it — and is retained.

Documentation

Fifty-four documents. Read five of them and you have the system.

01Product definitionCustomers, the activation event, what is out of scope 02ArchitectureLayer model, boundaries, failure semantics 03Federation meshNodes, connectors, routing, conflict resolution 05WorkforceSeats, occupancy, handoff, revocation 10Metric dictionaryEvery score in the product, defined once 11History authorityWhich record wins, and why 12AI contractThe non-negotiables, each with its test 16Acceptance criteria22 deliverables, 22 tests 53LicensingDual licensing, and what it does not grant 52Brief conformanceThe twenty deliverables, and every deviation 51ControlsSix IT general controls, and how each is tested 50TenancyIsolation by construction 49DeletionTombstone, reason, and what is not destroyed 48Standalone modeA layer and a CRM 47Running itOne command, one link 46CORSThe allowlist, and the gap it exposed 45Smoke auditOne real call into every module 44Archival and compactionSegments, a header, a proof that survives 43ReleasingThe tag, the gate and the generated note 42Property testsFour invariants, a replayable seed, R-17 41Offline mobileKey custody, durable outbox, seven days away 40Design systemMeasured contrast, 83 icons, the WCAG matrix 39Postgres and RLSThe DDL, four assertions, what could not run 38DeploymentContainer, manifests, and the docs rule 37Learning and onboardingBootcamps, academy, coach, glossary 36Migration wizardAuto-mapping, rollback, templates 35Jargon lint and pluginsA lint that blocks release, four gates 34LocalisationFive locales, RTL mechanism, historical rates 33Boring features and escape hatchesImport, undo, backup, four audited doors 32AutomationA condition language that is not Python 31Code review13 findings and a ship-or-block verdict 30Local-first syncOffline writes, guaranteed convergence 29ComplianceConsent, DSAR, retention - and R-07 28Access controlObject, field and row rules at one gate 27API and contractsHTTP, OpenAPI 3.1, ten MCP tools 26WorkforceSeats, signed handoff, revocation 24Projections and checkpointsWhat we knew vs what was true 23Stage one, completeSync modes, backpressure, measurement 22Provider connectorsHubSpot, Salesforce, Zendesk behind a seam 21Connectors and meshThe contract, the suite, the unified view 20Reference coreWhat is implemented, tested, and what is not ADefect register43 defects: severity, location, impact, fix RCompliance, checked 2026DPDP Rules 2025 and AI Act timing, with sources