// What we build

Reading is easy. Writing is the deployment.

A decision that survives the next endorsement, appears in the audit trail, and does not break the effective-dated model. This is the step most pilots die at.

// The surface

Where it actually runs.

Guidewire Cloud API — versionedApplication EventsIntegration GatewayCloud Data AccessDuck Creek gatewayeffective datingchange-control calendar

Reading from a Cloud Data Access replica in S3 is straightforward — the data is already leaving the system on its own. Writing a decision back into PolicyCenter so it survives the next endorsement, appears in the audit trail, and respects effective dating is a different problem, and it is the one that separates a demo from a deployment.

It needs entity-model depth, a versioned API contract, and your change-control calendar. Those are the three things a proof-of-concept never has, which is why the proof-of-concept always works.

// What we measure

Definitions, taken before anything is built.

01

Write success rate by transaction type

Not an average. New business, endorsement, cancellation and reinstatement each fail differently, and an average hides the one that matters.

02

Endorsement survival

The share of written decisions still correct after the next policy change. This is the number nobody measures, and the reason write-back projects get quietly abandoned.

03

Audit-trail completeness

Every written decision traceable to its input, its model version, and the human who could have overridden it.

04

Rollback rate

How often a written decision has to be reversed, and by whom — tracked as a first-class metric rather than hidden in a support queue.

“Write-back is the step that has to work before anything upstream of it matters. A decision that does not survive the next endorsement is a decision the business stops trusting.”

// Where this comes from

// What's hard about this

Release-train coupling.

Anything built against a non-sanctioned surface breaks on the vendor’s schedule, not yours.

So we build on Application Events, Integration Gateway and Cloud API — or we tell you the thing you want is not safe to build yet. We verify general-availability status against the vendor’s own documentation before scoping, not after, because several of these surfaces have moved in and out of early access in the last two years.

Bring us one workflow.

We will tell you whether the decision survives the next endorsement, and what it would take to make it. How the read works →