Platform · Viewpoints
One record, every angle.
Every value the platform reads or watches can be kept in one record: discovered, cleansed, catalogued, and opened through viewpoints your team saves and shares.
The same record layer holds every grade CIPD centres have marked on Sokros
01 · Discovery & ingest
Everything that holds values, in.
An estate is stores, drives, mailboxes, databases and, since the live layer, streams. The record layer pulls from all of them on a schedule you set.
Discovery comes first: the estate is walked and catalogued, so you know what holds values before anything is pulled.
Structured rows are checked at the door against written quality rules: dates that parse, codes that exist, names normalised. A row that fails goes back with its reasons attached, not silently into the record.
02 · The read
Every format, one field.
Contracts in print, notes in handwriting, a briefing on audio, a chart, a register, a walkthrough on video: Sokros' own models read them all into typed, quoted fields.
Bundles are split before a word is read: a contract, its certificates and a scanned email chain each routed to their own schema. Reading is multilingual, Arabic included. The quote stays in the language the author used, and the field arrives in yours.
“aggregate liability is capped at £2,000,000
page 14 · clause 14.2 · lines 3–4
03 · The catalogue
Completed by rules, resolved into entities.
A kept value is finished on the way in: normalised, coded and tagged by rules that are written down and versioned.
The account code, the tax treatment, the classification tag: each inferred value names the rule that produced it. Then mentions resolve into entities, matched across documents and checked against your system of record.
Meridian BioTech
4 mentions · matched on registration number, address, contract reference
Each match shows its evidence. A duplicate is held for a person, never deleted by a hunch.
One supplier, spelled four ways, resolves into one entity. Duplicates, conflicts and cross-document checks in depth: data resolution →
04 · Viewpoints
A viewpoint is a saved way of looking.
A query, its scope and its rules, kept under a name your team can open. The record stays one; the ways of looking at it multiply.
Static: pinned and versioned
A static viewpoint shows the record as it stood when the view was signed, kept under a version number. Open it next year and it re-runs byte for byte to the same page.
Dynamic: a live query
A dynamic viewpoint re-runs as values land. The certificate view is current the moment a new row arrives, under the same written rules every run.
Both run as written queries over the record. Open either twice and the same view comes back twice, every value keeping its quote.
Every saved view names its rules and its version. Re-running one is a click, not a request to IT.
05 · The graph
Your records, joined up.
Resolved entities connect: supplier to site, site to finding, finding to certificate. The result is a graph you can walk, drawn from evidence.
Views over the graph are deterministic queries, not model output. Ask which suppliers touch a site with an open finding and the answer is a path you can follow edge by edge, each edge quoting the record that created it.
Highlighted path: supplier → site → open finding. Every edge quotes the record that created it.
06 · Outputs
It ends where your systems start.
A viewpoint that ends in a paragraph has only moved the reading problem downstream. What a view shows, it can hand over.
Your schema
Typed fields land in the schema you defined, exported machine-readable to whatever ingests them next. No paragraph for a human to re-key.
Your templates
Values render back into the documents your organisation files: row for row, the same mechanism that fills the official CIPD feedback sheet today.
Media from data
Charts, summaries and rendered artefacts drawn straight from the record, every line tracing to a quoted field. A chart you can audit is the only kind worth presenting.
Ask the record in plain language: Sokros Copilot →
07 · The record
A record you can put under oath.
Every value carries its quote
A record entry is a value plus the words, frame or cell that earned it. The layer holds no orphan numbers.
Any view re-runs byte for byte
A report, an entity page, an answer: each re-runs on demand and lands identically, for an auditor holding a year-old question.
Retention on instruction
The layer stores decisions and quoted evidence, not profiles. Deletion follows your instruction, and the deletion is itself recorded.
Change ships as a configuration version: the old version stays runnable beside the new, so last year's view of the record is still last year's view, and both answers stay defensible.
Bring the estate nobody can query.
The shared drives, the mailboxes, the database exports. One briefing, one slice of your estate landed in the layer and asked in front of you.
A 30-minute briefing: one estate slice scoped, a gated pilot plan.