1
00:00:00,000 --> 00:00:08,590
This is the story of a single number — and
what it takes to never be surprised by it.

2
00:00:13,560 --> 00:00:17,950
A new enterprise agreement
has arrived at Meridian Care.

3
00:00:18,270 --> 00:00:31,030
Somewhere inside it is a number that now governs what people
must be paid. It is not in a dashboard, or a database.

4
00:00:33,040 --> 00:00:39,920
It is buried on page 146 of a PDF.

5
00:00:41,100 --> 00:00:50,420
Schedule J. Minimum hourly rates, per role and
level. And two employees are already below it.

6
00:00:53,890 --> 00:01:01,210
This is the result. One pay-floor alert. Two
employees below the minimum that applies to them.

7
00:01:02,180 --> 00:01:17,460
A. Nguyen is on twenty dollars an hour. The agreement requires twenty-one thirty-four.
The reason is visible in the row — not hidden behind a score or a summary.

8
00:01:17,660 --> 00:01:26,240
Now let's rewind — and see how Strata knew, and
why nobody has to take that answer on trust.

9
00:01:30,620 --> 00:01:36,260
Before that — one more result,
and it matters just as much.

10
00:01:37,530 --> 00:01:48,630
One employee's role has no matching minimum in the agreement. Strata reports it:
not enough data. It does not quietly turn missing information into compliance.

11
00:01:48,830 --> 00:01:55,730
In a system making consequential decisions,
knowing when not to claim certainty is a feature.

12
00:01:56,970 --> 00:02:02,610
So how did Strata know? Rewind
to the day the evidence arrived.

13
00:02:07,360 --> 00:02:15,520
It starts here: the agreement, the payroll export and
the employee register — together in one knowledge base.

14
00:02:15,880 --> 00:02:24,460
Strata reads each source, finds the structure inside it,
and keeps the original evidence attached to what it learns.

15
00:02:25,910 --> 00:02:37,020
That matters because the rule and the payroll record must stay
connected to where they came from — so the answer can be checked later.

16
00:02:39,960 --> 00:02:51,480
These are payroll records, employee details and enterprise agreements. None of them needs
to leave Meridian's environment — everything in this demonstration runs on one machine.

17
00:02:51,940 --> 00:03:00,520
Meridian does not have to trade control of sensitive
information for the ability to understand and act on it.

18
00:03:03,620 --> 00:03:13,460
From those documents, Strata builds a working model of Meridian:
its people, roles, pay rates and minimums — and how they connect.

19
00:03:13,790 --> 00:03:21,520
A pay rate belongs to a role. A role is
governed by a minimum. Employees hold roles.

20
00:03:21,720 --> 00:03:31,980
And where a real relationship depends on more than one field — here,
both classification and level — Strata keeps that relationship intact.

21
00:03:32,740 --> 00:03:39,220
Simple data-quality rules ride along: employee
IDs must be unique, rates must stay sensible.

22
00:03:39,650 --> 00:03:54,110
The screen calls this an ontology. In practice it means you can move from a rate,
to the rule that governs it, to the people affected — with no web of manual lookups.

23
00:03:57,860 --> 00:04:07,280
Now we ask the question the compliance lead actually cares
about: is any hourly rate below the minimum that governs it?

24
00:04:09,370 --> 00:04:16,670
Watch: the hourly rate… below…
the minimum from the agreement.

25
00:04:17,040 --> 00:04:29,820
The limit is not copied into a setting — it is read from the agreement
data itself. The rule you just watched being built is the rule Strata runs.

26
00:04:31,550 --> 00:04:43,490
No code needed — Certant turns this into a safe, exact check. And every
row gets one of three answers: in breach, compliant, or not enough data.

27
00:04:43,930 --> 00:04:48,150
Let's run it now — normally
it runs on a schedule.

28
00:04:52,500 --> 00:04:56,040
The rule runs. One alert. Two employees.

29
00:04:57,330 --> 00:05:12,610
A. Nguyen is on twenty dollars. M. Torres is on seventeen fifty. Both compared with the
DDSO level-two minimum of twenty-one thirty-four — the reason travels with the result.

30
00:05:12,810 --> 00:05:22,650
You can do the same comparison Strata just did. The minimum
was not typed into the monitor. It came from the agreement.

31
00:05:27,230 --> 00:05:34,970
The next question is the one a board member or
payroll manager asks immediately: who is affected?

