Platform · Agent Ops
The value moves. Work follows.
A builder your operations team can use: chains composed from the values already on record, run now, on a schedule, or after your approval. No code in the loop.
The same mechanism completes LMS procedures end to end for CIPD centres today
01 · The chain
A chain is a sentence anyone can read.
Not a diagram only an integrator understands. A written rule: when this value is on record, do these things.
Chains are authored and versioned like everything else on the platform. Sokros drafts them from how your team already works; you approve the version that runs, and every firing names the version that fired.
WHEN an invoice's payment terms are recorded
AND the early-settlement window is open
THEN flag the invoice with the window's closing date
THEN draft the settlement request, hold for approval
02 · The builder
Built from sentences, not code.
Your team composes WHEN and THEN rows from the record's own vocabulary. If a value is on file, a rule can name it.
Presets ship polished and configured to your estate. Every amendment publishes as a numbered version, and every firing names the version that fired. There is no marketplace to assemble: the builder is configured with the engagement, pointed at your record.
From the record
WHEN cert_expiry.forklift is within 30 days
THEN draft the renewal email to the site lead
THEN hold the draft for approval
03 · Schedules & blasts
Now, at six, or on Friday.
Chains run at the speed the work actually needs, and the speed is part of the written rule.
Instant
The chain fires the moment the value lands. For the work where an hour is the difference: an ineligible submission, a failed check on a live stream.
On instant plansThe daily sweep
Everything that accrued since yesterday, cleared in one run before the team sits down. The 06:00 sweep that CIPD centres know, pointed at any queue.
Standard plansBatch, on your calendar
Weekly reconciliations, bi-weekly pulls, month-end reports. Scheduled chains run unattended and file their results in the record.
Any planA blast, held at the door
The renewal run
When a run of certificates approaches expiry, the chain drafts the renewal emails as one blast and queues the whole batch for approval. Your ops lead reads it, releases it in one click, and every send files its receipt.
A digest, filed weekly
The Friday digest
Every week a chain compiles the area-insights digest and files it to the record, where it reads like any other value: the same figures, cut the same way, on the same morning.
04 · Early warning
Early warning, not fortune telling.
Some platforms sell prediction. Sokros does not put a guess between your evidence and your outcome.
A certificate thirty days from expiry is a fact with a date. A utilisation figure past a written threshold is a fact with a value. Chains warn from facts on record, the threshold is yours, and the warning names the value that tripped it.
Both warnings trace to a recorded value and a written threshold. Neither involves a forecast.
05 · Agents, with approvals
Agents with a written job description.
An agent here is a named worker assembled from chains: it has a job, the rules that bound it, and a record of everything it did.
Dispatch clerk
Releases approved work to your systems in batches, holds anything that fails a rule, files the receipt.
Bounded by your dispatch and approval chains
Preconfigured · amendable on requestRecords clerk
Files incoming values, applies the sorting patterns, flags what matches no pattern for a person.
Bounded by your ingest and quality chains
Preconfigured · amendable on requestSite watch
Watches live-layer events, raises threshold warnings, opens work orders where a chain says so.
Bounded by your monitoring chains
Preconfigured · amendable on requestNothing sends itself.
Any action that leaves your boundary can be held for a person, and the chain names who that person is.
Emails, releases, postings: drafted by the chain, queued for one-click approval, released in batches when you say so. What runs unattended is what you wrote down as safe to run unattended.
06 · Integration
It reaches the systems you already run.
The systems you already run
Chains read from and write to LMS platforms, ERP and finance systems, CRM, document stores and ticketing queues. Connections are configured per estate, not sold as a logo wall.
Webhooks and custom functions
Your engineers can receive every event a chain emits, and register functions a chain can call. Both run under the same written bounds as everything else.
A private API, with its docs
The API, its reference and the tooling around it arrive with the engagement, scoped to your build. Sokros does not run a public developer portal, and your integration surface is not a shared one.
Inside your product, under your brand
Under agreement, the layer runs embedded in your own product with your name on it. The record still replays; the boundary is still yours.
There is no public sandbox and no self-serve key. The surface arrives with the engagement, which is also why it fits when it does.
07 · Determinism
Same values in, same actions out.
Every firing is stored
Which value moved, which rule version fired, what ran and what was held: one record per firing, kept like every other decision.
Replay any day's activity
Re-run Tuesday's chain activity against the same values and the same rules and it lands identically. An automation you can audit is the only kind worth wiring in.
A chain cannot leave its bounds
Chains act only through the actions written in them. There is no improvisation step, and an action outside the written set has nowhere to come from.
Wire the record to the work.
Pick one queue your team clears by hand. One briefing, one chain written and fired in front of you, approvals exactly where you want them.
A 30-minute briefing: one queue scoped, a gated pilot plan.