Default completion
Imported.
Required readbacks and staged proofs pass. The import commits, with checkpoints and receipts recorded.
- Staged values checked
- Commit completed
- Full independent audit pending
Policy Capsule
Policy Capsule · For Guidewire PolicyCenter
Move the policy.Keep the proof.
Bring a complex policy case into QA. Keep its complete history without cloning the database.
- Complete policy history
- Business numbers preserved
- Independent verification
From a case to a working context
One policy.
Its whole story.
A difficult case is easier to investigate when its history comes with it. Follow a policy from its source to a rebuilt target, then see how the result is checked.
Illustrative exampleSource Target
01 / Capture
Start with the case
you already know.
Use a Policy Number or a Job Number. Capture the full policy history, including the records and relationships behind each transaction.
One starting point.
The complete history.
PolicyA history worth keeping.
- SubmissionWhere the policy begins
- Policy changeThe changes along the way
- RenewalThe next chapter
Records, relationships, and effective-dated history.
02 / Package
The history.
Ready to travel.
The policy, its connections, and the instructions for rebuilding it travel together. A manifest and checksums let the target check the package before making changes.
Business context.
In one portable capsule.
Business identityPolicy + Job numbers
Records & historyFields + effective-dated data
RelationshipsConnections + import intent
Manifest & evidenceChecksums + readiness
Logical records and relationships. A portable contract.
03 / Rebuild
Same policy.
A fresh home.
Keep the Policy and Job numbers. Rebuild the history with fresh internal identities and reconnect its relationships in the target environment.
Import committed.
Independent audit still to come.
Rebuilt policyFamiliar on the outside.
- Policy + Job numbers
- Preserved
- Internal identities
- New in target
- Relationships
- Reconnected
Imported with staged proofIndependent audit not yet run
04 / Verify · Optional audit
The target
gets its own say.
Export the rebuilt target, compare it with the source, and independently read unresolved persisted fields. A successful audit earns a separate verification receipt.
Run the audit now or later.
No import replay.
SourceOriginal
capsule
capsule
TargetFresh
export
export
- Compare the complete sets
- Read unresolved persisted fields
- Record the verification receipt
Independently verifiedOnly after a successful target audit
The difference is in the proof
Imported is one milestone.
Verified is another.
A completed import tells you the write process finished. An independent audit checks what actually persisted in the target.
After a successful independent audit
Verified.
A fresh target export is compared with the source. Unresolved persisted fields are read independently.
- Persisted target examined
- Differences resolved by evidence
- Separate verification receipt
The audit can run immediately or later on the same committed session. It is read-only and never repeats the import. If it finds a mismatch, the import stays committed and is not marked fully verified.
What comes with you
The context.
The connections.
The evidence.
Everything needed to describe the case and its intended rebuild travels together in the capsule.
- The policy’s story
Business numbers, fields, and complete effective-dated history preserve the context of the case.
- The relationships
Connections and import intent tell the target how the policy fits together.
- The evidence
A manifest, checksums, and readiness evidence let the target validate the package before changes begin.
Importable capsules contain sensitive policy business data. Administration exports encrypt them by default for download and transfer. Public reports expose hashes and counts—not raw values.
Boundaries you can trust
When the proof stops,
the workflow stops.
Unresolved relationships block import. An uncertain commit stops for reconciliation. Neither is quietly reported as success.
Data path
No raw SQLChanges go through PolicyCenter application APIs.
Target records
No silent deletionTarget-only records stay in place. The independent audit reports them as extras.
Commit outcome
No automatic retryAn uncertain commit is preserved for reconciliation, without repeating the mutation.
Policy Capsule
Bring the case.
Keep the context.
Reproducing a difficult issue in QA or preparing an upgrade validation? Let’s discuss how Policy Capsule fits your PolicyCenter workflow.