32
00:05:35,320 --> 00:05:46,000
Strata does not ask a model to estimate. It follows the relationships in
Meridian's data and counts the distinct records: one role, two employees.

33
00:05:47,060 --> 00:05:55,640
The path is visible — from the pay rates, to the
governing classification, to the people who hold it.

34
00:05:55,840 --> 00:06:05,260
That turns 'we think the issue is contained' into 'here
are the two people, and here is how we counted them'.

35
00:06:10,880 --> 00:06:21,570
Finding the breach is only useful if the response is controlled. This action
prepares the correction and carries it through a process Meridian designed.

36
00:06:22,000 --> 00:06:29,320
The most important step is the deliberate pause:
nothing consequential happens until a person signs off.

37
00:06:29,520 --> 00:06:36,010
Strata automates the chasing, the preparation and the
record-keeping. It does not automate accountability.

38
00:06:41,540 --> 00:06:50,120
Back at the alert, the correction is ready — and already
waiting for sign-off. Before anything changes, preview it.

39
00:06:51,280 --> 00:06:56,090
Preview shows what would happen —
without changing anything, anywhere.

40
00:06:58,090 --> 00:07:03,310
Two people are affected — let's
audit one of them properly.

41
00:07:08,710 --> 00:07:18,550
Here is A. Nguyen's pay record: twenty dollars an hour — with
its history, its relationships, and its sources in one place.

42
00:07:21,720 --> 00:07:31,980
The twenty dollars is tied back to the payroll file — hover
the source and there is the actual table it came from.

43
00:07:33,840 --> 00:07:40,740
Follow the governing relationship, and there is the minimum
that applies: twenty-one dollars, thirty-four cents.

44
00:07:46,920 --> 00:07:55,920
And the minimum has its own source: page 146 of
the agreement — the exact table from the cold open.

45
00:07:56,120 --> 00:08:07,640
The record, the rule, the comparison, and the page. This is the moment
the alert becomes defensible — nobody has to say 'the system says so'.

46
00:08:10,220 --> 00:08:17,540
The resolution is ready — but not authorised.
Notice who requested it: the watch rule itself.

47
00:08:17,880 --> 00:08:28,140
The payroll manager sees exactly what will run before signing off.
The plan is frozen — nothing can be quietly swapped in afterwards.

48
00:08:28,340 --> 00:08:32,720
And the requester can
never approve its own work.

49
00:08:35,050 --> 00:08:40,690
A person approves — and only then
does the agreed action execute.

50
00:08:45,960 --> 00:08:56,640
The record now answers the uncomfortable questions before anyone asks them:
who requested this, who approved it, what was authorised — and what happened.

51
00:08:56,840 --> 00:09:11,720
Where an effect can be compensated, Strata applies the defined correction rather than pretending time
can be reversed. And if an outcome is ever uncertain, the record says so — instead of inventing success.

52
00:09:14,470 --> 00:09:21,370
This is not a one-off analysis. Payroll can
send each weekly export straight into Strata.

53
00:09:21,730 --> 00:09:26,110
Each delivery is checked,
deduplicated and kept on file.

54
00:09:26,410 --> 00:09:28,750
Here is this week's delivery, arriving now.

55
00:09:32,260 --> 00:09:40,840
The model refreshes without anyone repeating the setup by hand.
The compliance control continues as the underlying data changes.

56
00:09:44,950 --> 00:09:56,050
But fresh never means uncontrolled. When a feed arrives in a shape
Strata has not seen before, it does not silently reshape the live model.

57
00:09:56,400 --> 00:10:04,560
The new structure waits here for a person to review
it. Your model never changes behind your back.

58
00:10:07,500 --> 00:10:19,440
The source does not have to be a document or a file feed. Strata can
follow changes straight from a database — every insert, update and delete.

59
00:10:21,120 --> 00:10:30,950
The same principle applies: new data can arrive continuously, but structural
change still passes through review before it reshapes the live model.

60
00:10:37,380 --> 00:10:43,860
The correction is through, the record
is complete — and the issue is closed.

61
00:10:47,230 --> 00:10:55,390
Monday morning now feels different. The agreement can
change. Payroll can keep moving. New data can keep arriving.

62
00:10:55,590 --> 00:11:06,930
But the rule, the people it affects, the evidence and the
approval stay connected — all the way back to this page.

63
00:11:07,130 --> 00:11:12,350
The audit may still come. The
surprise does not have to.

64
00:11:12,550 --> 00:11:17,710
Certant Strata. See it. Check it. Resolve it.