Zoikorum™
Records & Exports

Keep the engagement
record connected —export only what you’re authorized to use.

ZoikoRum brings permitted contracts, approvals,
delivery evidence, control decisions and other
engagement records into one source-linked view,
then lets authorized teams build scoped evidence
packages and controlled exports without losing
provenance.

Records workspace · synthetic example

Agreement · SOW v4

Contracts · current

Current

Approval decision · budget

Approval Workflows · approved

Approved

Milestone 2 evidence

Milestones · accepted submission v2

Current

Restricted record

View-only · excluded by policy

Restricted

Package tray · 4 records

AgreementApproval decisionMilestone 2 evidenceAudit event
  • Source-linked records
  • Permission-aware packaging
  • Explicit exclusions
  • Controlled export history
Connected
Source-linked
Scoped
Controlled
Why it matters

Evidence without
the scramble —
or the theater.

Connected
records

Bring
material
engagement
records
together
without
detaching
them
from
the
source
systems
that
own
them.

Source-
domain
+
version
chips

Source
lineage

See
where
each
record
came
from,
when
it was
current
and
which
governed
object
it
references.

Lineage
drawer

Scoped
packages

Select
the
evidence
needed
for a
defined
purpose
instead
of
downloading
everything
by
default.

Package
Builder

Controlled
delivery

Validate
permission,
exclusions
and
export
profile
before
a file
is
generated
or
retrieved.

Validation
+
manifest
+
Export
Center
What belongs in an engagement record

Eight record
families — each
owned at its source.

A retrieval taxonomy, not a second ledger. Source
domains stay authoritative.

Contract & scope

Agreement, SOW and change
versions

Agreement, SOW and change versions can
remain connected to the engagement record.

Contracts / SOW
Authority & decisions

Who decided, on which version

Approval and exception records can show who
decided, on which version and under what
authority where permitted.

Approval Workflows
Delivery & acceptance

Submissions stay traceable

Milestone submissions, permitted evidence
references and acceptance state can remain
traceable.

Milestones
Payment references

State, never secrets

Supported payment-state references can be
included without exposing payment secrets or
moving money.

Payment Protection
Disputes

Linked, still governed

Permitted case state and evidence references
can remain linked while restricted material stays
governed.

Dispute Resolution
Trust & eligibility

Status, not documents

Approved verification/eligibility state can be
referenced without exporting private credential
material by default.

Trust & Verification
Controls & exceptions

Outcomes with context

Control and exception outcomes can remain
connected to scope, policy and decision context.

Engagement Controls
Audit history

Timeline and report context

Material actions can be inspected in
timeline/report context and handed into a
package where supported.

Audit & Reporting

How record lineage works

Source → projection
→ package → export.

  1. 01

    Source

    A specialist system owns the truth — Contracts,
    Approvals, Milestones and more.

    Source domain + object label
  2. 02

    Projection

    Records show the exact object, version and when
    the view was last confirmed.

    Version + currentness
  3. 03

    Package

    You choose why each record is included — scope
    and category, never “everything.”

    Package scope + category
  4. 04

    Export

    The export carries an ID, generation time and an
    included/excluded summary.

    Manifest + profile

Product proof · records workspace

Find the right record,
see where it came from.

Filter, inspect provenance and add records to a
package. Restricted items stay view-only.
Synthetic data.

Example engagement · Advisory
program

Firm Example Advisory LLC

Service Regulated advisory

Jurisdiction [Jurisdiction]

Agreement SOW v4 (current)

Context changed [timestamp]

Illustrative
Search safe labels…
All familiesAny currentnessAny exportability
Record
Source
Object /
version
Date
Currentness
Exportability
Action
Executed
agreement
Agreement
Contracts
SOW v4
[date]
Current
Eligible
Remove
Budget approval
decision
Decision
Approval
Workflows
Decision request
· v4
[date]
Current
Eligible
Remove
Milestone 2
acceptance
Delivery
Milestones
Submission v2
[date]
Current
Eligible
Add to
package
Statement of workAgreement
Contracts
SOW v3
[date]
Superseded
View-only
View-only
Release-state
reference
Payment ref
Payment
Protection
Milestone 1
reference
[date]
Current
Eligible
Add to
package
Dispute case
evidence
Dispute
Dispute
Resolution
Case reference
[date]
Current
Excluded
Excluded
Control decision
history
Audit
Audit &
Reporting
Event stream
[date]
Source unavailable
View-only
View-only

Record detail · provenance

Executed agreement

SourceContracts
ObjectSOW v4 · Current
EventContract executed by authorized
signatories
ProjectionConfirmed [timestamp]
ExportEligible for selected profiles

Package tray

2
Executed agreementRemove
Budget approval decisionRemove
Open Package Builder

Related context

Audit & ReportingContracts / SOWMilestonesApproval WorkflowsPayment ProtectionDisputeTrust
Product proof · package builder

Explicit scope.
Validated before
before
anything is generated.

Nine steps — no default “all accessible data.”
Your tray currently holds 2 record(s).

  1. 1Define scope
  2. 2Choose purpose / recipe
  3. 3Select records
  4. 4Validate permissions & source
  5. 5Review exclusions / redactions
  6. 6Choose export profile
  7. 7Review manifest preview
  8. 8Confirm & generate
  9. 9Retrieve / handoff
Step 1 of 9Example

Define scope

Your decision

Choose engagement, record family, selected
records or a date range within allowed
context.

System responsibility

Resolve only records you may discover.

Guardrail

No default “all accessible data.”

Export manifest & history

Prove what was
generated — and why.

