Caelith Reporting Workflow Agent

Public demo guide for the real Annex IV operating workflow

What You Are Seeing

This demo does not treat Annex IV as an XML-generation problem. It shows the workflow compliance and fund-operations teams actually run: assemble a source pack, map it into the regulatory schema, resolve interpretive fields, screen the release population, then generate the XML and seal the evidence bundle.

Key idea: XML is the output of the workflow, not the workflow itself.

How to Read the Demo

The experience is organized around five phases that mirror real reporting operations.

1Intake

The agent assembles a filing pack from a controlling workbook, connected system exports, and parsed fund documents. The user confirms that this source pack reflects the actual reporting pack.

2Mapping

The agent maps internal operational fields into Annex IV fields, keeps provenance, highlights data-quality notes, and raises a judgment queue for fields that require regulatory interpretation.

3Screening

The mapped filing population is screened before release. Flagged names require explicit human dispositions so the filing pack cannot move forward without a visible decision.

4Filing

Only after the upstream work is complete does the agent render the Annex IV XML, validate it, and present the transport artifact for approval.

5Evidence

The final output is a sealed evidence bundle containing the audit trail, screening record, judgment decisions, XML snapshot, and source provenance.

What Is Real vs Simulated

Component	Status	Meaning
Source-pack model	Real	Workbook, systems, documents, mapping, and judgment layers match the actual product logic.
Screening workflow	Real	Flagged-subject review and human release controls are functional product concepts.
XML generation	Real	The demo renders a valid transport preview, but only after upstream workflow completion.
NCA submission	Simulated	The release to the regulator is simulated for the public demo.
Evidence bundle	Real	The demo shows the correct operational output: audit trail, provenance, and approvals.

What to Look For

Source-pack realism: The workflow starts from spreadsheets, system exports, and documents because that is what fund teams actually work with.
Mapping discipline: Notice how the agent shows internal-to-regulatory field translation instead of pretending data is already Annex IV-ready.
Human judgment: Some fields require interpretation. The agent surfaces those decisions instead of hiding them behind false certainty.
Release control: Screening is a real gate before filing, not a decorative extra.
Auditability: The evidence bundle is treated as a first-class output alongside the XML file.

                Strategic takeaway: Caelith automates the regulatory ETL, control, and evidence workflow that sits upstream of submission. That is the durable RegTech value, not just XML rendering.
            

Questions or technical discussion?

Julian Laycock, CEO
julian.laycock@caelith.tech

The public demo is designed to reflect real fund-reporting operations within a safe simulated environment. It is the right starting point for architecture, workflow, and pilot discussions.