Manifest previewExample
Scope
Example engagement · 2 selected record(s) · current
versions
Source coverage
Contracts · Approval Workflows · Milestones · Audit
— current
Included data
Human-readable categories and fields
Excluded / redacted
1 record excluded by policy · reason class only
Export profile
[Runtime-provided approved profile]
Requested by
You · Compliance reviewer · purpose recorded
Snapshot
[Request time] · validated source state
Limitations
A scoped export of authorized ZoikoRum records; it
does not establish universal legal sufficiency.
Export CenterDemo
Export
Status
Requested
Actions

Q3
procurement
review

Available

[timestamp]
·
Procurement

Manifest ·
Retrieve

Milestone 2
evidence

Generating

[timestamp]
· Legal

Manifest

Approval
history pack

Blocked

[timestamp]
· Finance

Why
blocked?

Earlier
evidence
pack

Expired

[timestamp]
·
Procurement

Regenerate
as new
Job statesDRAFTVALIDATINGBLOCKEDREADYGENERATINGAVAILABLEPARTIALFAILEDEXPIRED / UNAVAILABLESUPERSEDEDCANCELED

Meaning

Validation passed; confirmation is
required.

What you see

Manifest preview and a final confirm
action.

Roles, privacy & minimization

Clear data boundaries,
enforced at the server.

Recommended policy concepts —
actual classification names stay
implementation-controlled.

Classification concepts, workspace behavior and default export
Classification conceptWorkspace behaviorDefault export
General engagement metadataVisible to authorized participants/roles.Eligible when selected and the profile allows.
Role-restricted business dataVisible only to assigned roles.Included only after current role validation.
Sensitive professional / identity
evidence
Source summary/reference over raw payload.Excluded by default unless policy and purpose allow.
Sensitive financial dataSafe status/reference only.Never includes secrets; field masks apply.
Dispute / investigation
evidence
Highly scoped.Excluded unless the authorized case profile allows.
Buyer-private policy / rationaleNever shown in professional-facing views.Only internal authorized profiles, safe portions.
Secrets / credentials / tokensNever rendered.Never exported through this destination.

Exclusion

The record or field isn’t in the export. Used
when revealing its existence is unnecessary or
unsafe.

Redaction

A safe placeholder appears because disclosing
the field’s existence is appropriate. Policy-
driven — never a cosmetic front-end action.

Roles & permissions
RoleViewActMust not
silently gain
Buyer / requesterRecords relevant to their
engagement and role
Build/export
permitted packages
Procurement,
legal, finance
or org-wide
rights
Professional / firm memberShared participant-facing
records
Export own
permitted records
where supported
Buyer-private
policy logic or
others’
restricted
evidence
Procurement / program ownerRecords within assigned scopeCreate governed
evidence packages
Legal/finance
authority
unless granted
Legal / compliancePermissioned agreement,
approval, dispute and evidence
records
Review/export
within scope
Universal
tenant access
by title alone
Finance / controllerPermitted
commercial/milestone/payment-
reference records
Export
reconciliation/review
evidence
Bank/payment
secrets or
dispute
evidence
ApproverDecision records
assigned/visible to them
View/export
permitted decision
evidence
Policy-edit or
org-wide
record access
Internal auditor / reviewerRead-only evidence across audit
scope
Package/export
where granted
Mutation
rights
SupportDiagnostic metadata needed to
resolve issues
Support-safe
actions with audit
trail
Broad
evidence
access or
export for
convenience
AdministratorAdministrative access as
configured
Manage approved
settings/roles
Automatic
access to
sensitive
content
Changes & currentness

Snapshots, not rewrites.
History stays distinct.

  • Superseded

    SOW v3

    Kept distinct from the current version — never
    collapsed into one ambiguous “document.”

  • Current

    SOW v4

    The validated source state used for new export
    requests.

  • Snapshot

    Export #1 (v4)

    Fixed at its request time. Later changes never
    silently rewrite it.

  • Regenerated

    Export #2 (new)

    Regeneration creates a new snapshot with its own
    identity.

Source-unavailable records are never promoted to current
or export-ready because a cached projection exists.

Enterprise assurance

Auditable, least-
privilege — and
honest about its limits.

Request a Demo

Sourceownership

Specialistdomainsstayauthoritative;Records&Exportsneverbecomesasecondledger.

Leastprivilege

Role-awareaccessandminimization,enforcedserver-side.

Exporthistory

Everyexportkeepsan ID,manifestandrequesterwherepermitted.

Jurisdictionaware

Availabilityandpolicycanvarybymarket,programandservice.

Noinventedformats

Onlyruntime-supportedexportprofilesappear.

Nohard-codedretention

Retentionandavailabilitycomefromthesource.

Audithandoff

Audit &Reportingownstimelinesandcross-engagementanalysis.

AssistiveAIonly

AI mayexplainororganize;it can’tgrantaccessorinventevidence.

Your records · example
Shared SOW v4Viewable
Milestone 2 acceptanceExportable
Approval outcomeOutcome onlyBuyer-private rationale stays internal
For professionals & firms

Your participant
records — without
buyer-private leakage.

You can see & export

Agreement versions you’re entitled to, your
deliverables and acceptance records, approval
outcomes needed to operate, and payout/release
state through the payment domain’s rules.

Stays protected

Buyer-private policy logic, internal approvals,
approver rationale and other professionals’
restricted evidence.

Professionals and firms ·
illustrative photography

Find the record
Build the
package
Export
with proof
Questions

Records &
Exports, answered.

Audit & Reporting

Get started

Connected records.
Controlled exports.

Evaluate how ZoikoRum keeps evidence
source-linked, scoped and permissioned.

An export is a scoped package of authorized ZoikoRum
records and does not by itself establish legal, regulatory or
evidentiary sufficiency in every jurisdiction or proceeding.
Availability depends on engagement, role and implemented
capabilities.